I became a software engineer because writing code is fun. Thinking through hard problems, designing elegant solutions, seeing the things you’ve built working for the first time… these moments are all deeply satisfying, so why in the world would I ever surrender them to AI?

https://davidcel.is/articles/writing-code-is-fun

Writing Code Is Fun

I became a software engineer because writing code is fun. Thinking through hard problems, designing elegant solutions, seeing the things you’ve built working for the first time… these moments are all deeply satisfying, so why in the world would I ever surrender them to AI?

@davidcelis
My colleagues say that AI helps with boring boilerplate… but I’d rather they used their meaty brains to remove the need for boilerplate, not instruct their clunkers to automate it.

Great blogpost. 100% agree.

@matthew Yah, if AI is actually helpful with "boring boilerplate", then a non-AI tool can do the same, more safely and with way less resources.

If not, it isn't really boileplate.

The more complex frameworks become, the more useful AI can seem, when the true value would be to pick less complex frameworks.

One of my worries is that AI can make people put up with crap complexity we do not need, simply because they feel more powerful having a tool that makes them feel like they master this complexity, rather than trying going for something simpler and better.

@davidcelis

@lettosprey @matthew @davidcelis 100% - it's a much bigger version of the problem "why bother understanding how to do this effectively when I can just add 5 more useEffects and some extra state variables" and instead of figuring out what you need where, you end up getting the same data 3 different times and making the client side experience awful and buggy. Now you don't even have to figure out how to do it wrong, you don't have to figure out anything