ban and delete most if not all code comments!
agents love copying what already exists. a seemingly harmless comment explaining some temporary workaround is one of the worst viruses you can have in your codebase. like a weed it'll spread quickly as a tool for agents to quickly get their job done. before you know it, your codebase is overrun with hacks and stale comments. just one more workaround bro
you can use pstack's /no-comments skill as a weedkiller. it'll seek out useless comments while keeping the ones that actually should exist (like explaining a browser quirk), and figure out how to solve them on a first principles basis
here's a prompt you can try asking @bot:
create a project agent that uses /poteto-mode to spawn a /swarm to use /no-comments and identify useless code comments we can prune in my repo. come back with a high level plan of which of these workarounds would be best solved by refactoring and which we can straight up delete
https://t.co/nqeRdY62ee
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
ChatGPT can’t correctly produce image with 19 and 40 snails even after 5 attempts and multiple hints to check its result. It seems such an easy task, what went wrong here? https://t.co/IAq6NjSyAE #chatgpt
🇸🇮 Slovenia’s Ministry of Transport and Energy has tested Tesla FSD (Supervised) and is now working toward Robotaxi approval. 🤖🚕
“The system is safe, efficient, and above all, an exciting glimpse into the future of mobility. It doesn’t get tired, doesn’t fall asleep, and can significantly contribute to safer driving.
The next step: Robotaxis.”
Just got FSD and tried it for the first time. There's a good chance my kids never learn to drive. An arcane skill by the time they’re 18, not unlike operating an elevator back in the day.
I needed to move a sofa.
I mentioned this to an American. He said, "You know anybody with a truck?"
I did not know anybody with a truck.
He looked at me with real concern. Not pity. Concern. The way you look at a man who has told you he does not have a name.
"You gotta know somebody with a truck."
I asked how one acquires such a person.
He said, "You just do."
This is the third time I have received that answer in this country. It is the answer to everything here. You just do. There is no process. There is only the eventual fact of having.
He said, "Ask Kevin."
I do not know a Kevin. He said Kevin like I should. He said it the way you say a shared uncle.
I met Kevin four days later. Kevin owns a truck. Kevin does not own a truck for himself. Nobody owns a truck for themselves. Kevin owns a truck for a fifteen mile radius.
Inside I said: THIS MAN HAS TAKEN A VOW. HE DID NOT ANNOUNCE IT. HE SIMPLY PURCHASED A BED AND ACCEPTED THE CONSEQUENCES.
Kevin arrived on Saturday. He brought the truck. He also brought a second man.
I had not asked for a second man.
The second man's name is Tony. Tony came because Kevin came. Tony did not know me. Tony did not ask what we were moving. Tony brought gloves.
They moved the sofa in eleven minutes.
I offered them money. Both of them laughed at the same time, which felt rehearsed and was not.
I asked what I owed them.
Kevin said, "Buy the pizza."
That is the price. That is the entire economy. The truck costs one pizza and the pizza is not negotiable and the pizza is also not expensive and everyone knows what size.
Inside I said: THE FEE IS FIXED ACROSS THE ENTIRE NATION AND WAS SET BY NO ONE.
We ate on the floor because the sofa was against the wall and none of us wanted to be the first to sit on it.
Tony told me his daughter plays soccer. I asked if she is good. He said, "She's aggressive."
I still think about that.
Three weeks later, Kevin texted me.
"You free Sunday? Helping Tony move a fridge."
He did not ask if I wanted to. He informed me of a fridge.
Inside I said: I HAVE BEEN CALLED UP. I DID NOT ENLIST. THE PAPERS WERE FILED ON MY BEHALF.
I went. I moved the fridge. I have no truck. I contributed only arms.
Afterward, a man I had never met asked me if I knew anybody with a truck.
I said, "Yeah, I got a guy."
I have a guy.
I am somebody's guy now, too. Tony has told two people about me.
He describes me as "the guy who's strong for his size."
I have never been prouder of a sentence in my life.
this is insane
claude code found the COLDCARD wallet vulnerability with a single prompt, in just 8 minutes of thinking
we're not ready for what's coming
Full story — the exact quotes it ignored, and the rule you can copy: https://t.co/Tr2WkqsIQs
What is the most confidently wrong thing your AI has handed you?
The fix: a short rule in the file the agent reads every turn. Read the repo and your own memory before claiming anything is impossible. Treat pushback as a reason to check, not a debate to win.