The code is old.
Does it have to go?
“We’ll rewrite it” sounds like a fresh start. Sometimes it’s a very expensive way to rediscover the same rules. Why we prefer to understand first what is actually running.
Read the postIndependent minds.
Thorough code.
What’s on our minds about software.
And what you get out of it.
Thoughts on systems with a history, sensible decisions and the occasional comment that says “temporary”.
To the first post“We’ll rewrite it” sounds like a fresh start. Sometimes it’s a very expensive way to rediscover the same rules. Why we prefer to understand first what is actually running.
Read the postFor the decisions between “it works, doesn’t it?” and “should have been done ages ago”.
Two thoughts to take into your next technical conversation.
Before we optimise in the wrong place, we look for the time that is actually being lost. The most conspicuous code isn’t always the slowest.
Read about performanceA release needs a way into production, and a plan for the moment something there behaves differently than expected.
Read about operationsNew posts appear here when we have a thought worth sharing that helps with a real software decision. There’s no publishing quota. Your backlog is full enough already.
How we think