https://github.com/llvm/llvm-project/pull/130458
Right now I'm using Roo Code and Claude 4.0. Roo Code looks cooler and draws diagrams but I don't know if it's better.
Employers will buy AI tools for their employees, this isn't a problem.
If you're saying that you need to buy and learn these tools yourself in order to get a job, I strongly disagree. Prompting is not exactly rocket science, and with every generation of models it gets easier. Soon you'll be able to pick it up in a few hours. It's not a differentiator.
Of course, LLMs might get there eventually. But until then I think it will create a bigger divide between seniors and juniors than it traditionally has been.
Going AFK is a terrible idea anyways because I have to intervene when it's making bad architectural decisions. Otherwise it starts randomly deleting stuff or changing the expected results of test cases so they'll pass.
What's the point of shipping a Chrome feature before graduating? Just to put in your CV that you've committed in some repo? In the past this would be signal of competence, but now you're working towards a future where doing this thing is not competence signaling anymore.
When I started an internship last year, it took me weeks to learn my way around my team's relatively smaller codebase.
I consider this a skill and cost issue.
If you are rich and able to read fast, you can start writing LLVM/Chrome/etc features before graduating university.
If you cannot afford the hundreds of dollars a month Claude costs or cannot effectively review the code as it is being generated, you will not be employable in the workforce.