Comment by customguy
4 days ago
Are you not worried about this being a sort of one-way street? Do you have any strategies to avoid ending up with a codebase you cannot work on without "AI"? when I think insurance company, I would assume the value seems to be more in the trust you build up over decades of with customers, not producing lots of code faster.
Well I am still in the loop as a senior dev and I get to review everyones code before it gets merged. Official guidelines is that everybody is responsible for the code they produce (with or without AI) and must understand it when they give it to the reviewer. I've been doiing this 3+ years at this company, so before the whole AI thing landed. I am explicitly not allowed to implement features myself (because the idea is the juniors learn and get trained).
Now, within the last 6-12 months of AI advancement, I think you could lay off half or even 3/4 of the team if I was explicitly allowed to implement features myself using AI. But that is not the current policy.
As for worries "ending up on a codebase you can't manage without AI" - my personal take is: No, I am not worried. Because going forward AI will always be available in the development workflow. That is my own opinion, not the corporation standpoint, however.
> Because going forward AI will always be available in the development workflow.
So your AI subscription is basically a subscription to your own code. Are you sure the tokens will always flow for you?
Being unable to work on a codebase without AI is not necessary. Working with models you can fit on consumer hardware is already significantly more productive than rawdogging code. It's similar to "you won't always have a calculator with you" from math teachers, see how that turned out.
A way bigger problem is a codebase that you can't effectively work on with AI, which is a lot of legacy humanslop. And things that make a codebase more suited for AI, like documentation that provides relevant domain knowledge and context for requirements, automated quality control, and test coverage, also make a codebase easier to work on for a human too.
You get the same result when you calculate something by hand or with a calculator.
And that whole "legacy humanslop" paragraph is just stating the obvious with an air of spite towards humans.
People who can't bother to reason get angry when you say "hey, why put all eggs into one basket", episode N. Boring.
It's not spite towards humans. It's spite towards typical state of pre-AI codebases.
It's not even a matter of incompetence, most of the humanslop came from the fact that you could just never implement anything properly in the time you were expected to do it.