Yes. Hyperscalers promised AI and singularity, instead we got millions of programmers on the chopping block, scammers having a field day generating hyper realistic shit (trump playing hokey, anyone?), and projects like these.
Most “cs” students don’t work in aviation, majority (statistically) work on yet another SaaS that is a CRUD that has been solved millions of times already.
I think it's a bit like `rails generate`, where it massively speeds up getting a CRUD webapp 0 to 1, but once you get to GitHub or Shopify size, you need a lot more than that to add a new data model.
AIs are pushing many things forward, but due to training sets and context windows, I think meaningfully adding to actually valuable apps, at least as we currently write them (the kind with many DBs/caches/message queues, services) will take a fair bit longer.
Because the companies doing these will either not employ as many people as they do now or will cease to exist altogether since their customers will not need their services
The software engineers who like "digging ditches" are going to have a bad time in the new agentic engineering world, unfortunately.
Here "digging ditches" corresponds to somebody else figuring out the detailed requirements and specification and handing it to the engineer to transcribe into code.
That's what the coding agents replace. Thankfully for most engineers I've worked with that's only a small part of their overall jobs, albeit one of the most time consuming.
Anyway, you posted about speed, and then followed by a link to some python related thing. In python speed has never been a key tenet, at least when it comes to pure cpu based calculations. How much tooling is built in python? All the modern python tooling is mostly Rust based too. So theres that.
I mean for a dev working in JS with JS built tooling the speed is not in milliseconds, but in seconds, even minutes.
I still think my point holds, having a build take int he 10s of seconds vs 50ms is very much good enough for development (the usual frontend save and refresh browser cycle)
People shaving off the last milliseconds or microseconds in their tooling aren't the same people shipping slow code to browsers. Say thanks to POs, PMs, stakeholders, etc.
I've never met a single person obsessed with performance who goes half the way. You either have a performance junkie or a slob who will be fine with 20 minutes compile times.
They are talking about pnpm (which they said would be the uv equivalent for node, though I disagree given that what pnpm brings on top of npm is way less than the difference between uv and the status quo in Python).
reply