But Claude Code costs money. You really want to introduce a critical dependency into your workflow that will simultaneously atrophy your skills and charge you subscription fees?
It's also proprietary software running on someone else's machine. All other arguments for or against aside, I am surprised that so many people are okay with this. Not in a one-time use sense, necessarily, but to have long-term plans that this is what programming will be from here on out.
Another issue with it is IP protection. It reminded me stories where the moment physical manufacturing was outsourced to China, exact clones appeared shortly after.
Imagine investing tons of efforts and money into a startup, just to get a clone a week after launch, or worse - before your launch.
Right, we the workers are giving away control over the future of general purpose computation to the power elite, unless we reject the institutionalization of remote access proprietary tooling like this
tjr|2 months ago
oxag3n|2 months ago
Imagine investing tons of efforts and money into a startup, just to get a clone a week after launch, or worse - before your launch.
stemlord|2 months ago
dwaltrip|2 months ago
- google maps
- power tools
- complex js frameworks
- ORMs
- the electrical grid (outages are a thing)
- and so on…
This isn’t a new problem unique to LLMs.
Practice using the tool intelligently and responsibly, and also work to maintain your ability to function without when needed.
jennyholzer2|2 months ago