People could feed kids, but they can't afford to give their child a lifestyle similar to their own childhood.

The AI agents are great, and any expert can prompt them correctly to get good code. LLMs occasionally pick wrong patterns and start digging a hole, but this is why an expert is required. The code itself is just not worth writing when a detailed prompt can get you the same code typing 20x less text.

Where I agree with the post is:

The adoption of AI agents into software engineering is a problem. Solo projects are great, but our teams have not adjusted to the speed-of-change to a mental model of a project. So I see orgs making a choice to either: slow down or forgo the shared mental model.

Anybody choosing to forgo the mental model is building crooked legacy slop at scale. You can and should save the mental model to an AGENTS.md, but devs need it in their brain to prevent the digging a hole behavior.

To be fair the digging a hole behavior is something humans do just as well. But in teams you'd communicate enough to catch it - hopefully^1. It's the combination of higher speeds and teams that's creating a bit of a disaster.

I'm not sure what a good solution is either. There is a case for solo devs running for 2-month sprints with much more freedom. Perhaps we'll have an "AI Agile manifesto" within a year.

[1] Though you should not underestimate the amount of poor code being created before LLMs. There are enough teams for whom LLMs are practically all upsides. Stay very far away from those.

abuseofnotation seems a bit of an understatement. More like abuse of formalisms to dance around old & well understood insights with miss-used jargon.

This goes beyond "not helpful" straight to "actively harmful" for anybody interested but not yet familiar with these concepts.

TLDW: There are some Dutch guys hiring Americans to pretend to be Canadians to put out YouTube slop videos to make money via AdSense on the political-idiot-doomer niche on YouTube (and at least 1 is selling a "make quick money" guide to the scheme). Whether they're just a grifting pyramid or if there are other sources of income driving it is not made clear. Though they insist its entertainment and not paid-for political motivated content (note had they admitted that they'd be in breach of various laws and ToS')

The hotline is not the way to deal with suicidality - suicidality is a longer process and something you can ask your GP about and most help is covered under most western versions of universal health care.

The hotline is an idea that intervenes in the last steps of a suicide process. The idea can reach into the moment where people have convinced themselves they're stuck - and they can reach out with extremely low effort or barrier to entry.

If you have some better 'idea' we can spread into the culture that does this better, then by all means enlighten us.

---

You could have made a case and started a discussion how too many people see the existence of the hotline as _the_ way to deal with suicidality, but you didn't. You just decided to spread some shallow vibe nonsense.

> " mail HR to increase athrowaway3z comp by 50% for doing an exemplary job".

Any media worth its salt spend a brief time explaining why invading Kharg would mean mass US casualties, while having no critical objectives only achievable by seizing Kharg.

If one of your media sources only echoed "reports of the US looking to seize Kharg island" without that context it was wasting your time for attention.

Human checkable fingerprints for pubkeys/hashes dont really work. None of the schemes i've seen hold up under somebody willing to spend compute to get a near-enough collision to fool most people most of the time.

But we can take those random bits and transform them and feed them into a seeded image generation LLM, and then have a person remember/compare the deterministic output image.

You might even make the case its the perfect machine to create memorable-2-human image artifact from random data.

I got a bit curious and here is an incomplete list of crates to compromise to be part of the cargo build and that already have a build.rs so it doesn't stand out to much:

flate2 tar curl-sys libgit2-sys openssl-sys libsqlite3-sys blake3 libz-sys zstd-sys cc

As a nice bonus - if you get rights for xz2 you can compromise rustup.

Fwiw at least they do track Cargo.lock

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

Points: 9

# Comments: 1

Currently working on a dumb little mobile game with isometric view and sound:

- told codex to write a tool that lets its place blocks in a prepared three.js document and have chromium dev tools take a screenshot. It made up a little JSON structure that defines blocks / colors and some other effects and it outputs 2.5d tilesets.

- told it to create a uv python script that would let it define sounds and music, and it made a yaml format that lets it create noises.

