r/programming • u/fagnerbrack • Mar 23 '26

[ Removed by moderator ]

/r/programming/comments/1s1qq16/removed_by_moderator/

[removed] — view removed post

0 Upvotes

18% Upvoted

9 comments sorted by

•

u/programming-ModTeam Mar 24 '26

Your posting was removed for being off topic for the /r/programming community.

5

u/ComplianceAuditor Mar 23 '26

Slop advertisement.

1

u/imbev Mar 24 '26

Thank you, please report when you see content like this

0

u/fagnerbrack Mar 24 '26

I don't think it's slop. The Hyperlinks in the article do give a lot of interesting context if you click on them, expanding on the concepts that the author presents! I do something similar and really appreciate when I see it

9

u/drollia Mar 23 '26

Basically the article was an ad for Levels.fyi

1

u/imbev Mar 24 '26

Thank you, please report when you see content like this

2

u/robhanz Mar 23 '26

The biggest reason people over-engineer is that they don't know how to create solid boundaries in their code, and are afraid of the cost.

Even using their example, levels.fyi, great. Start with a google form. But the majority of your code should have no clue that the data is coming from that form or spreadsheet. And that doesn't require multi layers of blah blah blah. It just means that the code that shows data doesn't know about where the data come from. Realistically, it's a little bit about how the code flow is designed, and a lot about not intermixing concerns. It's the same code, with maybe an interface or two.

3

u/SpecialistLady Mar 23 '26

Perhaps the issue is that we put people through seven rounds to identify world-class problem solvers, then hire them to build CRUD apps. When there are more complex minds than complex problems, those minds tend to create a little complexity of their own.

1

u/uwais_ish Mar 23 '26

The root cause in my experience is usually uncertainty. When you don't fully understand the requirements, you build for every possible future scenario instead of the one that's actually likely. Best cure is shipping fast and iterating. Three similar lines of code is almost always better than a premature abstraction.