If you replaced "AI" with "a developer" in this article, it might make more sense why it's being dunked on. It would be an article about someone telling someone to do something, and then when the work was done they were happy with the result. It's just a bit of a nothing all round

> and then when the work was done they were happy with the result

It's worse than that -- they don't even know the result! They never tried to run it!

oh yeah - in this case the result is that the code was smaller and they were happy with that. correctness was not a criteria

yes, but it's only advantage if one is compute-strained and the other isn't. if they both have lots then there's no advantage. if one doesn't fully utilise their compute then it's not an advantage either

Well, it appears all their competitors are compute starved so…

I mean. they're selling it to a competitor so it's not really an advantage

Would you accuse someone of murder with 26% matching evidence?

The Director of Photography on the movie is also an Australian!

I'm building something that has to share a pool of phone numbers for SMS between many businesses with many clients and the architecture I had planned out looks a lot like this - client gets assigned a phone number from the pool for all its interactions with a certain business.

Good write up of a tricky problem, and glad to real-world validate the solution I was considering.

All the apps i've worked on lately in Rails use GoodJob, which is a Postgres NOTIFY/LISTEN based queue system.

Yes, I've seen a lot of Postgres-based queues lately too.

Even without Redis I still end up rebuilding some kind of job system on top of the DB, which is why I'm wondering if this should live outside the app entirely.

Their offering was paid-for bundles of components and templates using tailwind, which they primarily drove traffic to via their documentation, which wasn't getting visited as much anymore because people just used AI.

Startups generally _don't_ end up with better outcomes. Large companies stay stable, startups are volatile and often end in failure.

Stability means removal of volatility, which means to stay stable they end up becoming more generalised, rather than the laser focus a small team like a startup can have. That laser focus can work out when applied to the right problem at the right time, but is very much not a guarantee.

I'm an software engineer with 17 years experience and I can't even get an interview at most places I put my resume in to.

I'm being very picky with what I look at, which doesn't help, but yeah, it doesn't seem great. Maybe they're all in person gigs? Or is there some ageism? (There has always been some ageism in software)

Largely in-person gigs in the SF Bay Area, yeah. One reason the rents are up so much.

> Turso Database is a project to build the next evolution of SQLite in Rust, with a strong open contribution focus and features like native async support, vector search, and more