Log: porting the legacy config
(written in the morning, published later)
06:09 - GOOD MORNING!
Sleep broke around 4:30 and I have not been able to go back to sleep since. I don't know why. I had water and I had more water. But that wasn't it. I opened the window and it was the same case. So I don't know why I woke up but I have been awake since.
I have been thinking about this since yesterday, about this identity collapse thing.
And it made me realize that, in CS terms, I have been trying to refactor a legacy code base all at once and when ever a change is made the system fails in production. The same applies even if smaller targeted refactors are done. Fundamentally, you cannot outrun the system configs stuck on 20 year old versions and technical debt
For any meaningful change, you must slowly, painstakingly and deliberately port the old code to a new modern programming language. Focus on the port for now, I can apply optimization patches later. The new programming language should enable greater flexibility going forward.
Now the next question to answer is how I can port it and what is the acceptance criteria for the port.
Reach me at: b0.p3m1w@slmails.com