this seems to translate "we fucked it so hard with trying to vibe code a real thing, your job is to fix it and take all the blame"

[flaviusb@mastodon.social]

@davidgerard (Also also 'last line of defense, 100% responsibility for everything including all of the money stuff' and they say 'senior' instead of 'staff' - clown shoes)

[dysfun@social.treehouse.systems]

@ariadne @davidgerard oh wow, some of what they listed makes me think this is absolutely the job from hell.

[jmax@mastodon.social]

@duke_of_germany @davidgerard My criterion is enough money that after six months, I can do exactly that for the rest of my life.

(n.b. - I do think quite highly of myself. But nobody, including me, is worth that kind of money.)

[jmax@mastodon.social]

@duke_of_germany @davidgerard And the work, assuming I did, would actually be fending off the bozos while I did a complete rewrite.

[dysfun@social.treehouse.systems]

@ariadne @davidgerard

• Values accuracy over speed — a ledger bug in production is worse than a week of delay

lmao, if only there were some way to (as the cool kids are saying these days) 'shift left' such concerns.

[davidvedvick@fosstodon.org]

@davidgerard something tells me software engineering will remain alive and well

[fred@social.fthevenet.eu]

@davidgerard

Much of the codebase has been generated by AI.
[...]
We need someone who can look at all of this and say: “this will break in production” — before it actually does.

Not sure the "looking at it" step is even necessary, tbh.

[tubemeister@mstdn.social]

@davidgerard Oh I can do that for free even:

I can look at all of this and say: “this will break in production”

GLWT

[davidgerard@circumstances.run]

spotted by @froztbyte

[brohrer@recsys.social]

@davidgerard the idea of “engineering reliability” as a coat of paint

[barubary@infosec.exchange]

@davidgerard Look, all the hard parts are already done: infrastructure, distributed systems, database design, encryption, financial flows, etc. Now we just need someone to bolt on safety and security after the fact. How hard can it be‽

[ariadne@social.treehouse.systems]

@davidgerard @dysfun these are the types of jobs I used to take on

[dysfun@social.treehouse.systems]

@ariadne @davidgerard i mean i did too, but usually not knowing how bad it would be.

[wakingrufus@bigshoulders.city]

@davidgerard
They tried to vibe-code a PCI-DSS compliant payment processing system??? Lol. Lmao.

[speculationfictive@union.place]

@davidgerard This is satire, right? Right?!

[rycochet@furs.social]

@davidgerard Scapegoat wanted, must be willing to face all the consequences of our decision making and surrender a future career elsewhere because of the reputational harm when we throw you to the wolves.

[dukeboitans@mas.to]

@davidgerard why they don't just ask claude to "not make any mistake!"

[abucci@buc.ci]

@davidgerard@circumstances.run While I wouldn't put it past an AI-pilled startup to try using AI to poorly "solve" a problem that was solved by the Mesopotamians, I wonder whether this is real. The user joined twitter this month, and has only the one post. It's so over the top absurd it's hard to believe a real human being would write it, let alone post it.

[malvarma@tiny.tilde.website]

@davidgerard i dont get it. Why can't they just ask claude to review the codebase and fix all the bugs?

I am told that ai always works, you just need to prompt harder.

[slotos@toot.community]

@davidgerard With that salary I could retire early. With that job description I will retire right into the grave.