We use copilot literally every day and it's extremely helpful, literally not a single developer at our company disagreed on the most recent adoption survey.

Maybe you're trying to use it to do too much, or in the wrong way?

Oh I'm glad you're the be all know all arbiter of all software developers, and not just some grump on the internet.

Its not about writing easy entry programs, it's about writing code robustly.

Writing out test code where tests are isolated from each other, cover every edge case, and test every line of code, is tedious but pays dividends. AI makes it far less tedious to write out that test code and practice proper test driven development.

A well run dev team with enough senior people that manages the change properly should increase in velocity if they're already writing robust code, and increase in code quality if they're not.

Pointing this out in company wide meetings is a fun past time.

It does save a lot of time and effort, and does lead to better code in the hands of a skilled developer. Writing out thorough test code and actually doing proper test driven development suddenly becomes a lot less onerous.

Their graph also has no numbers and is just there to help visualize the difference they're referring to.

Read the article before commenting.

The literal entire thesis is that AI should maintain developer headcounts and just let them be more productive, not reduce headcount in favour of AI.

The irony is that you're putting in less effort and critical thought into your comment than an AI would.

I started my programming career teaching myself to script and code to write tools to automate large aspect of my electrical engineering job. Eventually I hit the point, where my tools were getting huge and complicated and I realized that my professional software skills were lacking and I couldn't just keep producing this untested spaghetti code and hope to actually get things done in manageable way.

I then left for the world of professional software engineering, and in the time since, I've seen two companies that actually build software properly, and three companies producing worse code with worse practices than my self taught code from years ago.

Quite frankly the world of software development is downright embarassing to work in at times. I don't think we necessarily need to gatekeep software development with engineering degrees, but I do think that all developers should be required to take engineering ethics courses to understand their own responsibilities to push back and say no, this is not done and shippable until it's properly built and documented.

So you're saying mash both a bunch of times to be super sure?

Thank fucking god.

I got sick of the overhyped tech bros pumping AI into everything with no understanding of it....

But then I got way more sick of everyone else thinking they're clowning on AI when in reality they're just demonstrating an equal sized misunderstanding of the technology in a snarky pessimistic format.

If it's shockingly easy to produce then just do it and then you can write a declarative headline that doesn't need to use the word "could". If you can't then I'm guessing it's not that shockingly easy.

The most important traits for doing well at work (in this order):

• clear, effective, and efficient communication
• taking ownership of problems
• having your boss and team members like you on a personal level
• competence at your tasks