The questions the Hacker News community asks, and honest answers from experience: careers, tech, life in the industry.
An Ask HN thread of 665 comments put the question to OpenAI. One answer: the labs need revenue now, and selling tokens through long-running agents is the only thing that is provably growing.
A rival answer: the models are not good enough yet, and a fully automated business at scale would be a landmark nobody has delivered.
He follows the four-weekly PHP release cycle and compiles from source, so he wanted to warn people like him to update. The disclosure schedule changed after his post.
A commenter's rule: if you got the vulnerability details without the embargo, someone upstream broke it, not you.
An Ask HN thread asked how engineers cope with shipping LLM-written code they haven't fully read. A Hasura engineer says his own system became fuzzy once he moved from IDE autocomplete to Claude and Codex CLIs, and argues the answer is formally verifiable code.
The loudest counter: you already ship code you haven't read. Principal engineers always have.
Forgejo and Codeberg kept coming up for people who want a lightweight forge they can host or use as a public service; GitLab was the answer for organizations that need a familiar enterprise-shaped platform.
The useful distinction was not hosted versus self-hosted. It was whether a team needs GitHub Actions and App integrations, or merely Git repositories with dependable CI.
Users reported failures across Microsoft services and pointed to GitHub’s long-running move toward Azure; neither observation alone established the root cause.
A second explanation was load: commenters cited rapid growth in commits and new accounts as AI-assisted development turns GitHub into a much busier system.
Several HN readers described abrupt account locks, weak support, or similar takeovers at other registrars. The recurring advice was operational rather than ideological: use domain privacy, keep recovery information current, and make a migration plan before an emergency.
The thread also undercuts the easy explanation that one company is uniquely broken—social engineering remains a human process wherever a support channel can reset access.
The post itself was simple: was anyone else's AWS bill suddenly showing nine or ten extra zeros? Hundreds of replies said yes, from a $286 million alert to one account reading a flat $109 billion.
The most surprising part wasn't the bug itself: AWS never sent a direct alert about it. Users had to stumble onto a single line buried on the AWS Health status page to learn their multi-billion-dollar bill was fake.
section33 (who runs an SRE and bespoke-tech consultancy on the side) tore out his bowling alley's original scoring hardware and rebuilt it lane by lane with off-the-shelf microcontrollers, open-sourcing the whole project as OpenLaneLink.
The sharpest pushback in the thread wasn't about his code — a longtime DevOps engineer argued the vendor's price was never really about parts: it buys a phone number to call, and a lane fixed in an hour instead of a weekend, when it fails mid-league night.
The OP wants to know what workflows others have found — and confesses he hasn't hit flow state with an LLM the way he can hand-writing code. That confession becomes the thread's real subject.
Two camps form: builders showing off homemade orchestration harnesses (one runs three autonomous agents that open their own PRs), and skeptics arguing the flow loss is inherent to a passive 'manager' role — and that most orchestrators are just an elaborate way to burn tokens.
One camp says nothing built with an AI exceeds what its operator could have built alone — the CS background is what shapes the prompt, and “knowing Dijkstra by heart” matters less than architecture. Another says the comparison was settled years ago: outsourcing to an LLM is the same trust trap as outsourcing to a dev shop.
A developer in China reframes the cost worry entirely: a $4,699 box already runs a smarter model locally, and a new state-of-the-art lands every two months.
The recurring diagnosis: the bloat is architectural, not algorithmic. Bundling Chromium to ship a chat app is the problem, not your choice of data structure.
Where optimization will actually happen, per a big-tech engineer in the thread: server-side, where RAM is a line item, and mostly by 'stop doing stupid stuff', not fancy algorithms.
A simple Ask HN prompt pulled a remarkably consistent set of fears: jobs, wealth concentration, and AI as a curator of what you're allowed to know. The single most common one-word answer was just 'AI.'
What made the thread sharp wasn't the venting — it was one founder, ex-Amazon and Apple, who kept replying to each despairing comment with a concrete question: 'If you could improve one small thing about your government, what would it be?'
The closest anyone gets: GLM and Qwen run agentically on self-hosted boxes and feel near Haiku, but the thread's experienced voices agree none of them reach Opus 4.8 or GPT 5.5 for real work.
The most-upvoted reply isn't an answer, it's a complaint about the genre: 'I use Qwen and get great results' tells you nothing without the quantization, llama parameters, context window, GPU and VRAM behind it.
The standout pattern isn't 'AI side-project' — it's the backlash to it. A search engine you can download the source of after 12 months as a paying customer. A baby tracker with zero analytics and on-device-only data. A publishing platform with 'strictly human content' and no algorithm.
And the deep cuts: a JVM written entirely in Go, a formally verified motion planner using arbitrary-precision math to fight numeric instability, and Magic: The Gathering played over webcam with whole-frame card detection.
The thread reached for David Graeber's "Bullshit Jobs" and a Civilization line about bureaucracy expanding to fill its own needs. The metrics people game — lines of code, PR count, hours in the building — got named as the cause.
The counter that kept it honest: small companies aren't a clean escape. Startups have their own perverse incentives, built on VC math and founders' whims.
The carve-outs — 30-day retention, exceptions for safety investigations and legal requirements — read as reasonable in isolation, until you remember teams send proprietary code and customer data through these systems.
Two EU practitioners flatly disagreed in the same thread: 'This is not going to fly in EU' versus 'Yes it will — clear purpose, customer agrees.'
Ries argues founders obsess over strategy and org charts while ignoring the deeper layer — structure, governance, boards, the relationship with investors. That's where missions die.
The AMA's funniest moment was self-inflicted: he linked a site he'd had Claude Code build to 'summarize' his book tour — and readers pointed out it had built a marketing page with no summaries in it.
The one use case everyone names is a giant private movie screen, especially while traveling. Almost no one cites a killer 'spatial' app.
The dealbreakers repeat: weight and neck fatigue, plus text that several owners call 'half-Retina' and unusable for real work.
The sharpest divide is owner-versus-owner on the exact same setup — a daily joy for one, a 10-minute novelty for the next.
The thread's unifying insight: Ticketmaster's real customers are venues, promoters and artists. The fees let artists keep a 'fair' face price while TM absorbs the hatred and funnels the money back.
An ex-competitor laid out the moat: a chicken-and-egg content problem, and incumbents who'll sign big venues at a loss just to deny you the catalog.
Pearl Jam tried to route around it in 1994 and got turned away by contract-locked venues.
The premise itself got contested within minutes: HN isn't anti-AI, several high-karma voices argued, it's anti-hype — the same reflex that met cryptocurrency. Others said the venom is real and specific, because this is the one technology aimed squarely at the people reading.
John Nagle's reply didn't bother with the framing question: many people reading this, he wrote, will be making far less money in two years; some unemployed, some homeless.
An open question on Hacker News asked engineers for the exact instant the ground shifted under them. The answers split clean down the middle: the moment something felt like magic, and the moment something felt like a threat.
Simon Willison points to a CSV dropped into ChatGPT in March 2023 that quietly did everything his data-journalism software did. A FAANG-adjacent academic's moment was deciding whether to fail a student for an LLM-written dissertation. Same technology, opposite gut reaction.