491 karma · joined January 11, 2020
That being said, the whole thing about go being "readable" is a little bit of a two-edged sword. Sure, it's straight-forward to read, but it's pretty verbose. And agents are good at producing a lot of text. The problem with reviewing go code for me is to see the forest for the trees. Subtle misunderstandings often hide in the vast amount of code that you have to read through while keeping the whole context in your head.
Just out of curiosity, why did you pick that name? Is there anything wallfacey about this project I'm not getting?
Before LLMs, when I still refactored by hand, coworkers who were using vim or vscode used to ask me to do big refactors, because IntelliJ always got it right, whereas with the other editors it was hit-or-miss.
`TC WHIMPER -1 # YES. DONT DO POODOO. DO BAILOUT.`
What do senior developers say they'll work on improving in their performance reviews?
You can spend three months in whiteboard sessions planning out the perfect solution, and then your plan falls apart the second you start implementing, because the real world imposes constraints on you that were practically impossible to know a priori. Not theoretically impossible, mind you. If you'd been smart enough and spent enough time thinking about it, you would have thought of them. But you aren't smart enough, and you don't have the time. Those are some other constraints that the universe puts on you.
Not saying that "there's nothing we can do" or anything, but it does feel like this is one of those instincts that you develop growing up with the internet. Like, my first instinct reading that (and I hope getting that call) would be "what the hell is the lawyer doing at the scene". You have to treat _everything_ coming through your phone as potentially untrusted. I don't have any data on this, but it feels like my friends, and especially younger people, do that automatically.
The primary defence against all phishing is to tell yourself: nothing is ever really that urgent. Nothing is ever that good.
Is it like chess only way more obvious, that the first mover wins, and if so, wouldn't the Romans have figured it out?
Or am I just exploiting a weakness in the AI and a human would make better choices?
Given Boeings later history this is pretty chilling...
But the bonus word (a word most player would miss) on 29/7 was not very subtle. No spoilers, but you won't miss it >.<