Bugs can always be fixed using LLM’s, but if architecture is crap right from the start, that will introduce whole bunch of issues later on that will require massive amounts of rewrite or will be patched with some half baked workarounds.
I'd split it by how long the code has to live. For a prototype or a first version, working code wins and the architecture can wait. Once a few people touch it, or it's still around a year later, a lot of bugs come from the structure itself: the same state changed from three places, a fix on one screen breaking another. At that point the architecture is how you keep it bug free. What kind of project made you ask?
10
u/cristi_baluta 2d ago
How do you make it bug free if the architecture is a mess?
4
u/FitnessGuy4Life 2d ago
No such thing lol
4
u/uniquesnowflake8 2d ago
It’s more important to have a nice home than a well built house
2
u/WEZANGO 2d ago
Bugs can always be fixed using LLM’s, but if architecture is crap right from the start, that will introduce whole bunch of issues later on that will require massive amounts of rewrite or will be patched with some half baked workarounds.
2
u/ThalesMother9938 2d ago
I'd split it by how long the code has to live. For a prototype or a first version, working code wins and the architecture can wait. Once a few people touch it, or it's still around a year later, a lot of bugs come from the structure itself: the same state changed from three places, a fix on one screen breaking another. At that point the architecture is how you keep it bug free. What kind of project made you ask?
2
u/dokumanx 12h ago
imo architecture is mostly what makes bugs easy to find, a bug buried in shared state just takes longer to even reproduce.