How is it a bad thing to have cloudflare out of your country? No single entity should have the power to do this kind of thing even if they choose not to. Don't threaten italy with a good time
We build our fine tuning and reinforcement pipeline at cortex.build by synthesizing interactions between a user, the agent loops, and a codebase. The exact data they get from users in Claude Code.
That data is critical to improve tool call use (both in correctness but also to improve when the agent chooses to use that tool). It's also important for the context rewrites Claude does. They rewrite your prompt and continuously manage the back-and-forth with the model. So does Cortex, just more aggressively with a more powerful context graph.
Then we'd be living in a world that didn't require you to have an email in order to do anything like have a job or a social life, which is probably a good thing
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
I think this question can be answered in so many ways - first of all, piling abstraction doesn’t automatically imply bloating - with proper compile time optimizations you can achieve zero cost abstractions, e.g C++ compilers.
Secondly, bloated comes in so many forms and they all have different reasons. Did you mean bloated as in huge dependency installs like those node modules? Or did you mean an electron app where a browser is bundled? Or perhaps you mean the insane number of FactoryFactoryFactoryBuilder classes that Java programmers have to bear with because of misguided overarchitecting? The 7 layer of network protocols - is that bloating?
These are human decisions - trade-offs between delivering values fast and performance. Foundational layers are usually built with care, and the right abstractions help with correctness and performance. At the app layers, requirements change more quickly and people are more accepting of performance hits, so they pick tech stacks that you would describe as bloated for faster iteration and delivery of value.
So even if I used abstraction as an analogy, I don’t think that automatically implies AI assisted coding will lead to more bloat. If anything it can help guide people to proper engineering principles and fit the code to the task at hand instead of overarchitecting. It’s still early days and we need to learn to work well with it so it can give us what we want.
You'd have to define bloat first. Is internationalization bloat? How about screen reader support for the blind? I mean, okay, Excel didn't need a whole flight simulator in it, but just because you doing don't you use a particular feature doesn't mean it's necessarily bloat. So first: define bloat.
Some termite mounds in Botswana already reach over two meters high, but these traditional engineering termites will be left behind in their careers if they don't start using AI and redefine themselves as mound builders.
reply