Remix.run Logo
▲ HolyLampshade 8 hours ago

It could also be as simple as the technology adjacent people developing tools via LLM that somehow end up in the critical path of some business function and now it needs to be supported by someone.

I’ve seen the same happen with insane spreadsheets.

As empowering as something like Claude code can be, leaving development to developers means the output is inherently supported by the organization long term.

▲HolyLampshade 7 hours ago | parent | next [-]

Extending the thought, there’s also the risk it enters critical path but something upstream changes or Anthropic starts charging 1000x for the tokens and now someone needs to walk through god knows how many lines of never before reviewed code to figure out how it works.

By wholly depending on the assisted coding you are wholly dependent on Anthropic, forever, for something that is now critical.

There are probably thousands of these little microscopic dependencies that occur when you make these tools widely available. What happens when you don’t want to foot the bill anymore?

▲phantompeace 7 hours ago | parent [-]

You use OpenAI or Deepseek in that case.

▲HolyLampshade 5 hours ago | parent [-]

Capture is capture though. It’s not a matter of which AI provider you use. It’s a matter of losing agency over how an aspect of your business works.

Like going 100% into a single cloud provider. Or 100% into MSFT products. There’s legitimate friction in decoupling.

▲specialp 7 hours ago | parent | prev [-]

This is what happens. We had this happen with end user scripting pre AI where these scripts became unknown production applications. It made the actual engineering impossible because you had no idea if anything you changed would impact the ??? processes run by users that have become critical. AI would amplify that greatly so we have an explicit rule that it can only be used for reporting and prototyping only and we restrict any write action