I get your point, but you also have to account for developer time.
Those miliseconds you can shave, how much developer time later on does it generate in technical debt?
There is a point where developer time would be less than whatever the gains are in performance, but that isn't a reality for most people, in most cases and in most applications.
Saving dolars in performance when you waste hours and hours of developers making 6 figures isn't a good trade off.
Time and time again, a cleaner code is shown to be better in the long run as far as developer time spent is considered. And as you said: the important thing is to put out value.
Finally, a MVP should be disposable, so it doesn't really matter because it's something for a sprint and not for a marathon.
There is not a single person on my one person team that makes six figures :) But I get your point and agree that any team manager who didn't consider such things would be considered negligent.
My point is that for people such as myself who develop alone, you are the team, you get to decide what rules/policies/guidelines/coding style you want (or not) to enforce.
Being a lone wolf developer, I have realized that no one looks at my code but me, no one gives a crap about my code but me, so why am I following all these rules when I don't have to and instead write my code, my way, the way that makes sense to me.
And yes, all this rampant rule breaking has made coding fun for me again :)
Follow the rules, Don't follow the rules, it's a choice not a requirement.
I get your point, but you also have to account for developer time.
Those miliseconds you can shave, how much developer time later on does it generate in technical debt?
There is a point where developer time would be less than whatever the gains are in performance, but that isn't a reality for most people, in most cases and in most applications.
Saving dolars in performance when you waste hours and hours of developers making 6 figures isn't a good trade off.
Time and time again, a cleaner code is shown to be better in the long run as far as developer time spent is considered. And as you said: the important thing is to put out value.
Finally, a MVP should be disposable, so it doesn't really matter because it's something for a sprint and not for a marathon.
There is not a single person on my one person team that makes six figures :) But I get your point and agree that any team manager who didn't consider such things would be considered negligent.
My point is that for people such as myself who develop alone, you are the team, you get to decide what rules/policies/guidelines/coding style you want (or not) to enforce.
Being a lone wolf developer, I have realized that no one looks at my code but me, no one gives a crap about my code but me, so why am I following all these rules when I don't have to and instead write my code, my way, the way that makes sense to me.
And yes, all this rampant rule breaking has made coding fun for me again :)
Follow the rules, Don't follow the rules, it's a choice not a requirement.
Happy Coding
You do you =D
And for toy projects, no one really cares.
But for projects that are "marathons", even working alone, there are things you can help your future self with: dev.to/noriller/im-stoopid-so-i-co...
At least it's what I do.