8 months ago
Thurs May 30, 2024 1:41pm PST
Ask HN: How do I stop being obsessed with software architecture?
So, I'm an experienced dev with more than 10 years of experience. I do mostly web development.

Every once in a while, I catch myself obsessing about architecture. It usually goes like this: I got some free time, I start to think that my current code sucks and that I need to rewrite it "the proper way".

This usually means proper separation of concerns, layers, abstractions and what not. I'd go crazy with that. I get troubles sleeping, I get very stressed mainly because I want to do it quick so I could go back to actually adding features and fixing bugs.

This mainly apply to my side projects, as at work I rarely have the luxury to rewrite stuff or introduce big changes. But it's really bothering me. For example right now I have an app that makes some money and I want to scale it by adding more features. But I got caught into this architecture obsession and so I want to rewrite it because right now there are no abstractions whatsoever. HTTP requests comes in, I do raw sql queries and get shit done. But I want to make it nice, have clean architecture, onion architecture, proper domain layer. But none of this matters. It's a one man show, and it works.

And yet, I got stuck in this mode for the past couple of days, and I can't seem to get out of it. The sad thing is that I start the refactor, realize midway that I did not think it through, waste a day of my life, go to sleep, and repeat the same tomorrow thinking that I have found a "better way" to do it, just to make the same mistake again in a different place.

How do I stop being obsessed with software architecture and actually focus on getting shit done?

comments:
add comment
loading comments...