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

Is there a version of this "article" not written by AI? Feels like this was just an AI scraping twitter and writing an article.

It really took ages to get anywhere. Even the section explaining how the hack happened left me non the wiser.

Basically, bit-rot-ly missed up by deleting old link names when deleting accounts; people now register old links and redirect them to wherever they want.

What project is closest to doing this today?

It's possible "tech companies" die as tech no longer becomes a differentiator. Businesses will just ask their agents for whatever tech they need.

And the frontier labs themselves are hiring a ton.

What are you doing with your subagents? I find that as long as I use Opus at the top level and Sonnet/Haiku for subagents I generally don't run into usage limits.

We never risk using Sonnet or Haiku. Too many mistakes. The cost is worth it to always use Opus 5.5 even in the subagents.

Do you think this was a human choice, or one of those subtle Claude choices you don't notice until it bites you?

I'm sure the answer will be to update AGENTS.md to not do this particular thing, expose email in this way, which isn't the same as having sense.


I think none of these dolts have any idea what claude code does.

What do you mean by "solved"?

You don’t need to write anything by hand at your run of the mill tech job.

Ah, I think some people who say "coding is solved" implicitly also mean "you don't need to read the code that AI generates". It's not a super clear proclamation, but it is certainly provocative!

You really don't need to.

Between Opus 5.5 + GPT-6.1 Sol reviewer, most issues and unhandled edge cases are caught during implementation.

Then you QA test and provide the feedback.

I guarantee that this is enough to produce not only a working product, but is well capable of building apps much better than what is out there, without ever looking at the code.

Depending on your product and risk tolerance you may disagree. I believe that for the vast majority of use cases the approach I described, combined with extensive manual testing, is entirely adequate.


I run a solo SaaS that is closing in on $500k ARR, so I have real skin in the game here, and I agree with you. My experience of writing code with agents over the last 18 months in particular has been a steady erosion in my need to read the code. There are still a few parts of the codebase I'm particularly cautious about doing code review on, and I spot check PRs outside of that, but Opus 5.5 + Sol / Astra / Fable for reviews has been another paradigm shift. I don't think I"ve opened my IDE in weeks at this point.

It's worth noting that I also have a lot of guardrails and custom tooling around my own process to check code quality, QA functionality, limit blast radius of bugs, add observability, make deployments and rollbacks quick and low risk, etc.


I have solopreneur friend in a similar situation. I think solo businesses are another interesting case and in many ways a special case, because one person takes responsibility the entire business. Working in a large organization, one sticking point I see with AI is that it is very easy to externalize the cost of bad AI usage onto another employee or team. That problem doesn't exist in solo ventures.

I'm not sure if this means we will see smaller and smaller firms as a sort of market darwinism rewards good AI use by solopreneurs, and as large organizations tear themselves apart, or if we see the way big firms hold people accountable for their work change dramatically.

I also wonder what happens to these solo-businesses as they need to hire their second employee. What goes from a personal workflow will need to become a business process. I bet a lot of solo operators will resist employee #2 at nearly every cost!


Haha, it's funny you mention that: my goal is to never hire a second employee. I want to see how far I can go with just me + agents.

I bet a lot of solo folks are thinking along the same lines. I'm curious how it influences the shape of these enterprises. I imagine that if something can't be done with AI, or can't be bought, it won't be done at all.

Of course, if your objective is simply to make money, this might be relevant. You can also make quick money by polluting the environment, or being devious, or... there are many more direct ways to make money.

If you want to provide a good, secure, user-empowering, performant product, you cannot delegate everything agents, I assure you. And, building your foundation on un-reviewed mess of code will come back to bite you (partly depending on how big you grow), the same way it does with humans, which management always think is not an issue until it becomes one.

Now, you don't have to take my word for. Think of this: why is every change to Claude Code making it worse now? It is not almost unusable for me after many regressions over past hew years in its UX. Is it because of a lack of AI being used in its development?


On what basis do you assure us that?

Because by my estimation we did build our products in such a way and have that experience, while you presumably did not.