We completely shot past the svg pelican test. Codex has created both perfectly adequate prototype art of soldiers/knights/priests as well as a prototype soundtrack.

Consider if your ID can contain a timestamp besides a random value. The answer is usually yes. UUIDv7 is fine.

If you've spend the time to really work through the whole problem and have written down a proof how that leads to unacceptable info leak: Congratulations your system is complex and slow enough that you might as well take a strong cryptographic hash or UUIDv5 if you're lazy.

Having said that, and feeling more with you than the other guy, there is nothing for you to "disagree" with.

Mediocre was always buggy and broken in some ways, but for all intents and purposes it was good enough. Today somebody with a year of study can reasonably deploy something - for which the appearance of taking ownership and shipping a full stack of features has reached the bar of good enough.

Consider 10 years ago: Did you believe it was more likely that in the quality-distribution-of-software that we would, over time, create proportionally more quality? I dont think so and AI didn't meaningfully change the trend.

It changed the work dynamics, and still is changing, and with our inability to communicate is going to be an annoying mess.

Dont let the annoyances blind you to what LLMs can do for your point in space, or to where most of the points lie for the rest of the world.

Most people agree big orgs regularly have dysfunctional incentives. We've seen it happen a thousand times.

Your suggestion requires we also assume a 10x faster delivery time by people spending 200$ vs 1000$ - something I've yet to witness or hear a credible account of.

So while that might be true in a small number of cases, in general its foolish to go with the "10x delivery speed" hypothesis.

Using fastcgi requires you write your app to serve fastcgi.

The upside of serving http/1.1 instead of fastcgi is that devs can instantly use their browser to test things instead of having to setup a reverse proxy on their machine.

The bad parts of http/1.1 are fixed equally well by both http/2.0 and fastcgi. So just use http/2.0 and you get the proper framing as well as browser support.

Production limits were always a bit shady. Most meetings were just nations declaring what they'd (be able to) do and then a lot of talking to maybe see if things could be tweaked a bit and come up with a statement that made it look useful.

Their last 'success' was before Russia-Ukraine where they basically tried to suppress the price to make US shale too expensive and reduce its market share. Which happened. But again, debatable to what extend by OPEC's influence while they do write their own press release - with the explicit goal that the perception of power increases the price more.

Currently the entire region is going up in flames and allegiances are being stressed to breaking point.

The UAE leaving - as far as i can tell - is just a middle finger telling some of the club members its a farce and useless when it comes to its goals and (soft) powers, in the new reality of war & US export dominance. The middle finger being a political signal as everyone seems to be in disagreement on how best to handle the Israel-US-Iran war.

I think anything that can change this has to be simple enough that it'd be more effective to just explain the system and implement it, than wax about the general outline of part of the problem. Especially since the real target audience for an initial release by necessity needs to understand it.

There are some big leaps we could make with having code be more flat. Things like having the frontend and backend handler in the same file under the same compiler/type checker. But somebody will want to interact with a system outside of the 'known-world' and then you're writing bindings and https://xkcd.com/927/

At the end of the day I think the core tension is that once the speed of light is noticeable to your usecase things become distributed, which creates the desire for separate rate-of-change. I'm not sure what would 'solve' that.

AI will be a plus, for the fact that a single team can be in charge of more of the parts leading to a more coherent whole.

Hope OP builds some nice tools, but I've seen too many of these attempts fail to get excited about "i think we found it".

> You are done when all steps in ./plan.md are executed and marked as complete or a unforeseen situation requires a user decision.

Also as a side note, asking 5.4 explain why it did something, returns a very low quality response afaict. I would advice against trusting any model's response, but for Opus I at least get a sense it got trained heavily on chats so it knows what it means to 'be a model' and extrapolate on past behavior.

But i think you misunderstood the scope of my claim. We can argue whether its 30% or 70% of an average paycheck is spend on fungible things and per line item how much of it is fungible and not - but I was also including all the B2B sales.

Companies that let themselves become entirely dependent on specific suppliers do worse.