"Competing with AI vs competing against AI" is a useful framing, but it's worth being specific about what "competing with" actually looks like in practice — because it's easy for this to become vague career advice.
The concrete version: AI is very good at local optimization (write this function, fix this bug, generate this boilerplate) and weak at global judgment (is this the right architecture, what should we build next, why is this feature not adopted despite working correctly). Developers who stay relevant are the ones shifting their value toward the second category — requirements clarification, system design, tradeoff evaluation, and understanding user behavior.
The practical implication for anyone reading this: pick one AI tool and use it for everything in your current role for 30 days, not to replace your thinking but to compress the time you spend on the local optimization work. That freed time is what you reinvest into the judgment work that compounds.
What stands out is the shift you're pointing to - not less work, but different work. The leverage comes from treating AI as a speed multiplier on execution, then deliberately reinvesting that saved time into decisions that AI can't make well what to build, why it matters, and whether it's working.
A lot of people stop at AI makes me faster but your framing pushes it to AI changes what's worth being good at which is the more important shift.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"Competing with AI vs competing against AI" is a useful framing, but it's worth being specific about what "competing with" actually looks like in practice — because it's easy for this to become vague career advice.
The concrete version: AI is very good at local optimization (write this function, fix this bug, generate this boilerplate) and weak at global judgment (is this the right architecture, what should we build next, why is this feature not adopted despite working correctly). Developers who stay relevant are the ones shifting their value toward the second category — requirements clarification, system design, tradeoff evaluation, and understanding user behavior.
The practical implication for anyone reading this: pick one AI tool and use it for everything in your current role for 30 days, not to replace your thinking but to compress the time you spend on the local optimization work. That freed time is what you reinvest into the judgment work that compounds.
What stands out is the shift you're pointing to - not less work, but different work. The leverage comes from treating AI as a speed multiplier on execution, then deliberately reinvesting that saved time into decisions that AI can't make well what to build, why it matters, and whether it's working.
A lot of people stop at AI makes me faster but your framing pushes it to AI changes what's worth being good at which is the more important shift.