Goldman Sachs pulled AI coding tools from its traders. Keep building, just not on your laptop

stormstorm·
#ai-coding-tools#data-security#no-code#goldman-sachs

A State of AI story about Goldman Sachs picked up 722 points and 396 comments on Hacker News this week. Most of the bank's traders and bankers can no longer use AI coding tools at work. Citing Bloomberg News, the story says guidance updated in October limits Claude Code and GitHub to the bank's engineers, following a review of productivity and risk concerns. Traders had been using the tools to track client flows and build market models.

The part I keep coming back to is from July. Goldman's CIO, Marco Argenti, was talking up "vibe coding" by non-technical staff. Traders and bankers built tools with AI and passed them to the firm's roughly 12,000 engineers to improve. The article lays out both sides of that arrangement. The people closest to a problem got a first version without waiting for engineering time. And thousands of people with no engineering training were running software that writes and executes code, on the same machines they use for client information.

I don't read this as proof that non-engineers shouldn't build. The tools were useful enough that losing them frustrated some traders. The risky part was where they ran: an agent that writes and runs code, on the computer that holds client data.

Your laptop has client data too

You probably don't handle trading flows. But if you run a shop or a studio, your laptop likely has your customer list, your email, your bank session and a pile of saved passwords. Point a coding agent at a folder on that machine and you've built a small version of the setup Goldman just pulled back.

Four questions before you build with AI

  1. Where does the code run? If the answer is "my computer," everything on it is within reach.
  2. What can the app touch? Customer data should be reachable only from the pages that need it.
  3. Who checks it before real people use it?
  4. How do you undo a bad change?

How DontCode answers them

You describe your app to Insight in plain words. The code is written and runs on our platform, never on your laptop, and you never have to open it.

  • Each time a new version goes live, the platform reads the app's code and writes the rules for it: the browser reaches only the tables and files your pages use, and where a table belongs to someone, only that person's rows, with nothing for you to set up.
  • Depending on your plan, every build is checked in a test world, a separate copy of your app's data, before it goes live. A change that keeps failing doesn't ship, and the live app stays as it was.
  • Restore any earlier version in a minute or two, without touching your data.
  • Activity records every data edit: who changed which row, and what it was before.

Goldman's traders could hand a first version to 12,000 engineers. A bakery owner can't. So the first version a small business builds has to be safe to run as it is.

If there's an app you've been putting off, try building it on DontCode.

    Goldman Sachs pulled AI coding tools from its traders. Keep building, just not on your laptop | DontCode