The problem is the job market has basically priced in exaggerations on resumes. People exaggerate all the time and don’t get punished for it.

If you don’t exaggerate, you may even miss out on opportunities and hamper your career goals whatever they may be, because they already assume you exaggerate and already account for it when reading your resume. And if you don’t exaggerate? Well, they’re happy to pay you less than they would’ve.

Certainly at least in tech in the Bay Area, fake it till you make it is the norm. I’ve met plenty of people with amazing resumes and references just to see them not be as good as advertised.

Blame all the companies with ridiculously high requirements just to hire people who don’t meet all of them. It’s a common advice to apply even when you don’t meet all the reqs, because it works out so often.

This whole thing is basically a nonstory when you realize how much money is in tech. Meta changed their name and sank billions on an idea that everyone thought was stupid from the beginning, and they’re still fine.

Putting a billion into the flavor-of-the-month that has like 10% chance to be the next big thing is a no-brainer when you’re printing multiple billions in profit doing nothing, and have a lot more cash on hand.

The real story, is how wealth inequality and monopolies have essentially allowed the rich to waste tons of money chasing more wealth while having almost no incentive to provide value to society. Who gives a fuck about hallucination and prompt injection? It’s all trivial details that VCs are giving away billions to eventually solve.

The point about a binary protocol is interesting, because it would inherently solve the injection issue.

However, constructing an ad-hoc query becomes tedious, as you’re now dealing with bytes and text together. Doing so in a terminal can be pretty tedious, and most people would require a tool to do so. Compare this against SQL, where you can easily build a query in your terminal. I think the tradeoff is similar to protobuf vs json.

You could do a text representation (like textproto), but guess what? Now injection is an issue again.

Another thing would be the complexity of client libraries. With SQL client libraries, the library doesn’t need to parse or know SQL - it can send off the prepared statement as-is. With a binary protocol, the client libraries will likely need to include a query builder that builds the byte representation since no developers are going to be concatenating bytes by hand, which makes the bar higher for open-source libraries. This also means that if you add a new query feature to your DB, all client libraries will likely need to be updated to use the feature.

And you’re still going to need to tune and optimize queries for this new DB. That’s just the nature of the beast: scaling is hard especially when you can’t throw money at the problem.

Quite frankly, it’s a lot of hard tradeoffs to not need to use prepared statements or query builders. Injection is still is an issue for SQL today, but it’s been “solved” as much as it possibly can.

I’ve been using Jooq to build my queries (and run them). Beats the hell out of writing prepared statements in strings.

Not sure what power I’m missing though, I’ve been able to do everything via Jooq that I want to do.

Everyone loves the idea of scraping, no one likes maintaining scrapers that break once a week because the CSS or HTML changed.

Same, having competitors to Android and iOS would be great.