I think there's a certain amount of privledge in being a tech leader, or self employed developer.
What the author calls "extreme side B", is what most of us go in to work and have to do every day. Everything you do has to be attached to business value.
It's sad the web becomes less learnable every day, but telling people not to use frameworks and push pixels around, is out of touch, and pretty much impossible for most of us.
Fair enough, although I don't think the argument is whether one should push pixels or use a framework. Modern CSS is very good at dealing with responsive layouts in a way that doesn't have one manually moving components around. Neither did I mean to imply that a developer shouldn't care about the business value of their work, but rather, that the discussion is around whether this can be done without removing the parts that make the web accessible. "No" is a valid answer, but it's an attitude as extreme as my own of "everything should be accessible", in the sense that these attitudes describe polar opposites, and most people would compromise somewhere along the middle (though most would lean one way or the other).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think there's a certain amount of privledge in being a tech leader, or self employed developer.
What the author calls "extreme side B", is what most of us go in to work and have to do every day. Everything you do has to be attached to business value.
It's sad the web becomes less learnable every day, but telling people not to use frameworks and push pixels around, is out of touch, and pretty much impossible for most of us.
Fair enough, although I don't think the argument is whether one should push pixels or use a framework. Modern CSS is very good at dealing with responsive layouts in a way that doesn't have one manually moving components around. Neither did I mean to imply that a developer shouldn't care about the business value of their work, but rather, that the discussion is around whether this can be done without removing the parts that make the web accessible. "No" is a valid answer, but it's an attitude as extreme as my own of "everything should be accessible", in the sense that these attitudes describe polar opposites, and most people would compromise somewhere along the middle (though most would lean one way or the other).