[serge2k]

> I've seen devs who were perfectly comfortable with all the math and "real dev" practically break down when presented with a web project. More than one of them admitted to me after beating their heads against it for a few weeks that it was harder than it looked.

Because they haven't done it before.

Hard because you have to learn the framework of the week, deal with shitty tooling, and leverage design skills you haven't ever really had to develop is a very different thing than hard because you have to design and build a complex system with strict requirements and intractable problems.

[vinceguidry]

> hard because you have to design and build a complex system with strict requirements and intractable problems.

That sounds like web dev. The intractability of the problems comes from the fashion-like nature of how often things change and the speed at which they have to change. The more you learn, the more you can do, but also the requirements will change as a function of your abilities. Maintaining an business advantage demands it.

The framework doesn't have to change, the tooling can be self-designed, the design skills can be learned, and web dev remains hard and interesting. I understand that lots of devs don't appreciate it, but I still find it interesting after 5 years, and expect it to remain so after 20.

I liken it to a craft, take woodworking as an example. Sure, anybody can learn to bang nails into wood. But the way you hit a nail into a piece of wood the first time is going to be way different than the way you bang it in after 5 years, and it's going to be a totally different experience to the way you bang it in after 40 years.

There's a definite craft to choosing frameworks, growing tooling, and fashioning design to solve interface problems.

Is it as hard as hard math? No. Is it harder than 99% of people can do at all, and harder than 80% of software developers can do well? I fully believe so.