This is a perfect trigger for the follow-up discussion regarding who should reap the benefits of AI. It feels today like most employers are attempting to go with "I buy a Claude Code subscription for you, you be a 10x developer now".
No. Simply no. It's my decision how to use AI as good as possible, how much extra time to invest now (a fixed cost) to incorporate guidelines and tooling to help AI help me even more in the future. But do not attempt, as an organization, to use that reason to put ++ work on me because every developer starting to do architect work let's face it, that is what will happen, and this is a lot higher-value work than being a plain dev) is not for free.
If your argument is that you pay for Claude Code, fine. I will pay for it but then you as organization get none of the benefits at all.
I can appreciate your sentiment, and it's part of the reason that I pay for my own tools. That said, I do use them to deliver more value to my employer, but also so that I build transferrable experience to fuel my departure when the gap between that value and my compensation becomes insurmountable.
Being more effective at your job will definitely benefit your employer first, but there's also risk and time involved in learning to deliver that value -which they're paying you for even if you pay for your own tools. They absorb that cost & risk while you learn, and when you ideally become an Nx developer, you'll have transferrable skills and experience and be measurably more valuable to your current (or next) employer.
This is a perfect trigger for the follow-up discussion regarding who should reap the benefits of AI. It feels today like most employers are attempting to go with "I buy a Claude Code subscription for you, you be a 10x developer now".
No. Simply no. It's my decision how to use AI as good as possible, how much extra time to invest now (a fixed cost) to incorporate guidelines and tooling to help AI help me even more in the future. But do not attempt, as an organization, to use that reason to put ++ work on me because every developer starting to do architect work let's face it, that is what will happen, and this is a lot higher-value work than being a plain dev) is not for free.
If your argument is that you pay for Claude Code, fine. I will pay for it but then you as organization get none of the benefits at all.
I can appreciate your sentiment, and it's part of the reason that I pay for my own tools. That said, I do use them to deliver more value to my employer, but also so that I build transferrable experience to fuel my departure when the gap between that value and my compensation becomes insurmountable.
Being more effective at your job will definitely benefit your employer first, but there's also risk and time involved in learning to deliver that value -which they're paying you for even if you pay for your own tools. They absorb that cost & risk while you learn, and when you ideally become an Nx developer, you'll have transferrable skills and experience and be measurably more valuable to your current (or next) employer.