Have a Coherent AI Policy
61–66 of 66 posts
Re: Have a Coherent AI Policy
#62> It’s Still Your Code... AI maximalists will read this section and scoff. They’re already vibe coding everything and have little to no idea what the generated code looks like. This frames the argument like a dichotomy. And to be honest, using the Social Media "vibe-coding" as a strawman risks anchoring against something that's a mirage. There are plenty of good engineers getting good results whilst accepting code-ow…
Who's name do you put down on a code commit? Yours, or the LLM? If it's yours then it is your code and you are responsible for knowing all about it. If it's the LLM then what do we even need you for?
Yeah, I get that it means “you’re responsible for it”, but the phrasing irks me.
Re: Have a Coherent AI Policy
#63> You must understand what your AI generated code does Absolutely yes. > You must be able to do your job if your AI tooling disappears Absolutely not. Look, I'm an alright programmer. Not good, far from great. Interpreted languages work for me; add all that strong typing and compilation and it starts to go beyond what I'm interested in. Nonetheless, pre-AI, I have shipped many very functional, production-grade applic…
A better analogy would be "the trebuchet for computers". "but when there's hundreds of kilometres to cover in a short amount of time, the trebuchet is clearly the correct choice." you point it in the rough direction and distance you want to go, pull the lever, see if you hit your mark, adjust, pull the lever again, etc. And once you have dialed in the variables for that particular piece of rock that one time, you wri…
That’s off by about three orders of magnitude. A trebuchet’s range is in the hundreds of meters, not hundreds of kilometers.
Re: Have a Coherent AI Policy
#64Re: Have a Coherent AI Policy
#65> You must be able to do your job if your AI tooling disappears While I agree with the sentiment I fear this won’t last long. I already find myself, when Claude goes down for 15 minutes due to whatever, kind of throwing my hands up and taking a walk assuming it’ll be up by the time I get back. Usually it is. If it went away for good I’d be able to code, but would I want to? I’d be kind of bummed in a way. Which is od…
It feels like the arguments here are very "status quo biased" - Ok, sure - I guess for some shops the code is the source of truth for the org and you really have to be prepared/equipped to deeply reason around the code and these so-called-patterns.
Really it seems to me that the era of "agentic coding" has uncovered some uncomfortable truths. This is purely speculative, but it seems like most shops maintain little-to-no specification documentation for defining the code behavior - the code IS the documentation and that feels dangerous from a software engineering / architectural statdpoint.
Re: Have a Coherent AI Policy
#66Earlier quoted context omitted.
A better analogy would be "the trebuchet for computers". "but when there's hundreds of kilometres to cover in a short amount of time, the trebuchet is clearly the correct choice." you point it in the rough direction and distance you want to go, pull the lever, see if you hit your mark, adjust, pull the lever again, etc. And once you have dialed in the variables for that particular piece of rock that one time, you wri…
> “but when there's hundreds of kilometres to cover in a short amount of time, the trebuchet is clearly the correct choice." That’s off by about three orders of magnitude. A trebuchet’s range is in the hundreds of meters, not hundreds of kilometers.