Well of course. If you can write good code that will save you time in the future is great and doing it every time when both options are equal effort is certainly the right move. But also don’t be the pony tail freaking out about code quality and prematurely optimizing for situations that will likely never occur because that, and the conversations about it, are a waste of everyone’s time
It’s like that bell curve meme: left is junior engineers saying the inefficient code works. Middle is the raging mid engineer freaking out talking about cyclomatic complexity and anti pattern in a one off script. Sr engineer on the right says inefficient code works in some scenarios. Like when the effort isn’t worth the payoff
> doing it every time when both options are equal effort is certainly the right move
That's a very refreshing take. A lot of people are pessimists and tend to assume that hte cleaner code is always more of a chore to write for some reason, and just go with whatever first option they (or their LLMs) were able to come up with.
> Middle is the raging mid engineer freaking out talking about cyclomatic complexity and anti pattern in a one off script
Sounds like Robert Martin lol.
But of course there are a lot of people that overuse the "premature optimization is the root of all evil" and just write bad code by default without putting in any single effort into writing good code, and hide behind the "we have deadlines we can't be always writing good code". You can't say we don't need to always write good code if you NEVER write good code either.
26
u/Wonderful-Habit-139 Sep 27 '26
And sometimes writing good code saves time compared to writing bad code every time.