Hey everyone! I'm a junior developer trying to dive into the world of software architectures and methodologies, and I've got a few questions. Do big companies stick to strict architectures, or does it vary by project? How do they keep their code structured over the years? I'm also curious if there are any well-known IT products with messy source code. Lately, I've been freelancing and noticed that using MVC in expressJs can lead to bloated models (basically just functions handling raw MySQL queries). Now I'm exploring Service layers, DTOs, and more structured frameworks like NestJS and Adonis. I feel like it takes time to choose and implement the right architecture, and I'm wondering if making mistakes and refactoring while on a tight deadline is the best way to learn. Are there any resources or frameworks that might be better for me at this point?
3 Answers
You know, every big codebase has its fair share of messiness. Take Microsoft Excel as an example; they had a major recalculation bug that took them ages to figure out, leading to band-aid fixes. So, there’s definitely a chance that the code behind critical financial software is a bit of a 'ball of mud.' Don't worry too much about it; it’s pretty common, and even big companies deal with technical debt.
Exactly! Just remember, refactoring is key. Even the big players have messy code, but they learn to manage it over time.
When it comes to architecture, there's really no one-size-fits-all solution, especially in larger projects. Keeping the code clean over time is hard—more contributors usually means more chaos. Solo projects can stay structured easier, but company projects require strong technical leadership to maintain order. Learning by doing is essential; reading about design patterns is helpful but applying what you learn is what builds real understanding.
Ugh, so I really have to mess up before getting it right? That’s a bit daunting since I keep worrying about every little change I make potentially breaking something.
Totally get it; it's a steep learning curve. But don't sweat it too much; trial and error is part of the process. Just keep at it!
Honestly, don't get too caught up in the theoretical architectures. In the real world, messy code is everywhere. Just focus on coding, learn from your mistakes, and gradually refine your skills. There’s no perfect system, just keep experimenting!
Interesting! So, does that mean that even the giants have spaghetti code, yet they manage to iterate without major issues? It's kind of comforting to know it's not just a solo developer's burden.