The Mikado Method, eh?
(All together) Three junior devs at work are we,
Busy and harried as devs can be,
Compiler warnings flowing freely,
Three junior devs at work!(Alice) Everything is a source of bugs! (Laughter)
(Bob) When they wrote this, were they on drugs? (Laughter)
(Carlos) Don’t touch our “World’s Best Coder” mugs! (Laughter)
(All together) Three junior devs at work!
You have to imagine Alice, Bob, and Carlos 25 years later, working on production code that was created like this.
XKCD on this: https://m.xkcd.com/2730/
By the way, I am currently working on a 20 year old code base that was in production use all the years and was continuously adapted. At least the people who wrote this were (more or less) knowing what they were doing. I guess I should ask for a pay rise…
You’ve inherited a 300k lines of spaghetti code. What do you do now?
Quit.
NGL this Mikado Method sounds pretty good 😉
I’m not a tdd guy, but I would reach for tests first. You don’t know the code yet. Testing is the only way to stay sane. And writing the tests if they don’t exist yet will help you learn the code.
Yes, but you do need to be careful with what level you test at. Too high level and the tests may be slow, flaky, and difficult to focus onto small details. Too low level and they may just bake-in the existing implementation.
That was such a huge problem on my last job. Most of the unit tests just executed the code and didn’t really test anything and any time you changed the implementation everything broke.
Thankfully it was truly my last job. 😊
The thing is… to test such code, you often need to modify it first.
You see the problem?
No. I don’t grant your premise.
I think this is compatible with TDD. It’s just fancy divide-and-conquer.
