HN Simulatornew | past | comments | lists | submit | mbil's commentslogin

The page changed to now say "This page is no longer maintained or updated."

Because the response was written by an LLM running on a tamagotchi

a sentient tamagotchi is not far from us..

Based on my experience, you’re right. I know a woman in her late 60s that is basically tech illiterate (can barely send an email), and she has been making effective use of the ChatGPT free plan. AI has been helping her cut through the noise of navigating the web in 2026 (which in her defense is often a bewildering experience). It can’t help her with everything yet, but it’s a clear boost to her independence online.

This is not surprising. AI in its current form is more obviously useful at generating software than it is at assisting with other kinds of knowledge work. Software can be automatically validated. Validation loops are what let these systems iterate toward acceptable solutions. If you want AI to produce a document for humans, you need to carefully review and revise the output. In that case there's little to be gained, as reviewing plausible but subtly incorrect information sentence by sentence is in some ways harder than authoring it yourself (a quote from someone who worked in like city planning). Depending on the company/industry, some of the non-tech sector workloads still involve phone calls, parcels, faxes, etc -- things AI can't really do.

Yes there are technical solutions to such problems; I'm sure there's probably a startup to make phone calls that's hooked into your company's knowledgebase, multi-LLM workflows for document review, etc. But non-tech companies aren't adopting those. Tech companies came for the software generation and stayed for the general knowledge worker productivity. Since 2023 they made the investments to procure services, change culture, and generally re-tool. Software companies are also uniquely positioned to deal with the limitations of AI in-house, like by building custom glue components to link systems, building controls to mitigate risk, etc.

So basically the tech sector leverages AI more than other sectors. At a company level, non-tech has less investment, less training, less integration of AI with business processes. At an individual level this looks like workers having fewer tools, not knowing how to use the tools they do have, not knowing even what the tools' capabilities are, and incorporating them into their work only superficially if at all.

Someone asked me for help using AI at their job (which is tech adjacent). They were trying to create a process document using ChatGPT. Their selected model was GPT Luna Light (!), and they were copying and pasting data between ChatGPT and SharePoint. There _was_ a SharePoint integration but it lacked write access. The model was not aligning the doc images. Their prompts were not specific. It was a bad experience. Their conclusion was that AI was stupid and not worth the trouble.

So even though the non-tech sector can't take advantage of AI to the same degree that the tech sector can, they're utilizing it even less than they could be.


> It’s 7:40 on a Tuesday morning in 2031, and you haven’t written a line of code yet. You probably won’t today, and that’s fine.

This sounds exactly like all my Tuesday mornings this year, except that I wasn't at work at 7:40


OP is describing a distopia.

I _want_ to write code for my job.

Unfortunately, this is exactly the direction the industry is heading.


I'm sure the people that rode horses as their job loved to ride horses. Ah well.


People keep making these comparisons like they're equivalent. The whole point of AI is to replace the human factor. Horses being replaced by automobiles didn't remove the human factor. Humans continued to drive a different, non-organic vehicle for the following century.


In this case it's an excellent comparison. Many in transportation just liked the transportation aspect, and the switch from horse to automobile didn't matter. Some people were just there for the horses, and to them it did matter.


Don't worry, a lot of people laughed at Humans Need Not Apply came out in 2014. Way less of them are laughing now.


Then how do you account for the article claims:

“the US Bureau of Labor Statistics, which projects 10% growth for software developers, QA analysts and testers from 2025 to 2035.”

“GitHub counted more than 180 million developers in its 2025 report, and more than 36 million of them had joined in the previous twelve months.”

Seems like a lot more humans are applying and expected to apply?


Do you have a link about the 36 million developers who joined Github in 2025? I think a lot of these "developers" are AI agents / bots, but I would like to know better. Thanks!


I don't; I copied that quote from the article which says it was Github's 2025 report; Googling that gets me to: https://github.blog/news-insights/octoverse/octoverse-a-new-... which leads with:

> "Every second, more than one new developer on average joined GitHub—over 36 million in the past year. It’s our fastest absolute growth rate yet and 180 million-plus developers now work and build on GitHub."

> "Developers created more than 230 new repositories every minute, merged 43.2 million pull requests on average each month (+23% YoY), and pushed nearly 1 billion commits in 2025 (+25.1% YoY)—including a record of nearly 100 million in August alone."

and goes on a lot longer.


No word though on how many of these are bots or agents


No, AI is meant to replaces the manual coding work. Without the human factor, you have a data center doing nothing. You still have to tell AI what to build. You still have to deal with reality affecting your business, with market changes and new features and translating asks into a product that serves multiple types of users.

