david celisI 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?
thinkbeforecoding@davidcelis boiler plate is usually a symptom of badly designed languages/frameworks/libraries.
Creating tools to write boilerplate faster is a stupid goal.
We should work on reducing the need for boilerplate by improving languages/frameworks/libraries...
Creating tools to write boilerplate faster is a stupid goal.
We should work on reducing the need for boilerplate by improving languages/frameworks/libraries...
cryptix@thinkb4coding @davidcelis In my years in this space I heard this so many times, and people usually nod, yet I can’t see any meaningful change. The people who like the coding part still rather build shiny new toys, mostly for themselves. And I mean, sure, you do you, but this isn’t driving adoption for people that try to solve their everyday problems.
@cryptix @davidcelis I understand, but this is still optimizing for solving the wrong problem.
@thinkb4coding @davidcelis I could have made this clearer but I agree that Silicon Valley fueled AI brings out the worst. Yet I also think the problem you outlined was a a thing before llms and vibe coding and we didn’t tackle it then because it’s more of an organizational then technical one. Now people actually have a toy to circumvent the problem, probably making it even worse. See linked in “vibe coding fixers”