Agile Software Development: Principles, Patterns, and Practices

Agile Practices Individuals and interactions over process and tools working well with others, communicating, and interacting is more important than raw programming talent tools can be overemphasized, start small until you outgrow it Working software over comprehensive documentation software without documentation is a disaster, but too much is worse than too little maintain a rationale… Continue reading Agile Software Development: Principles, Patterns, and Practices

Peopleware: Productive Projects and Teams

Managing the Human Resource Intro managers try to treat people as modules Somewhere Today, a Project is Failing 15% (worse for bigger projects) software projects fail due to people-related issues, not technology high tech illusion: we are in high-tech business we are mostly in the human communication business focus on the technical, because it is… Continue reading Peopleware: Productive Projects and Teams

A Philosophy of Software Design

Introduction If you can visualize a system, you can probably implement it Means greatest limitation is theĀ  ability to understand the system we are creating Over time, complexity accumulates, leading to bugs which slows development two general approaches to fight complexity making code simpler and more obvious encapsulate complexity software design continual process, waterfall rarely… Continue reading A Philosophy of Software Design

Designing Data-Intensive Applications

Reliable, Scalable, and Maintainable Applications Intro applications today more data-intensive than compute intensive need to store data (dbs), remember expensive operations (cache), allow users to search (indexes), send a message to another process async (stream processing), periodically crunch a large amount of data (batch) Thinking About Data Systems wide-ranging requirements handled by stitching different tools… Continue reading Designing Data-Intensive Applications

Working Effectively with Legacy Code

Changing Software Four reasons to change software adding a feature fixing a bug improving design optimizing resource usage Adding features and fixing bugs some argue whether something is a bug fix vs feature more important distinction is behavior i.e. adding or changing Improving Design (Refactoring) keep behavior intact programmers avoid because easy to lose behavior… Continue reading Working Effectively with Legacy Code