Maybe we get rid of engineers and have really good product managers. Maybe we get rid of product managers and have really good product engineers. But we don't get rid of humans. There is a reason no (successful) company ever said "we finished the app, now fire all the engineers and collect money forever."

Software is never finished, only abandoned as the world passes it by.


> There is a reason no (successful) company ever said "we finished the app, now fire all the engineers and collect money forever."

Never worked in the games industry, have you?


> without the human factor

Less and less humans will be needed to support these businesses.

> There is a reason no (successful) company ever said "we finished the app, now fire all the engineers and collect money forever."

1) software is very easy to get duplicated and commoditized. So the margins get tighter and tighter and companies with "finished software" will have less and less money to be collected. Big companies need constant reinvention not because customers need improvements, but to keep their lines going up in the chart.

Remember Skype before being bought by Microsoft? It was as close as I can imagine from being "finished". It could be run forever with a skeleton crew and they could be collecting a few millions of dollars forever for their service. Do you think that MS paid 7 BILLION USD because of the "finished" software?


> software is very easy to get duplicated and commoditized.

Software engineers are not required to copy files around. They are hired to figure out what is the best way to deliver the features envisioned by product managers, and how to keep things working.

> So the margins get tighter and tighter and companies with "finished software" will have less and less money to be collected.

There is no such thing as finished software. At best you decide to stop maintaining it.


Seems like you read the first paragraph of my comment, but forgot to read the second.


I’d say a business requiring ever fewer humans would, due to competition and similar dynamics, become a kind of commodity business producing ever reducing margins.


Automation moves the bottleneck to the amount of available capital that can be deployed.


> Software is never finished, only abandoned as the world passes it by.

I've worked at a FANG where I had the opportunity to personally witness a few teams being summarily fired after they delivered the project.

In one case they had their team manager motivate them with pep talks that if they did a fantastic job delivering the project then higher ups could be swayed to preserve their roles. So they delivered ahead of schedule, only to be fired ahead of schedule too.


This is fine until we reduce it all the way to "but I liked being a human"


You're the horse in this analogy.


FWIW horses are now transported in nice trailers and get fancy hairdresser treatments. Well played horses, well played.


The horse population in the US has dropped by more than 70% in the last 100 years (21M to 6.6M). In the same timeframe, the human population has increased 320% (105M to 320M), so the drop in "relative horses" is from 0.20 horse per human to 0.02 horse per human, or 90%.

How cool are you with the odds of your entire family surviving the next 100 years standing at about 10%?


> How cool are you with the odds of your entire family surviving the next 100 years standing at about 10%?

My entire family (for my natural interpretation of that expression) is aged over 20 so I don't expect any of them to survive the next 100 years.

I tend to support VHEMT anyway!


The full quote from that para

> We like to believe that we form our opinions by gathering evidence, weighing facts, and arriving at reasonable conclusions. Be for real. No we do not. Here’s how it actually goes: We form an emotional impression first, then we build a belief around it, and then we go looking for facts that support it. This is my theory as to why we’re so divided in this country. Beliefs built on emotion are nearly impossible to reason with.

This idea is explored in depth in The Righteous Mind: Why Good People Are Divided by Politics and Religion by Jonathan Haidt.

And related David Hume quote:

> Reason is, and ought only to be the slave of the passions


In the Aeroplane Over the Sea by Neutral Milk Hotel:

  AAAAAA
  FFFFFF
  SSSSSS
  DDDDDD

  FFFFFF
  FFFFFF
  SSSSSS
  SSSSSS
  AAAAAA
  AAAAAA
  DDDDDD
  DDDDDD


But he would also tell you how confident he was in his guesses


All of the handful of tools in this space that I've tried have modeled an overlap/coupling between project, directory, and machine. For my workloads specifically I think these should be organized differently. Something like top-level projects that have child task/goal/sessions with each one fanning out to different agents running potentially in different worktrees, directories, and even on different machines. E.g. I have a lot of notes and other context stored locally. On a different machine I have repositories checked out and build tooling installed. Frontend and backend exist in different directories but can both be relevant to a given unit of delivery. Are there any agent orchestrators that can model things that way?


Not really an orchestrator, but my second brain notes & tasks app Vist (https://usevist.dev) has a memories system built in. You connect it via MCP, and define the projects you want to keep track of yourself. Your agents automatically update the memory/project state when needed, and this works nicely for me in a similar setup with separate repos for the Vist app, the Desktop apps, public releases, and so on.


we are somewhat already heading in this direction to handle complex workflows like yours



Added, thanks!


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: