It’s not a popular opinion but you’re entirely right.

AI isn’t copying in the way that most people think it is. It truly is transformative in all the tradition copyright ways.

Is it copyright infringements if my company pays an employee to study the internet and that makes them capable of animating a frame from the Simpsons? No, it’s copyright infringement when that company publishes that copyright infringing work.

The reality is that copyright has always been a nonsense system and ‘fair use’ concepts were also nonsense and arbitrary. AI algorithms just let us expose how nonsense they are at scale.

I really wish Vercel would put more effort into the static site generation side of Nextjs, but they won’t because that inherently makes them no money.

If they pay to power it with sustainable energy then it doesn’t. Simple as that. Energy use is really not a problem.

AI’s biggest problem is that it accelerates the effects of capitalism and wealth concentration, and our societies are not set up to handle that, or even to adapt particularly quickly.

I worked at a major tech company and their attitude was ‘if this becomes popular enough, and copyright is an issue, we’ll just pay artists to produce training data en masse’.

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?

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.

It would look a lot better if you just pressure cleaned the wall and painted it normally.