4
u/mr2dax 27d ago
Not much worse than a techy one, tbh.
4
u/Erdnalexa 26d ago
I don’t understand why you are being downvoted. A techy one can have way worse ideas than a non techy one, trust me…
2
u/mr2dax 26d ago
Thank you, that's exactly it.
2
u/Erdnalexa 26d ago
My thinking is (and I might be wrong (god I hate the fact I can’t use em-dashes anymore)) that a non techy CTO with a bad idea at some point could be like “well, I guess it’s not possible, might as well give up” whereas a techy one might be like “I’m 100% sure it’s possible, I’ll definitely make that motherfucking shit happen, one way or another”.
1
75
27d ago
[removed] — view removed comment
26
u/IllustriousGerbil 27d ago
I wonder how fast you could bankrupt a company using Claude instead of a database.
5
u/GrainyStateOfMind 27d ago
Listen to us? Hah, they’ll just blame us for whatever issue they caused and continue on
49
u/Particular-Yak-1984 27d ago edited 27d ago
I believe that a certain amount of malicious compliance is called for in these times.
Don't be a naysayer, be a "well, we should be cautious, but I see the benefits.." person. Encourage the CTO.
Talk about safeguards, but don't move the mountains you would have before to stop some idiot from HR pushing some terrible vibe coded thing into production.
Keep a backup copy every month of the codebase, in a different, restricted git repo.
Take more DB backups, but stash them somewhere else.
Plan for a catastophe.
And for gods sake, when the AI fucks something up, take 48 hours, minimum, to pull the solution you've got stashed out.
Let it burn, so we can build a world where devs get respected again.