3 ms·
I gasped when I saw this article at the top of HN due to the relevance of it right now in my life. I am currently working on a real monolithic jambalaya that su
by markatkinson 9y ago
I gasped when I saw this article at the top of HN due to the relevance of it right now in my life. I am currently working on a real monolithic jambalaya that suffers from a lack of documentation, architecture, extreme abstraction, rampant tight coupling and no previous source control.
Your point on performing architecture discovery and documentation is spot on. It has really helped me to strip away the mess and understand the flow of the logic and maybe even shine some light on the parts of code that are valuable.
- korzun 9y ago> I gasped when I saw this article at the top of HN due to the relevance of it right now in my life. You are not the only one :)
- xivusr 9y agoThis article is painfully relevant for me. I just reviewed a code base with zero tests, documentation, no inheritance- rampant duplication. It's a simple event tracking system and yet there are 75 models, and over 80 controllers. This was outsourced to a team which coincidentally appears to have close to that many devs working there. The good news is that according to the client "it pretty much works". I know better than to suggest a Big Bang - though it seems so appealing. Documentation and code freeze are my next steps and implementing end to end testing.