3 ms·
> 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 Claud
by willio58 5mo ago
> 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 odd because I used to tout myself as someone who like programming but I think what I’ve discovered is I like building.
- xboxnolifes 5mo agoI'd still want to code without AI if it's permanently gone. But if it's gone for 10 minutes? Sure, I'll switch to something else.
- ray_v 5mo agoIf your spaceship is broken, you'd still be able to fly back to the moon on your own just like our forefathers did! /s 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.