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

Building Microservices

Microservices Intro Emerged in context of domain driven design, CI/CD, on-demand virtualization, infrastructure automation, small autonomous teams, systems at scale more flexibility to respond faster is goal What are microservices? small autonomous services that work together service boundaries based on business boundaries shouldn’t be too big (~2 weeks to rewrite) separate entities ideally own own… Continue reading Building Microservices

What We Actually Know About Software Development, and Why We Believe It’s True

Notes from talk have high standards when evaluating new methodologies / look for citations 10-100x developer study based on a small number of developers in the 60’s newer study looked at ~50 and each person for less than 1 hour Lutz Prechelt has done many studies here Study has shown errors correlated to lines of… Continue reading What We Actually Know About Software Development, and Why We Believe It’s True