HN Reader

Can't read this every paragraph ends with it's not x it's y. Just give me the prompt so I can read the real insights you have and not the generated fluff.

I saw someone use the term "orchestration", which seems to be the word for building the software using LLM tools.

It made me think of the conductor, seemingly the most skillless job in the orchestra. All you do is wave the batton, no need to ever play a instrument. If LLMs are doing the hard part (writing code) then we can be the conductor waving the batton.

But of course the visuals are misleading. Being conductor doesn't take the least skill, it takes the most. He hears every instrument individually, he knows the piece intimately, and through his conducting brings a unique expression to a familiar work.

LLMs have made the musician part automated. They'll play whatever you want. No doubt a powerful tool in the hands of a skilled conductor. And a incredible tool for someone who can't play to generate music for themselves.

There's no shortage of "I built it and they won't come" posts here on HN, predating LLMs by decades. Because code has never been the hard part of "software as a business ". LLMs have driven this point home. Code has never been cheaper. Business has never been harder.

The "barrier to entry for building software" has not collapsed, as it was never about "where engineering shifts from writing code to shaping systems". It has always been about understanding the problem to solve and doing so in a provably correct manner.

Another way to reify this is:

  When making software, remember that it is a snapshot of 
  your understanding of the problem.  It states to all, 
  including your future-self, your approach, clarity, and 
  appropriateness of the solution for the problem at hand.  
  Choose your statements wisely.

We are all fashion designers now. LLM can code the cloth, do the seams, put in zippers, and sow buttons. You pick what creature you are designing for. You study how it moves, where the limits of movement lie, where it needs ventilation, flexibility, extra reinforced knees, fire resistance, a cape for flare (or no cape for safety). We are all Edna Mode. And the best of us can turn the problems we are working on into superheroes.

You model inference provider and any intermediaries get to watch what you’re designing from behind the curtain and copy, train on, or sell the insights if you’re not paying attention.

> People are increasingly building tools to solve a single, specific problem exactly once—and then discarding them. It is software as a disposable utility, designed for the immediate "now" rather than the distant "later."

Yes! This is 100% it.

This is a net good for everyone because it brings basic programming literacy to the masses and culls a lot of junk projects that are littering github or SaaS scams.

It means people can focus on the problems that actually matter.

AI doesn't have any impact on the need for accountable humans to write code.

The scratchpad analogy is so good. Most mature business software is almost literally like a tome of legal documents that have to be edited carefully, but that doesn't have anything to do with the napkin in your pocket.

This is a massive shift.

So many nice blogs showing on HN, and no RSS feed. Seems like most are on github pages, that should be a feature over there.

Turns out taste and judgement still matter. Weird.

solving problem should be an obsession rather than building. AI have fueled way too many builders while edge cases and lifecycle maintainence of the code is more of an afterthought

When you pay for anything you basically exchange money so that someone else take care of a problem you have. Obviously if you are paying you expect the result to be of good quality. Software is no different, AI won't change that fact and engineering is about creating robust solution at the cheapest price. Just my 2 cents.

> The barrier to entry has effectively collapsed.

Google, Apple, Meta, X, Bluesky, Shopify, Stripe and all the big software companies must be really shaking in their boots for disruption against the army of vibe coders. /s

(They are actually laughing at all of them)

If your job is to write code, you are being replaced. If your job is to use technology to solve problems, your job just got a lot more interesting.

Man. This post reminded me I wanted a Firefox extension for switching between tabs using Q and E. I got it done in like 15 min and moved on.

For the love of all that is holy, I cannot read another 5 page AI post that could've been like 200 words. Just make it a paragraph or two and write using your brain, people. Does everything have to be ran through an AI? I'm sure there's some decent ideas in here, but I'm not wasting my time reading this slop.

> The contrast with the traditional SaaS model is stark.

It looks like LLM-supported coding becomes the new SaaS. The more things change, the more they stay the same.

In other words, yes we have CNC machines and electric saws and whatnot, reliable to a certain degree (you can still injure yourself badly), but it doesn't remove the need of a carpenter, because a carpenter also knows how to make a hammer from scratch even if he doesn't make one in his entire life.

The cost of reviewing code is not cheap now.

This post is AI generated slop.

Keep in mind a gaggle of CC/Opus 4.5 agents is the worst this tech will be. How long ago did we hail 3.5 as the best? ATM, we are counting in months and weeks and the frogs are still leaping, and for all the naysayers, this has not yet slowed down.

Will the bubble pop and wipe out progress? Will this be a boon or bust for humanity? Who knows. In any case, the future's so bright, I gotta wear shades ;).