AI is. a tool. a power tool for sure but ultimatly it multiplies what the developer brings to the table. I personally have found it of limited use outside a few

AI is. a tool. a power tool for sure but ultimatly it multiplies what the developer brings to the table. I personally have found it of limited use outside a few situations such as knocking out a bunch of boilerplate. That said, I would keeo this thing the hell away fro junior engineers and I wouldn't want a junior who has used AI his entire career anywhere near my codebase. AI is gasoline and without someone with experience behind the scenes, they are just going to be 10x faster at knocking out unmaintainable spagetti code. When you run a saas company, code is only ONE factor among many you are maintaining. The other arguable more important one is the domain specific knowledge that exists in the heads of your talent. Give me the nerd that uses emacs with 5+ years of experience thinking though and solving problems without AI. I'll let him have copilot because he'll be the one writing and maintaining the code. More importantly, he'll have teh experience to know when copilot is leading him astray.