I’m pretty sure that the alternatives are ostracisation or leaving the company. Leaders set company policy, you’re not going to have a good time fighting something this fundamental. Just my 2p.
Plus, maybe if you try it, you won’t be so scared of it, it’s not in a state yet where it doesn’t need a lot of guidance from real engineers
I’m not necessarily confrontational about AI adoption. I’m more interested in situations where leadership basically sets you to fail: unrealistic velocity expectation, too much context switching, code sprawl, PR floods, and so on.
Then communicate that clearly and directly to upper level and set the boundaries. It would lead to a conflict, but you can’t run away from that and agree on a compromise.
AI does increase productivity if you use it as a correct tool when needed. Measure the productivity gain/loss over the time and refine approach iteratively.
Leadership that sets you up to fail is bad leadership. If they weren't true believers in AI, they'd be true believers in the management fad du jour, and would be setting you up to fail by shoving that down your throat.
My approach was usually to start looking - not frantically, but with some sustained effort. If they persist, then it's increasingly going to be a bad place to work, and I can usually find a better place.
Just go with the flow, leadership doesn't know the limitations and by using it and and causing incidents or pushing lots of slop, they will find out.
They are the leaders, you are the employee and the follower.
And honestly, AI is so fucking good, for me it's surprising the fact that you are so behind in adoption and questioning it.
Nobody is writing code anymore.
Companies now need to figure out how to actually structure work and teams based on the fact they can build anything very quickly.
As harsh as it sounds, I loved writing code and configuring my VIM editor, but our old way of working is absolutely over. You have to adapt to it or they have no reason to keep you.
I’m pretty sure that the alternatives are ostracisation or leaving the company. Leaders set company policy, you’re not going to have a good time fighting something this fundamental. Just my 2p.
Plus, maybe if you try it, you won’t be so scared of it, it’s not in a state yet where it doesn’t need a lot of guidance from real engineers
AI does increase productivity if you use it as a correct tool when needed. Measure the productivity gain/loss over the time and refine approach iteratively.
My approach was usually to start looking - not frantically, but with some sustained effort. If they persist, then it's increasingly going to be a bad place to work, and I can usually find a better place.
They are the leaders, you are the employee and the follower.
And honestly, AI is so fucking good, for me it's surprising the fact that you are so behind in adoption and questioning it.
Nobody is writing code anymore.
Companies now need to figure out how to actually structure work and teams based on the fact they can build anything very quickly.
As harsh as it sounds, I loved writing code and configuring my VIM editor, but our old way of working is absolutely over. You have to adapt to it or they have no reason to keep you.