#Issue9
3 posts

Efficient Software Project Management at its Roots

Clarity & alignment right from the start on why is the project being taken up, how will the team get it done and what role will each individual play Setting milestones that verify if the team is making progress in the right direction or not
Read more

Efficient Software Project Management at its Roots

Common patterns in software projects that are more successful than others:

  • Clarity & alignment right from the start on why is the project being taken up, how will the team get it done and what role will each individual play
  • Setting milestones that verify if the team is making progress in the right direction or not
  • Regular updates with 100% transparency about where each individual and the team really is in the development cycle
  • Dependency & risk management in a pragmatic way

Full post here, 8 mins read

Bad Practices in Database Design: Are You Making These Mistakes

Bad Referential Integrity Not Taking Advantage of DB Engine Features Poor Indexing & Naming Conventions
Read more

Bad Practices in Database Design: Are You Making These Mistakes

  • Ignoring the purpose of the data
  • Poor normalization
  • Redundancy
  • Bad Referential Integrity
  • Not Taking Advantage of DB Engine Features
  • Poor Indexing & Naming Conventions

Full post here, 9 mins read

A one size fits all database doesn’t fit anyone

When to consider what type of database: Relational: when referential integrity with strong consistency is needed. Key-value: when access patterns require low-latency Gets/Puts for known key values.
Read more

A one size fits all database doesn’t fit anyone

When to consider what type of database:

  • Relational: when referential integrity with strong consistency is needed.
  • Key-value: when access patterns require low-latency Gets/Puts for known key values.
  • Document: when you want developers to use something intuitive. Data in the application tier is typically represented as a JSON document.
  • Graph: when working with highly connected datasets.
  • In-memory: when you need microsecond response times and expect large spikes in traffic coming at any time.
  • Search: when you need to index and search semi-structured logs & data.

Full post here, 7 mins read