Live data from Hacker News

After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

arstechnica.com

11–20 of 37 posts

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#11
post #9

Well, I have all the sympathy for the SO people who are stressed out over losing their jobs... but at least a LLM doesn't chew me out when I ask a question that's remotely similar to one asked 7 years ago. And I like the low-latency, interactive rubber ducking experience way better than the slower turnaround on a SO question.

Wait Stackoverflow employees chewed you out?

Not the employees, the community

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#12

Seems poorly correlated. It seems unlikely that any significant number of developers quit using SO in favor of blindly trusting ChatGPT. More likely - advertising revenue declined in line with the reduced ad spending across the industry, largely due to expectations of economic recession by ad buyers.

> It seems unlikely that any significant number of developers quit using SO in favor of blindly trusting ChatGPT.

Most people I know have done exactly that.

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#13

Seems poorly correlated. It seems unlikely that any significant number of developers quit using SO in favor of blindly trusting ChatGPT. More likely - advertising revenue declined in line with the reduced ad spending across the industry, largely due to expectations of economic recession by ad buyers.

Well chatgpt reduced my usage of SO with around 90%.

For the simpler questions it is quite ok. As in write me x in language y where those are inputs

SO is left only for really hard or niche one.

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#14
> While no chatbot is 100 percent reliable, code has the unique ability to be instantly verified by just testing it in your IDE, which makes it an ideal use case for chatbots.

Oh, this is so wrong. Code is not instantly verified by any IDE except for things like syntax errors and compiler warnings. SO critique comments under each answer are so more valuable in that sense, it's not even funny. Every time I give feedback on ChatGPT's proposed answers it tends to go into incredible rabbit holes and endless recursion, reminiscent of WOPR playing tic tac toe.

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#15

Seems poorly correlated. It seems unlikely that any significant number of developers quit using SO in favor of blindly trusting ChatGPT. More likely - advertising revenue declined in line with the reduced ad spending across the industry, largely due to expectations of economic recession by ad buyers.

> It seems unlikely that any significant number of developers quit using SO in favor of blindly trusting ChatGPT.

I did to a large extent. If verification is easy(which in most of cases it is), I first ask the question to GPT 4 before searching SO. And tbh I have found SO top answer to be more probability of being wrong than GPT 4. In most of the code, if the code doesn't look wrong and could pass the testcases, which I use GPT 4 to generate and verify manually, it is likely fine.

Also there is a huge difference between GPT-3.5 and GPT-4 so if you have only tried GPT-3.5, you experience will differ wildly.

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#16

Seems poorly correlated. It seems unlikely that any significant number of developers quit using SO in favor of blindly trusting ChatGPT. More likely - advertising revenue declined in line with the reduced ad spending across the industry, largely due to expectations of economic recession by ad buyers.

My usual flow went from “do two or three searches with slightly modified wording, land on SO or the official docs of whatever I’m struggling with” to just “take a few minutes to explain the issue to ChatGPT, get actionable and mostly correct advice”.

For me, ChatGPT has unlocked an entire class of questions and investigations that would be almost impossible to handle with just search.

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#18
I used to relay on SO, still do sometimes but most problems seem dated. And with quality of Google search declining, getting to the core of a problem takes too long.

I used to relay on GitHub issues but github.com way too slow and quality of search is abysmal.

So more and more when in doubts I just read source code. Seems fastest.

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#19
post #18

I used to relay on SO, still do sometimes but most problems seem dated. And with quality of Google search declining, getting to the core of a problem takes too long. I used to relay on GitHub issues but github.com way too slow and quality of search is abysmal. So more and more when in doubts I just read source code. Seems fastest.

*rely

Re: After ChatGPT disruption, Stack Overflow lays off 28 percent of staff

#20

Seems poorly correlated. It seems unlikely that any significant number of developers quit using SO in favor of blindly trusting ChatGPT. More likely - advertising revenue declined in line with the reduced ad spending across the industry, largely due to expectations of economic recession by ad buyers.

My SO usage is massively down since ChatGPT. Probably 95%+. This is not a surprise to me at all.
Post reply on HN