This is the difference between "made in China" and "designed in California, assembled in China". People will generally not say "I constructed this table" just as an architect won't say "I built this house", unless you have the context that they're an architect or they're trying to mislead you.

There will come a time where by default we interpret "I built this software" not to mean that you literally wrote the code, unless you say that explicitly, just as when somebody says "I built this computer" we know it means they picked the parts, rather than soldered the boards, which is what it meant in Woz' day.

Karpathy said it best. To paraphrase: there will be a rift of hate/love between programmers and builders respectively. You simply enjoy the craft a lot more that you enjoy the result of your craft.

There's nothing wrong with that, just as you can enjoy the effort and craftsmanship of hand-knitting a sweater. But some of us are more fulfilled by making nice clothes, and the labour (or delegation thereof) is a means to an end.

Try it for yourself, use their website to explore some domains you might like and watch them register from right under you and price gouge.

The startups that decouple do so because engineers build agents with git, and non-engineers (lawyers/clinicians/etc) align agents outside of git.

So the problem of coordination and versioning shifts to out-of-sync docs and platforms.

This is why I built Gravel.

An open-source library that embeds a prompt editor straight into your app. Your prompts have a single source of truth (your codebase).

After a minute of setup:

1. Your team can make prompt PRs without knowing what a PR is

2. They can review outputs straight from your production traces

3. Those reviews create prompt change suggestions and evals

If you're building vertical agents, would love your feedback on it!

Comments URL: https://news.ycombinator.com/item?id=48280684

Points: 1

# Comments: 0

So to answer your first question, it's less about _reading_ and more about _doing_. The interfaces for humans are not always the best interfaces for machines and vice versa in the doing, because we're no longer dealing with text but dynamic UIs. So we can cut out the middle man.

As for coding, Karpathy said it best: there will be a split between those who love to code and those who love to build. I too enjoyed writing code as a craft, and I'll miss doing it for a living and the recognition for being really fast at it, but I can do so much more than I could before now, genuinely. We'll just have to lean more into our joy of building and hand-code on the side. People still painted even after the camera was invented.

What I'm saying is that the AI hype is making people make that business decision, and that is ultimately a good thing because it means more human accessibility. Not just for people with disabilities, but through interoperability and fewer silos like YouTube.

Same when it comes to staying on top of tech news -- almost everything is a flash in the pan. I used to bookmark cool new products, never revisit them, and then a year later realise half of the links are now dead.

One thing I realised though is I still need to mindlessly browse an endless feed every once in a while for some downtime. One way or another I'll want to fill that time with something, so it's a question of being mindful what goes in it. So my drugs of choice are Hacker News, and carefully curated YouTube subscriptions.

Before that I used Happy (https://happy.engineering/) which is also open source and a lot more sophisticated. It has a voice assistant that can chat with Claude Code on your behalf in the mobile app. However, it wasn't very reliable, and there are other reasons to use Hapi instead (documented in the Hapi repo).

Before that, Omnara (https://www.omnara.com/) a YC company and seemingly a proprietary Happy fork (?) but it never worked properly for me.

Long story short, there are a few of the around, and frankly I really like to use them. Unlike other commenters, I don't find that they wreck my work-life balance. Rather, I can go out and have a walk in the park, only checking in on long-running tasks every once in a while. The diff view is pretty good too. There are many tasks where I'd rather not stare at my PC all day and instead do other things, and these tools allow me to do that.

They also had good incentive structures for keeping the bar high -- you could get kicked out for having a bad ratio, so the easiest way to pump your upload up was to fulfil obscure requests for FLACs you could purchase online but were extremely difficult to purchase (if you're lucky it's just an unknown artist on Bandcamp). I discovered a lot of obscure music this way, some that I'm still looking for to this day after it shut down.

Because I cared so much about being part of that private tracker, this is what also prompted me to rent a seedbox for the first time. I paid in Bitcoin out of paranoia (I lived in Germany where the fines for piracy are HEFTY, and they actually do come after you) back when Bitcoin wasn't really worth that much, and later found that that old wallet suddenly had a couple thousand in it instead of the spare change I couldn't move!

So for example, it's possible that if you already have chronic illness, a disability, or any other kind of health issues, you're more likely to have higher social isolation and therefore be more lonely, in addition to having a higher mortality risk. There's an outside variable (your health) that is correlated with both (loneliness and mortality), but that doesn't necessarily mean that loneliness causes mortality. If this were the case, we could defend claims like "autism increases mortality", because we already know that autism increases social isolation.