As for Claude Code, they recently delivered a significant upgrade to the desktop app where some commented that it felt like they upgraded Opus 5.5 to 5.6.

It's in fact working great, and the days where it was buggy are in my view in the past.


I mean...yeah, my objective here is to make money. It's a business. It provides for my family. I find it humorous that you feel the need to diminish it and compare it to polluting the environment or being devious, but you do you.

As for the rest, I assure you that the product is much more performant, secure, and delivers far, far more value to my users than I ever could have done prior to AI-assisted coding. And I'm a staff level engineer with 25 years of coding experience across all kinds of organizations. I'm not the best coder, but I'm at least decent. AI has been a massive force multiplier for me, even as I agree that it's not perfect.

Unpacking a little more, I think the area you might be running into issues with is the idea that because I rarely open my IDE, I'm "delegating everything to agents". I'm really not. I review PRs (just not in my IDE), I steer higher-level abstractions in the broader system. To me, automated coding with a frontier model is definitely good enough that it's utterly pointless of me to read the internals of 99% of functions, even classes. Assuming the inputs are correct, the agents will get those details correct. And for the tiny fraction of the time when that's not the case, that's why we have adversarial review, guardrails, tests, o11y, quick rollbacks, etc, etc. Working at the level of how the broader building blocks of the system fit together, bisecting the software into low / medium / high risk areas so I can direct more of my scarcest resource (my attention) towards the highest ROI portions, and building the infrastructure (the "software factory") that the agents work within building and improving the product is where I can add the most value in November 2026.

Have you ever worked in a bigger tech company with tens of millions of lines of code and senior staff / principal engineers? In my experience, sure they're reading and writing code here and there, but that's not the value they provide. The value they provide is the broader architectural view of the systems and how they fit together. It's no different with AI.


OK, then we are mostly in agreement. It does not sound like you are completely vibe-coding your way around.

We may differ in the level of review and steering we do a bit. I have worked in codebases approaching a 1 million LOC, and I am now working on a suite of products and libraries in a monorepo that would be the flagship products of my own small company.

I have defined a strong architecture, guardrails, and a way of working that the agents keep to. I approve almost every single edit they do in the terminal, but most of the time I do not have to read each line, because they are good enough. Every now and then, I catch them doing something egregious, and I correct or redirect them. Other times, they stop to ask me for direction. Still, I am faster and do more work with the help of the agents.

So, no I'm not saying the agents do not provide value; they help with a lot of grunt work, and they can write most code basically correctly. Where I am firmly still in the driver's seat is with architecture, UX, quality control, product invariants and standards, and the occasional tweak to lower level implementation details. These remain a lot of work, unless you are simply building CRUD forms.

This does not sound like "coding is solved". If coding is solved, then I can one-shot a complex software product into being, which is never going to be the case.


That's the most natural interpretation IMO.

That is not at all what "solved" means! If you're still reviewing and re-prompting, it is not solved by a long way.

That’s where we disagree. Feel free to continue refining meaning of “solved” while I chill on HN while my agents are working.

Hopefully I'm not using any of the software you are 'working' on.

Unfortunately for you, you probably do at some point.

Would you mind telling me what it is? Asking for a friend.

Most people I've seen saying coding is solved are ML engineers who write throw away code for running one-off experiments. If you can effectively "archive" code after getting the results you need, I can see why you would say coding is solved. Sustainment is a non issue.

yes and web people who are just gluing together api's or writing what essentially amounts to UI templates that can never really be "wrong"

I'm lucky I guess, I feel like the product team is on "my side" with respect to building a resilient system. They understand that bad architecture shows up as a fragmented and friction-full UX.

The demand for new features come from sales and executive people who want to check more boxes on a customer's checklist.


Ultimately your paycheck exists through deals that involve those boxes on checklists. It doesn't simply materialize out of thin air. If there are no deals, it doesn't matter how robust and elegant the architecture is.


My anecdotal experience has been that is is very reliable on inputs over 500 words. There are a number of third party evaluations that corroborate. Pangram is pretty easy to test for yourself if you are a skeptic.


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

Search: