Member-only story
This article is written by our sponsor nautilus2k.com which is a new startup trying to help other startups building data-driven apps on the Microsoft .NET Core/ Azure tech stack.
I have not seen many engineers able to change vast amounts of code and still produce a stable output at the end of the day. But it seems to be a necessary capability to make evolutionary changes to software.
There is a tendency to keep changing the code to infinity, with the code never stabilizing. This causes no end of frustration for management because this is usually an engineer who is highly skilled.
I have always changed a lot of code for my projects. Some were originally written by me, and others were originally written by someone else.
One of my most cherished memories is implementing a variable to improve something, and after a week, finding that the founder of the company had completed what I had started (intending the same thing) and both our code could together complete the implementation he had started many years ago (he had left by the time I joined).
Even for Reactor, I have changed thousands of lines of code in three different versions, and even though I may debug and fix issues for a week or two, it always eventually stabilizes. It could be because I am focused on reaching a specific functional…
