75
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Sep 2023
75 points (100.0% liked)
Programming
14035 readers
1 users here now
All things programming and coding related. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
What an utterly blind, self-centered view. Write good, readable code so you can actually maintain it and so your coworkers don't want to kill you.
I think vzq's point is that you can write good, readable code that doesn't do what the user wants. Same with other metrics that are ripe for navel-gazing like code coverage.
It's bordering on a false dichotomy... but I also believe that dynamic, untyped languages have proven exceptionally useful for rapid prototyping and iteration.
You're setting up a theoretically boogie man that no one said exists and then setup the extreme opposite point of view. You're annoying the people that are actually sane. You're being dogmatic in your one views and too extreme.
This is a shitty response. You won't make money if you design the app poorly and can't maintain it.
That sounds like bad business. No application is 100% unique in everything. Code reuse saves time. If you are unable to bring anything from one app to another, you're doing it wrong.
Let me guess though, I was right. You're a manager not a developer.
? I mentioned it twice. And you sounded like a manager a little bit in one comment, and then a lot in the followup reply to it. To the point it sounded like you were defending it. Making claims that developers aren't allowed to make the choice you were saying to make. So it was really weird. I don't even know how your stance makes sense from your point of view.
Edit: and thanks for ignoring anything of actual value to reply to.
Except that prototypes never end up as just prototypes, they die or become the real app with lots of masking tape.
If you can't see that writing readable code is part of the means to that end, I don't know what to tell you. If nobody can maintain the codebase because it's a mess of spaghetti logic and 20-deep dependency trees (I'm looking at you, every JavaScript project I've ever seen), the end product is going to suffer while also making every single engineer working on it want to leave.
Funny, it sure seems like "maintainability should not be a priority" is a pretty controversial take to me.
Then I'm really glad I don't live in that world.
Weird. In most cases priorities change as the situation demands. The application doesn't matter when it comes to maintainability. Tech debt will take down any application if you keep ignoring maintainability at the expense of just delivering more and more. You sound more like a manager than a developer.
Even their excuses if a “24h only event app” don’t hold water
Even in that case, a business would be wanting to make many of those apps, and this commenter is arguing making a new one from scratch every time over massively simplifying things with quality reusable code.
Even their own example shows how terrible it is an idea to deprioritize code quality/readability.
I guess they are running some kind of shovelware company with constant bluffings.
Maybe, but you can push it really far before the breaking point is reached.
But you can do that in vanilla JS, too.
Even better, don't use JS at all if you don't have to.
You can write shitty code in TS too.