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!
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.
> A trading floor is a bad place for unreviewed code written by people who can't read it, and the information barrier problem would be reason enough on its own. Requiring that agent-written code come from people trained to review it is a sensible rule for a regulated business.
Jokes on them: devs are also losing the capacity to read the code. Can't mix move fast, high volume with "read code".
> "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."
As someone who has been on the receiving end of many of these tools, I feel 'improved' is doing some heavy lifting here.
Completely overhauled to be operationally viable, perhaps.
Thrown into the dark recesses of the backlog, more likely.
Internal guidance updated in October restricts Anthropic's Claude Code and Microsoft's GitHub to the bank's engineers
There. Now only devs can use Claude Code. That makes sense.
Has nothing to do with AI being bad. Good engineers have a mind for it. They tend to be more detailed oriented. Understands how parts connect. Understands the pros and cons of approaches. Can see when the AI does something stupid. Probably knows a better way if the AI veers off.
We don’t ask software engineers to file Goldman Sachs yearly company taxes using just AI right without any expertise right?
Yeah, this is more likely to not waste engineers time while dipshits vibe code their own "tools" and demand that they are production ready despite being said dipshit.
I bet engineering loved traders tossing vibe-coded crap across the wall and demanding it be productionized. "It can't be hard, after all I've already written the code for you."
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!
Just fyi.
Agentic engineering needs to be "all in".
As someone who has been on the receiving end of many of these tools, I feel 'improved' is doing some heavy lifting here.
Completely overhauled to be operationally viable, perhaps.
Thrown into the dark recesses of the backlog, more likely.
Has nothing to do with AI being bad. Good engineers have a mind for it. They tend to be more detailed oriented. Understands how parts connect. Understands the pros and cons of approaches. Can see when the AI does something stupid. Probably knows a better way if the AI veers off.
We don’t ask software engineers to file Goldman Sachs yearly company taxes using just AI right without any expertise right?