Maybe this is a neurodivergent thing, but I have, as long as I can remember, always had the following progression in my mind: "What are you doing? No, that's this situation's name, what is this really?" and I'd continue a few times seeking the "larger problem, the more basic problem being solved" that whatever I was doing "really is". That "basic problem" was "communicating" far more frequently than I expected, and t…
Indeed. If we SW developers define ourselves as 'coders', we could easily end up into this identity crisis which the article seems to refer to. But in fact we are much more than that. We are problem solvers and a big part of it is understanding, defining and refining the problem itself and in finding an elegant solution. The meaningfulness comes from all the communication and experimenting involved with that process,…
The AI vendors want to sell to upper management that that part is what's slowing their company down or costing a lot of money, but I don't think it's that. And in a few years (or now already), AI tooling will probably be an accepted part of the toolchain, but software engineers will always be necessary.
Cobol said you won't need coders anymore because it's basically English. Dreamweaver and Frontpage said you won't need to know HTML because you can just build a website by clicking and typing. No-code platforms said you won't need coders anymore because you can just click and drag. AI evangelists say you don't need coders anymore because you just type in a prompt and working software comes out.