> Yes, if they are "responsible" for the code delivered, where responsible means they understand the code, the architecture, the decisions made, etc.
This is a good principle to maintain, I think.
I'm not a professor, but I manage a team of about a dozen people. The maxim I have is: "You're responsible for anything that hits git."
Don't care if the LLM generated it, or the LLM told you if it's a good idea. If you commit it, you are endorsing it as a good idea - so you're the one I'm going to ask about it. I see the same principle at work in your pedagogy.
> I'm not anti-AI (and really, what could I do if I were?) since I use it myself, I'm just anti-slop, especially from my students.
This hits. Especially this part:
> and really, what could I do if I were?
My completely unsolicited opinion: you're doing a responsible thing by teaching these students how to use AI as a reference, and keeping them honest about not using it as a substitute for their own critical thinking.
Personally I hate how badly internal users are served by the majority of their systems and am willing to take some calculated long-term governance risks
This, I think, is the LLM/vibe coded app’s current place to shine.
Most internal systems don’t need massive concurrency or redundancy. It’s a webapp that reduces coordination cost between 20ish people. That’s something you can typically vibe code and deploy for ten bucks a month, and create real value.
I was one of probably eight people who played the Emperor: Battle for Dune RTS game, and I always think of the Fremen character sound bite whenever I see the Old Man of the Desert’s true name invoked:
One other commenter asked a decent question - does going lighter (Zig) or harder on memory safety (Rust) confer any meaningful advantages against the phenomenon you describe?
POC generally means “you can demonstrate unintentional behavior”.
“Exploit” means you can gain access or do something malicious.
It’s a fine line. Author’s point is that the LLM was able to demonstrate some malfeasance, not just unintended consequence. That’s a big deal considering that actual malicious intent generally requires more knowhow than raw POC.
If they can build a peaceful relationship with Taiwan without military involvement where both countries can continue to prosper we really will have a new super power
Ah, if only.
Those damn intransigent Taiwanese!
It’s almost as if they don’t want to join the PRC.
A few weeks ago my friend Aadil and I were at Whole Foods buying a birthday cake for a friend. We wanted to write something clever on the cake but couldn’t really think of anything. We stood around thinking for a few minutes before Aadil said "Let's just say a bunch of bad ideas out loud so we can get to the good ones." And it worked!
It's a well known creative / brainstorming trick that the best way to have a lot of good ideas is to have a lot of ideas.
Focus on genesis decoupled from critique, then critique later.
Not sure what you mean, but I’d never heard of Sarah Paine before that. I thought she gave a very concise yet nuanced view of the modern world order in her lectures for Dwarkesh.
it's usually coding something more precise in a sort of plausible deniability.
Yep. I'm a director now. This is exactly how it is. A big part of being effective in this role is understanding how direct you can be in a given scenario.
A senior manager on reviewing a proposal asks them to synergize with existing efforts: Your work is redundant you're wasting your time.
Option 1 is how I'd say it to a peer whose org is duplicating effort. You can give your advice, but at the end of the day: not my circus, not my clowns.
Option 2 is a more-direct way of how I'd say it to someone in my own org. I'd rephrase to: "Someone else is already doing this; focus your efforts on something more impactful."
I suspect that part of it is that people don’t have enough time to mentally incorporate the fix.
Is it weird to submit the MR later, after people have had a chance to digest the issues?