I had a fun one this week! I needed to make an SQL query that would aggregate rows by invoice and date, but only aggregate 5 then overflow to a new row. I also needed to access the individual row data because the invoice items weren’t summed, they were displayed on separate columns!

I ask my senior if there’s an easy way to do this, he comes back with “chatgpt says you can assign row numbers then get individual row data with % row number”

I go to Gemini and ask “how to aggregate rows by 5 and get individual row data out?” It says “you can’t” (since when has Ai’s been able to say you can’t do X) So I ask it about the modulo operator and it gives me an example that doesn’t really work. After screwing around for a while I give up and decide I’ll just run this query 3 times. 1 for rows 1-5 then for 6-10 and one more for 11-15 that’s so many rows surely no one will break this.

Isn’t the “passive aggressive licence” just MIT?

deleted by creator

I agree with you, it was more of a commentary on “what would happen if we had AGI tomorrow”.

We’ve been 3 months away from AGI for a few years now and it’s debatable if we’ll ever get there with LLM’s. Looking into the results of AI tests and benchmarks show that they are heavily gamed (tbf, all benchmarks are gamed.) With AI though, there’s so much money involved, it’s ridiculous.

Fortunately it looks like reality is slowly coming back. Microsoft’s CEO said that something like “AI solutions are not addressing customer problems.” Maybe I’m in a bubble but I feel like overall, people are starting to cool on AI and the constant hype cycle.

I’d agree that in the short term, AI is overhyped and in the long term, who really knows.

One thing I’ve always found funny though is that if we have AI’s that can replace programmers then don’t we also, by definition, have AI’s that can create AI’s? Isn’t that literally the start of the “singularity”, where every office worker is out of a job in a week and labourers only lasting long enough for our AI overlords to sort out robot bodies?

“we’re just trying to display <insert field here> why is this so hard? It’s a ten minute job!”

Rust makes multi threading very easy you can just use

thread::spawn();

But rust makes Async difficult because it’s naturally stackless so you need to create your own scheduler or use someone else’s like Tokio. Also, people have a bad habit of conflating async with concurrency which makes it more confusing.

My favourite is always;

Lemme quickly write this test, it passes great, if I make this little change it’ll fail. It’s still passing, damn.