Is it? I mean I can always run to home depot and cobble something together based on books, youtube, and AI guidance, but I know when I need a professional.
I don't think any trade was ever harmed by the existence of hardware stores. Much the same, AI is not harming dev work. It's filling gaps where no product could exist before.
Big tech does not like DIY unless they control it and that's the actual story, not attacking devs and telling them they're obsolete. Why do you insist on avoiding that story and coming back here to argue with devs?
If I tell you to build me a house and you do so, I have not built the house.
I can give you requirements, give you feedback during the process, and otherwise contribute to the design, but at the end of the day I did not build the house.
I have no idea what this analogy is meant to communicate. If you're trying to suggest that software construction is only intentional or attributable if you write source code by hand, I'll just come back and say you haven't legitimately build anything unless you hex-edited it in machine code.
It's meant to communicate that building is something that requires effort on the part of the builder.
I don't write assembly, but I still had to learn how to code. I had to practice and put in the effort to develop it as a skill. Then, when I write something, I have to put in the effort to do it.
Of course, building things with AI generally takes varying levels of domain knowledge and guiding for now, but if we're talking about ordinary users making their own software, the implication is that in some cases existing skill won't be necessary, if not now then eventually.
At that point it would be truly effortless, and I don't think that you can rightfully say you built something if it required zero effort on your part.
Is it? I mean I can always run to home depot and cobble something together based on books, youtube, and AI guidance, but I know when I need a professional.
I don't think any trade was ever harmed by the existence of hardware stores. Much the same, AI is not harming dev work. It's filling gaps where no product could exist before.
Big tech does not like DIY unless they control it and that's the actual story, not attacking devs and telling them they're obsolete. Why do you insist on avoiding that story and coming back here to argue with devs?
If I tell you to build me a house and you do so, I have not built the house.
I can give you requirements, give you feedback during the process, and otherwise contribute to the design, but at the end of the day I did not build the house.
I have no idea what this analogy is meant to communicate. If you're trying to suggest that software construction is only intentional or attributable if you write source code by hand, I'll just come back and say you haven't legitimately build anything unless you hex-edited it in machine code.
It's meant to communicate that building is something that requires effort on the part of the builder.
I don't write assembly, but I still had to learn how to code. I had to practice and put in the effort to develop it as a skill. Then, when I write something, I have to put in the effort to do it.
Of course, building things with AI generally takes varying levels of domain knowledge and guiding for now, but if we're talking about ordinary users making their own software, the implication is that in some cases existing skill won't be necessary, if not now then eventually.
At that point it would be truly effortless, and I don't think that you can rightfully say you built something if it required zero effort on your part.
1 reply →