In part 1 we talked about naming as a process. We talked about how legacy code is really defined by its poor legibility, and that reading is the core of coding. And we talked about how working effectively with legacy code is simply the process of having an insight, writing it down, and checking it […]
Posts Tagged ‘legacy code’
Naming is a Process, Part 7: Intent to Domain Abstraction
Posted in post, tagged design, legacy code, naming, naming is a process, refactoring, tdd on October 5, 2015 | 2 Comments »
New code is legacy code
Posted in post, tagged design, greenfield, legacy code, refactoring, tdd on October 2, 2015 | Leave a Comment »
My series about naming as a process is really about design. It focuses on design in legacy code. That has sparked people to ask about new code. What about new code? Why not start with intent? I was taught to pseudocode or model, so that I could focus on the intent first. Then I don’t need all […]
Naming is a Process, Part 6: Does the Right Thing to Intent
Posted in post, tagged design, legacy code, naming, naming is a process, refactoring, tdd on August 28, 2015 | 6 Comments »
In part 1 we talked about naming as a process. We talked about how legacy code is really defined by its poor legibility, and that reading is the core of coding. And we talked about how working effectively with legacy code is simply the process of having an insight, writing it down, and checking it […]
Naming is a Process, part 5: Honest and Complete to Does the Right Thing
Posted in post, tagged design, legacy code, naming, naming is a process, refactoring, tdd on August 27, 2015 | 1 Comment »
In part 1 we talked about naming as a process. We talked about how legacy code is really defined by its poor legibility, and that reading is the core of coding. And we talked about how working effectively with legacy code is simply the process of having an insight, writing it down, and checking it […]
Naming is a Process, part 4: Honest to Honest and Complete
Posted in post, tagged design, legacy code, naming, naming is a process, refactoring, tdd on August 26, 2015 | Leave a Comment »
In part 1 we talked about naming as a process. We talked about how legacy code is really defined by its poor legibility, and that reading is the core of coding. And we talked about how working effectively with legacy code is simply the process of having an insight, writing it down, and checking it […]
Naming is a process, part 3: Nonsense to Honest
Posted in post, tagged design, legacy code, naming, naming is a process, refactoring, tdd on August 25, 2015 | Leave a Comment »
In part 1 we talked about naming as a process. We talked about how legacy code is really defined by its poor legibility, and that reading is the core of coding. And we talked about how working effectively with legacy code is simply the process of having an insight, writing it down, and checking it […]
Naming is a Process, part 2: Missing to Nonsense
Posted in post, tagged design, legacy code, naming, naming is a process, refactoring, tdd on August 24, 2015 | 2 Comments »
In part 1, we talked about naming as a process. We talked about how legacy code is really defined by its poor legibility, and that reading is the core of coding. And we talked about how working effectively with legacy code is simply the process of having an insight, writing it down, and checking it […]
Good naming is a process, not a single step
Posted in post, tagged design, legacy code, naming, naming is a process, refactoring, tdd on August 21, 2015 | 6 Comments »
Many people try to come up with a great name all at once. This is hard and rarely works well. The problem is that naming is design: it is picking the correct place for each thing and creating the right abstraction. Doing that perfectly the first time is unlikely. Let’s talk about evolutionary naming.
Fixing Legacy: What Should I Blow Up First?
Posted in post, tagged legacy code, refactoring, technical debt on October 16, 2012 | 2 Comments »
Another good question came over the wires at work. My reply grew too long and I figured more people would want to see it. Besides, this way I can blog and call it a legitimate business activity. Problem statement: what patterns and strategies work for choosing when and what to refactor? Does this change at […]
Paying Down Code Debt
Posted in post, tagged code debt, legacy code on September 18, 2012 | 8 Comments »
We have huge code debt. We want to pay it down. But we just can’t afford to this week (or last, or the one before that). How can we afford to pay down our debt? OK, it’s not a direct quote. But I’ve heard something close to that often enough that random word ordering may […]
