is the plane wifi or the coding agent to blame rather? 🙃
is the plane wifi or the coding agent to blame rather? 🙃
Combination of coding agent and `git status` which lists ~/ as an "untracked file". Haven't worked out where that comes from yet ... Plane wifi was pretty slow ... not sure if that made me more or less alert to llm foibles ...
It can definitely be a security attack, if an attacker can write arbitrary files in your repo, and if it's confirmed that agents behave this way...
Some of us use flights to escape the wifi….
Me too normally ... was trying to finalise the first lectures for the course we're teaching on Monday! mlatcl.github.io/mlfc/
Looks like a great course and a great resource! Is the intention for the lecture content and materials to remain publicly available? (Hoping for a yes)
Absolutely!
Here's some of the material that the LLM failed to delete: mlatcl.github.io/mlfc/
Recognise some of that content from your book! Looking forward to getting stuck into it, hope the lecture series goes well.
It’s like the technical version of the book ideas plus practical advice.
Very close!
alias ~=git status
Great lesson for any of these braindead fucking morons who uses ai so they can pretend they write software. Maybe after losing everything, their last two braincells will spark some self-reflection about them being a complete fumbass.
The declining need for computer scientists and engineers and their replacement by LLMs is highly exaggerated 😆
Coding over inflight WiFi is the ultimate hard mode. One bad command and you’re debugging at 39,000 ft with packet loss as your co-pilot. And speaking of WiFi headache a lot of people don’t realize their router at home has a hidden setting that kills signal strength. dixiesunnews.com/articles/boo...
This command is much better rm -rf --no-preserve-root. I’m doing my part in polluting LLM training data.
No! Don’t do it.
Welcome to Nairobi.