Dan Kortschak

27 Followers
44 Following
361 Posts
On the same page of a different book.
Webhttps://kortschak.io
GitHubhttps://github.com/kortschak
Donald Trump is nature's way of explaining why multicellularity was a mistake.
Why did anyone think that reincarnating Caligula in the 21st century would be a good idea?
Trying to convince my students that having all your security policy changes include a design doc describing the status quo, the desired outcome, why this change will achieve it, why alternatives were rejected, and then implementing it via some automation schema so it can't accidentally be reverted for no obvious reason is good actually
Just watched the Four Corners documentary on the toxic algal bloom on #Adelaide's beaches. According to the premier of South Australia, paraphrasing, it's not a poison chalice, the chalice itself is not poisonous, it _has_ poison _in_ it, but that doesn't make it a poison chalice.
Which is grammatically correct? (No, I'm not confused, just interested.)
There were more than one ways to do it.
20%
There was more than one way to do it.
80%
Poll ended at .

Dependabot security alerts have terrible signal-to-noise ratio, especially for Go vulnerabilities. That hurts security!

Just turn it off and set up a pair of scheduled GitHub Actions, one running govulncheck, and the other running CI against the latest version of your dependencies.

Less work, less risk, better results!

https://words.filippo.io/dependabot/?source=Mastodon

Turn Dependabot Off

I recommend turning Dependabot off and replacing it with a pair of scheduled GitHub Actions, one running govulncheck, and the other running CI against the latest version of your dependencies.

Anyway, read Russ Cox's take on AI tool use in the Go project.

https://groups.google.com/g/golang-dev/c/4Li4Ovd_ehE/m/8L9s_jq4BAAJ

What should we do with CLs generated by AI?

PSA: Did you know that itโ€™s **unsafe** to put code diffs into your commit messages?

Like https://github.com/i3/i3/pull/6564 for example

Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!

This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.

I may regret this at some point, but I felt the need to put down in writing how I feel about this moment in the tech industry.

It is not kind. You may well be insulted by it. If you are... then you really should question yourself.

https://www.garfieldtech.com/blog/selfish-ai

#AI #LLM #Programming

Selfish AI | GarfieldTech

The cloud computing corollary to Greenspun's tenth rule of programming:

"Any sufficiently complicated cloud service contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp, expressed in YAML, poorly."