There's plenty of non-critical code that I would trust non-technical people with good AI tooling to touch. As long as their access is segregated from the actual critical stuff. But let them write marketing pages or help and documentation pages. Let them write internal reporting code or build tools to use themselves.

▲

jdbiggs 2 hours ago | parent | next [-]

I ran content and educational pages for Kraken a few years ago. This was just as AI was getting useful. I was told by the head of security, the guy who coded all the original software, not to use any outside AI tools to proofread or edit. Then, a few months in, the CEO, Jesse Powell, asked why we were so slow in producing content - we had to edit it all by hand, as you do. We explained the security issues and he said "Who cares, just use it."

So on one hand they are the most secure business on the Internet and on the other hand YOLO!

▲

brandall10 2 hours ago | parent | prev | next [-]

Internal tools and help/marketing pages aren't generally considered production code.

▲

Atotalnoob an hour ago | parent | next [-]

What world do you live in internal tooling isn’t production code?

Internal tools keep the lights on and allow customer facing code to function!

Operational tooling also isn’t a sexy thing, but it’s vital for any company to function.

	▲	kenferry 2 minutes ago \| parent [-]
		I mean, this is semantics. Production is not the same thing as "important", but to me production code means customer facing. Internal tooling isn't production.

▲

estimator7292 2 hours ago | parent | prev [-]

You and I wouldn't because we're engineers. An executive with ulterior motives would want to call it production for "Marketing"

▲

themafia 2 hours ago | parent | prev [-]

> As long as their access is segregated from the actual critical stuff.

Do fintech customers share your ideals as to what is "critical stuff" and what isn't? How much of this business could _plausibly_ be "non critical?"