Cut corners, remove features and sacrifice quality. Pretty much what I do in my hobby projects.
this post was submitted on 18 Jul 2025
-2 points (44.4% liked)
Programming
21711 readers
66 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
That's... too realistic.
How a lot of software development ends up in real life too.
Don't go crazy about abstraction.
Sometimes it's better to write some code twice than expending two weeks trying to make a fit-all new class with 50 interfaces.
Sometimes you should do that, but for many projects that level of abstraction is not needed.
Well, the writing-part isn't the bad part about duplicated code. It's the maintaining of it. In particular, if you duplicate logic, it happens all too quickly that you make modifications to one, but not the other, or you make differing modifications to both.
Eventually, you'll end up with two wildly different versions, where you won't know why certain changes were made and not applied to the other version. Similarly, if you do need to make a similar change to both, you might now need to implement it two times.
I guess, I do agree that it isn't *always* worth it, but in my experience, it is far more often worth it than one might think.
c/thanksimcured
This is a developer perspective that doesn't consider the big picture with security holes. And one of the reasons why software has gotten worse.
So, go agile?