erpellan

Most British people don’t respond well to attempts to cow them. They refuse to be cowed! To allow oneself to be cowed would be cowardly. To do so would have one accused of cowardice, of being a coward.

There was: Heroku

It was glorious.

I meant the social media platforms. If HN charged a fee for posting and commenting it doesn’t matter how cheap the AI models are, it’d be punishingly expensive to sling slop.

Invert the economics. Right now there is value in posting LLM generated content that is more than the cost of using the model.

If platforms had a subscription model that you had to pay for in order to do more than just read comments, there’d be a lot less LLM content. There would also be a lot less of all content. But maybe that’s the price you pay (literally) to get rid of AI slop.

Tell it like it is, sis.

If we just put enough effort in and write the right spec/prompt/design then the programmers/llms/plug compatible coding units will produce the correct output first time!

Closing feedback loops. That’s the whole thing. WE Deming would have recognised agile (little a) as a PDCA system and approved.

Am I missing something or would this be solved by adding a 1 byte `msg` field to the payload?

Making charcoal releases CO2 though? How does that help with carbon capture?

The standard pattern to avoid select for update (which can cause poor performance under load) is to use optimistic concurrency control.

Add a numeric version column to the table being updated, read and increment it in the application layer and use the value you saw as part of the where clause in the update statement. If you see ‘0 rows updated’ it means you were beaten in a race and should replay the operation.

But you’re not getting slower and slower for every car. Lets say 100 cars pull in front of you, and let’s be say each car adds 5 metres of space, so you have 500 metres of ‘lost’ space to regain.

At 30 mph how much later will you be? 37 seconds.

I’ll take that trade.

Unfortunately for the vast majority of people, it absolutely is some kind of magic.

It’s always DNS! Except when it’s the firewall.

You do indeed use JOINS. The goal is to retrieve exactly the data you require in a single query. Then you get the DB to `EXPLAIN VERBOSE` or similar and ensure that full table scans aren't happening and that you have indexed the columns the query is being filtered on.

I can’t believe they still make processors out of sand. Talk about outdated technology.

Sarcasm aside, a great many projects started on MySQL and moved to postgres. As did projects using mongo, couchdb, firebase, oracle etc etc…

And I’m sure many projects switched away from Postgres to other technologies. Right tool for the job at hand.