this post was submitted on 14 Jan 2025
1 points (52.0% liked)
Programming
17921 readers
120 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 [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I read this as a claim that there is only two. Which seems to match the overall flow of the document, describing only two, and then arguing between those two as if only those two exist.
No, that's wrong. Especially those two bleak, described extremes. They're not the only ways to develop software.
What the heck are they even talking about anymore. Now one is the only feasible one. But then neither are.
Now, by the end, I have no idea what this was even trying to argue. Meant as entertainment, following two theoretical development process extremes? Formulating in the extreme to make a point? None of it seems to apply. No conclusion is made at the end, instead falling further into anecdotes and unrelated, far away equivalences that make the whole thing even more confusing.
That quote is hilarious to me, I guess they haven’t stumbled upon design patterns yet? I don’t even know who this blog is supposed to be for, there’s no name attached so I’m half guessing it’s more AI slop