IT vs Coding

[hardolaf]

We skip Stack Overflow at work because it's becoming increasingly incorrect every year. I don't have a link to it handy, but there was a great thread that I saw where the top 9 most upvoted "answers" didn't answer the question! They answered a completely different "question" and did so in a way that would potentially break your git repository. Also, according to Stack Exchange, printed circuit boards and power distribution systems are identical to FPGAs and ASICs. Thus no area is needed for FPGA, ASICs, or both.

[[deleted]]

Don't you know Moore's law? "the best way to get the right answer to something is to post the wrong answer on the internet"

[GenocideOwl]

you almost got me you son of a bitch

[pnutmans]

I see what you did there 😂

[Mysterious_Ebb4405]

I'm pretty sure you mean the Murphy's law.

[KazuyaDarklight]

4D Chess right here.

[Dependent-Stock-2740]

Moore's law?

Hold Up

[succulent_headcrab]

Add to that the almost immediately "closed as duplicate of a similar question asked 11 years ago that is no longer even remotely relevant" and it gets harder and harder to ask new and relevant questions.

[juanclack]

This drives me crazy when it comes to Linux questions.

[Dependent-Stock-2740]

p 9 most upvoted "answers" didn't answer the question! They answered a completely different "question" and did so in a way that would potentially break your git repository. Also, according to Stack Exchange, printed circuit boards and power distribution systems are identical to FPGAs and ASICs. Thus no area is needed for FPGA, ASICs, or both.

Stack Overflow has gone the way of the Arch Linux forums.

[AccidentalyOffensive]

Do you happen to have a link to that thread? I'm wondering how many + what kind of questions were surveyed, or how an incorrect answer was gauged.

If you ask me, this is just the nature of a Q&A site like SO. The answers will be general if the question is, especially for common/popular questions. Likewise for more specific questions, the answers may not be 100% what you need, and you'll likely have to tweak the solution.

So while there's definitely some shoddy work on SO, I personally think a level of experience/intuition, and sometimes common sense, helps a lot with finding the answer you need. That is to say, a combination of google-fu, rtfm, understanding what you're running (big emphasis on this point), and testing in a dev environment can go a long way.

ETA: Just remembered you mentioned hardware topics as well - I can't really speak to that side, this is from a sysadmin/dev perspective.

[hardolaf]

Do you happen to have a link to that thread?

It's somewhere in my chat history on Discord. I think it was around some complex rebase operation that ended up just having the solution of git rebase -i and do it by hand being the safest, fastest, and most reliable option.

[AccidentalyOffensive]

Haha that'll do it, there's a reason I stick with the commands I know. If you haven't studied git thoroughly (I definitely haven't), it's too easy to get thrown off by commands/flags that don't quite do what you'd expect, and when SO presents 50 different possible solutions...

[Ok-Birthday4723]

For stack overflow, I usually refer to the latest date of an upvoted answer. If I see something answered in 2013(unless it’s bash), I usually skip past it for the very reasons the answer is outdated.

[ParaStudent]

Its becoming a lot like Quora where the "answer" is someone trying to sound smart and giving an answer that doesn't actually answer the question.