I may regret this at some point, but I felt the need to put down in writing how I feel about this moment in the tech industry.
It is not kind. You may well be insulted by it. If you are... then you really should question yourself.
I may regret this at some point, but I felt the need to put down in writing how I feel about this moment in the tech industry.
It is not kind. You may well be insulted by it. If you are... then you really should question yourself.
@elduvelle @krig @Crell Because companies have made "AI adoption rates" part of the corporate goals, and thus resisting / opposing it is an actual job-loss level risk.
Some individuals can take it, or are principled enough to; not everyone can, especially those marginalized and/or with care obligations.
But, prospective employers don't need to know what techniques you use to do your coding, right? If you plan your code architecture with pen and paper, or use a genAI to plan it (...) isn't the output the thing that matters: is the code well-written, does it work, is it well documented and easy to update / fix?
Could you just lie and say that you use genAI if it makes them happy, but actually not use it, would they even see the difference?
@elduvelle @krig @Crell Employers do measure and observe AI use. You're often required to not *only* use company approved tools (for compliance reasons), but to *use* company approved tools.
They *would* know.
Being caught in a lie would also not be great.
(And there's the unfortunate fact that, for certain applications and subjects, GenAI *is* a productivity boost, so one would fall behind in an externally observable manner.)
@elduvelle @larsmb @krig @Crell
Unfortunately - output alone is not the only factor. Speed/velocity could be another ranked high, whereas correctness might not rank as high.
Multiple such factors exists.
Usually it comes down to cost/benefit.