I dunno, I have a lot more sympathy for non-technical users writing slop than engineers. I think it's really great that more people get to "properly" use the computer, in that they experience a flexible programmable environment, rather than a fixed set of discreet programs "take it or leave it".

If the issue is security, a much more interesting problem for the engineering team to do is design the programming environment for the bankers so they cannot hurt themselves.

If the issue a performance, designing great abstractions that the bankers' agents can use is "low code done right".

I hope the bankers rebel hard against this policy change!

The ability of bankers or traders to even create an app that others can run, without any IT review/approval process is probable a compliance issue in and of itself.

There are things simple building blocks don't prevent in the event of nefarious or stupid behavior.

Imagine a nefarious banker creates an app that lets him talk to a trader on the other side of the "Chinese wall" about M&A deal flow without getting caught because they are avoiding monitored channels like email, slack, phone, zoom.

Imagine an idiot writes an app that scans his email and summarizes client information he is privy to and writes it to some database that his app then serves up to others on the trading desk. He is unaware that entitlements exist, and by giving others access to his new app he has broken them. Btw summarizing email is a HUGE use case across non-technical users in finance that they are very excited about.

I feel the same way. There's also a lot of startups promising this future but none of them are technically equipped to deliver it. I think almost every company is going to have an interesting ecosystem of internal apis in the future.

In certain industries, compliance/lack thereof has serious consequences, so it might be more to do with that rather than punishing non-technical users just for using AI. For example, if an AI model trains on your internal financials, and someone else uses it to make a quick buck, then that's insider trading. Things like that.

There have been a lot of recent issues with LLMs finding security bugs quickly. If the issue is security, they need to design the bulletproof platform first, then give the less-technical users access to it.

I dunno if rebellion is the right framing. Maybe pulling the organization toward their side instead. Ultimate the “bankers” at an investment company decide where the company is going, after all. Grabbing your own steering wheel isn’t rebellion.

Yeah, I wonder if the medium term shift here is away from CC (which runs on your own machine and is super risky if you have sensitive client information) to something like Claude Managed Agents, where everything is sandboxed.

Or just the Claude app with local execution disabled by org policy, if that’s a thing.

> rather than a fixed set of discreet programs "take it or leave it".

> If the issue is security, a much more interesting problem for the engineering team to do is design the programming environment for the bankers so they cannot hurt themselves.

Interesting take but it doesn't compute. When engineering team teams design programming environments so that people can't hurt themselves they will be locked into a "take it or leave it" set of environments.

Also, you do know security isn't just about engineering, it is also about data right?

How do you suppose it works when bankers who have day to day access to sensitive data as part of their job - upload it to AI? What to do then? Restrict data access?

> rather than a fixed set of discreet programs "take it or leave it".

This part always amuses me. AI boosters seem to think everyone hosting their own bespoke app is the next big thing. But who manages that? Banks are not tech giants. Most engineering teams don't bring in money and headcounts are strictly managed. As the article says:

> "He told Bloomberg that traders and bankers had built tools with AI and passed them to the firm's engineers, of whom there are about 12,000, to be improved."

So, how does engineering with limited staff design a safe environment and improve 12k apps. I am sure Goldman's management wont be thrilled about increasing engineering headcount to match these expectations.

> design the programming environment for the bankers so they cannot hurt themselves

Sounds like the web platform.

Anthropic and OpenAI can’t design secure programming environments.

> they experience a flexible programmable environment, rather than a fixed set of discreet programs "take it or leave it".

> If the issue is security, a much more interesting problem for the engineering team to do is design the programming environment for the bankers so they cannot hurt themselves.

> If the issue a performance, designing great abstractions that the bankers' agents can use is "low code done right".

You do realize you're contradicting yourself right? To get to a state where "bankers cannot hurt themselves" or "low code [is] done right" is to end up right back at the "take it or leave it" programs.

Security was already addressed, by these "take it or leave it" programs.

Add enough abstractions on top of each other that must be adhered to or else it falls apart, and what do you get? "take it or leave it" programs.

This reminds me of the sovereign citizen movement that got really popular in 2019. The illusion of freedom feels great I'm sure. Until you realize you are entirely dependent on the existing infrastructure and the people who maintain it to enjoy the apparent freedom.

The issue is probably an overwhelming amount of slop like PoCs, presentations on every topic, claude artifacts with 1000 pages instead if 10 liner in the chat.

All this is just counter productive and drowns everyone is slop.