Make Changing Your Code Easier by Planning Ahead
In many agile development projects, code will need to change frequently, and clean code that is easy to understand is easier to change.| Atomic Spin
In many agile development projects, code will need to change frequently, and clean code that is easy to understand is easier to change.| Atomic Spin
This article is part of the series JEG2's Questions. I've built a lot of applications with a lot of teams. I've seen a lot of the problems with software development. There are two problems that I've seen so often that I believe they are worth looking out for at all times. The first of those is the accumulation of high cost dependencies.| The Programmer's Stone
Know how good your code needs to be for the task at hand. Start with a rough draft. Try to soften requirements if you can. Don't get distracted. Make small changes. Practice specific skills.| evanhahn.com
I’m going to talk about testing over the next few posts. If you’ve talked to me at any length over the last several years, you know I’ve been …| robnapier.net
Let's look at a simple example of a name. Let's judge the name (kindly!), then imagine some likely next steps in refactoring. We can learn and do quite a lot...| blog.thecodewhisperer.com
Going directly to a microservices architecture is risky, so consider building a monolithic system first. Split to microservices when, and if, you need it.| martinfowler.com
