Why is web programming looked down amongst programmers?

 Why is web programming looked down amongst programmers?

 

Web programming is awful. Hear me out:

• You’re usually forced to code in multiple languages
• Many of those languages have serious flaws and limitations
• The sands are constantly shifting as browsers, libraries, etc. change, often without discernible improvement
• Mysterious problems caused by near-invisible factors, sometimes outside your control, are frequent (e.g. strange proxy behaviour; caches)
• Very basic things arrive late and broken (I remember web developer friends’ excitement about finally getting sockets and a canvas to paint on)

When I meet a developer who likes web development, I assume that’s the only kind of development they do and they’re probably inexperienced. This could be my prejudice, of course; maybe client-side web development is better these days (I wouldn’t know; I’ve been avoiding it for years).

Web development is also a bit like Visual Basic programming in the 90s in that the bar to entry is very low (it’s easy to build something), but the standard of developer required to produce a really good result is extremely high (it’s very difficult to build something good). As a result, there’s an awful lot of really terrible code out there, written and maintained by developers who have no idea what good software design looks like. Software built for the web is not often built for a long life, and there’s a worryingly high tolerance for:

• Poor user experience (making things look great rather than making them work well)
• Poor stability (just hit refresh; don’t use the back button; clear your cache and try again)
• Poor performance (I swear, some web developers have no idea what ‘fast’ really means on a modern computer, and never test on a machine over 5 years old)
• High resource consumption (never mind, it’s just the client machine’s resources being wasted)
• Very poor maintainability (we’ll build a whole new one before we make significant changes to this one anyway)

I try not to look down on anyone though. Anyone can learn any kind of development, and getting tribal about technologies and disrespecting people who like things we don’t isn’t productive.

If a software developer didn't meet the deadline, how should a good manager respond?

https://www.quora.com/

If a software developer didn't meet the deadline, how should a good manager respond? Is pushing developers to work for long hours the right thing to do?

Originally Answered: If a software developer didn't meet the deadline how should a good manager respond? Does pushing developer to work For long hours a right thing to do?

There are some managers who like to put schedule risk off onto the dev team. If the team gets behind, make them work more hours until they catch up. This practice is E.V.I.L. It is like if your director asked you, as manager, to pay the company back from your own paycheck if your team goes over budget. The budget is the same kind of prediction of the future as a software schedule is. And as manager you are just as responsible.

Estimating schedules is hard, because it is predicting the future. There is a school of thought that this practice is so hard that teams ought to refuse to do it.

How should you handle a developer who is not good at predicting the future? Should you punish them by making them work more hours? Or should you get them a better crystal ball in the form of some kind of class on scheduling?

If you have a developer who is wasting time, always has facebook open, spends all afternoon yakking with the other devs, takes extended smoking breaks, etc., you should definitely push them to work harder. (I mean, duh.) If your developers are at their desks doing the job of developing software, punishing them for being late is both cruel and counterproductive.