I guess we've both been traumatized by modern linux distros?

I just renovated an Ikea table from 1980-something. Actually found it in the catalog too.

It's solid wood, so it'll probably last another 40 years at least.

When I opened it, it said it was a multilingual dictionary so I just typed a (nonsense) Swedish word:

Me: gurkburk

Reply: #include#include#include (4096 times)

Seems useful!

I asked GPT about it:

> You are using the newest model OpenAI offers to the public (GPT-4o). There is no “GPT-5” model accessible yet, despite the splashy headlines.

I can use it with the Github Copilot Pro plan.

Great article. The overall idea is summarized by its closing statement:

"strive for overall system clarity as your principle pursuit

I put a chapter of a paper I wrote in 2016 into GPTZero and got the probability breakdown 90% AI, 10% human. I am 100% human, and I wrote it myself, so I guess I'm lucky that I didn't hand it in this year, or I could have gotten accused of cheating?

That's more an indictment of the accuracy of such tools. Writing in a very 'standard' style like found in papers is going to match well with the LLM predictions, regardless of origin.

maybe gptzero had your paper on its training data (it being from 2016)?

I wasn't being serious when I said it, I was using it as an insult for bad work

I've been using Arch as my daily driver for over fifteen years. I'm not a fanatic, it just works really well.

I met a dev who's mom had been working on legacy banking systems her whole career. She had started in the eighties and she still did some urgent jobs at a crazy rate despite officially having retired.

My stepmom who retired five years ago, did COBOL dev as part of her banking job until 2002ish and then she was full-time management track. In her bank, most of the work had been integrated with Java, and the Java was done by outsourced Indian teams. At the time she retired she felt the Indian teams had been failing for years to meet objectives, and finally management was seeing it. Additionally everybody who knew the COBOL side of things was retiring at the same time as she was and she did not want to know what the system would look like in five years.

I can imagine the conversation involving something along the lines of “don’t ever call me.”

My mother used to teach Cobol back in the 80’s in Brazil but later she transitioned into management and haven’t touched a line of code for more than 30 years, she can’t even speak english wtf

Credo!

I would have flagged that they're logging their Redis URL, if I was reviewing this. Most of the time this includes credentials.

Normally I think it's a bit rude to criticize the code of blog posts, bit I thought it was relevant here for these reasons:

"I often don’t even remove when I’m done debugging because they’re now valuable in prod" - think about where your production credentials end up. Most of the time, logging them won't hurt, just like keeping your password on a post-it doesn't hurt most of the time.

The arguments about letting an AI reduce the mental overhead is compelling, but this shows one of the (often mentioned) risks: you didn't write it so you didn't consider the implications.

Or maybe the author did consider it, and has a lot of good arguments for why logging it is perfectly safe. I often get pushback from other devs about stuff like this, for example:

- We're the only ones with access to the logs (still, no reason to store credentials in the logs)

- The Redis URL only has an IP, no credentials. (will we remember to update this log line when the settings.redis_url changes?)

- We only log warnings or higher in production (same argument as above)

Maybe I should stop worrying and learn to love AI? Human devs do the same thing, after all?