> 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.
> 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.
"strive for overall system clarity as your principle pursuit
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?
Everything is quickly strapped together due to teams being understaffed. Preparing infrastructure in a way such that it can easily be recreated is easily twice the effort as “just” setting it up the usual way.
Turns out some of the software running on it had some weird licensing checks tied to the hardware so it refused to start on the new server.
It turns out that the company that made this important piece of software doesn't even exist anymore.
"Might" is not "will".
"Your personal information is removed, but some content you’ve posted in community areas is not. This includes things like discussion posts, or content that you posted in Steam community hubs, as well as comments you made on other Steam account’s profiles."
Me: gurkburk
Reply: #include#include#include (4096 times)
Seems useful!