
Legacy vs. Modern Systems: When to Modernize, Replace, or Leave It Alone
A practical decision framework for determining whether a legacy system should be left alone, stabilized, incrementally modernized, or replaced.
Read article →Practical architecture decisions, tradeoffs, and operating lessons from software that has to survive business change.
Search by business problem, system, or architecture decision, then narrow by the kind of guidance you need.
Showing 4 of 24 articles
Latest writing

A practical decision framework for determining whether a legacy system should be left alone, stabilized, incrementally modernized, or replaced.
Read article →Exploring the emerging software development scene in Fresno, California, and how local businesses are leveraging technology to grow in the Central Valley.
A practical approach to software time estimation with a 5-step methodology that includes worst/best case scenarios and padding for realistic project planning.
Complete guide to setting up AWS Code Build for TypeScript Node.js projects with buildspec.yml configuration for automated deployment to Elastic Beanstalk.