666
The Fall of Stack Overflow
(programming.dev)
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
Follow the wormhole through a path of communities !webdev@programming.dev
You lack vision, but I see a place where people get blocked and their questions opened then immediately closed as duplicates. Opened and closed, opened and closed all day, all night. Soon, where the internet once stood will be a string of condescending experts, admonitions that "you shouldn't do that, do Y instead", pleas for information closed as off-topic. Passive aggression, spiteful ego contests and wonderful, wonderful karma meters reaching as far as the eye can see. My God, it'll be beautiful.
That's one of my favorites: ignore the problem, only pick on the scope we can't change.
I asked for advice on how to express something in UML once:
"No one cares whether you follow the UML standard, just make something up"
"But my company uses waterfall and requires UML diagrams to move onto the next phase of development!"
"That's an issue with your company then. Ask your boss how to do it. Question closed."
It isnt even my problem and I still despair reading this.
You have to build Rust from source, then install the dependencies with cargo, then update your node.js because it uses npm to manage it's configurations and if your npm isn't at least the current unstable version, the configs will be outdated. This worked for me on Arch, which is what I use btw.
As someone who actually did out of interest at one point, you'd be surprised how easy this is to do.
x.py
is a godsend.For the rest of your comment, it was immediately invalidated when you said you use Arch. The reality is that more people use Ubuntu, so you should be using Ubuntu too. Don't use
apt
? Figure it out yourself :PI think it's a behavior from work got carried over answering questions in StackOverflow. Usually when there's a request from client/PM/PO, I usually ask them what they want to achieve by requesting said feature, usually after asking that question they will think and find out that making that pet feature is not the best way to achieve that goal.
As a Software Engineer we're conditioned to respond that way to a question, and when we go to websites that's specifically to answer questions, we are still answering questions from fellow technical people in that same mindset, which is not helpful.
However, I've used the condescending answers from StackOverflow to my advantage. Sometimes in a project we'll get businesspeople with a technical background, either they used to be an engineer 15 years ago or they studied computer science in university but transitioned to product management after graduation. If they are really insistent on some technical detail, I usually created a StackOverflow question based on their request and show them all the comments telling how stupid that idea is.
Heh. Easy there, Satan. But I do like how you weaponised S.O ;-)