Name: Anonymous 2018-04-22 2:05
Full stack web dev. Ha! What a joke. Real developers know more difficult shit like C++. Web is easy shit for plebs. Right?
People say you should use Bootstrap instead of doing manual CSS because it’s easier. But then you end up spending more time learning Bootstrap classes than it takes to learn actual CSS. And then you inevitably learn CSS anyway because you want to customize the layout with certain selectors in a way that Bootstrap doesn’t support. And you end up with a billion div elements with Bootstrap classes and your own ids to have both Bootstrap and custom CSS rules applied.
So you have to put your own custom CSS after the Bootstrap minified CDN-cached shit. If you mess up the order of linking, or z-index shit, then the site looks broken and it’s annoying yo debut even with browser dev tools. It might be dumb, but I use this for debugging CSS:
To make problematic shit stand out. Sometimes I inspect element but I do this too. It’s the web dev equivalent to printf debugging.
And when you look up Bootstrap tutorials they have to be for the very same version you’re using or else it won’t work.
People say you should learn Sass (a CSS preprocessor) because it’s “easier” than doing manual CSS. But then you end up spending a lot of time learning the ins and outs of Sass (or some other preprocessor) and then you end up on working on a project where you’re dealing with preexisting CSS and they don’t use preprocessors so you still end up having to learn CSS anyway. Sometimes there is a quirks mode workaround but people tell you it has to pass with no errors in some validated or test that nobody gives a shit about. So what’s the point of an preprocessor if it’s supposed to streamline things but then you end up just learnings mode stuff anyway?
Now someone is telling me to learn w3.css because it’s even easier than Bootstrap. I already learned Bootstrap and manual CSS and Sass though. Why are there so many redundant ways of doing the exact same thing?
People say you should use jQuery because it’s better than regular JavaScript. But really, you have to remember the differences between regular JS and jQuery and you have to link to your minified jQuery JS file in addition to the million other scripts and CSS files and it just becomes a huge mess of cross-site requests and bloat. It can take so long to load that you have to experiment with asynchronous shit or make pretty loading icons with CSS3 animations.
And people say ES6 is better than ES5 like with things like class-based inheritance over prototypical inheritance but you end up using ES5 anyway because of support issues. Then some people say you should use React or Angular. And Express and Node and PugJS. But Pug used to be called Jade, so you have to search for multiple things when you need help. And old documentation doesn’t work on newer shit.
Your packages.json file inevitably has a zillion dependencies and it takes a while to npm install everything and you have a bigger attack surface and there are so many features you have to secure that aren’t always explained well in tutorials or books.
And I didn’t even get into supporting legacy browsers or ones that simply aren’t standards-compliant. Separate shit for different user agents.
Backend shit like databases isn’t hard, but you have to learn SQL and NoSQL because MongoDB is getting pretty popular but relational databases aren’t quite dead yet. At least JSON is cool though. Better than XML.
Then you spend all this time learning MEAN and Django and Flask and Bootstrap and then you end up being put on some LAMP stack project anyway because there’s still a lot of work to be done on legacy code even though PHP is a pile of shit.
Some people think web dev is easy, but man, nobody uses vanilla HTML5/CSS3/JS. You gotta use all this other shit too. People who diss web development don’t realize how there are a million things you need to be familiar with and the tools come and go very quickly compared to old-school programming languages and frameworks.
People say you should use Bootstrap instead of doing manual CSS because it’s easier. But then you end up spending more time learning Bootstrap classes than it takes to learn actual CSS. And then you inevitably learn CSS anyway because you want to customize the layout with certain selectors in a way that Bootstrap doesn’t support. And you end up with a billion div elements with Bootstrap classes and your own ids to have both Bootstrap and custom CSS rules applied.
So you have to put your own custom CSS after the Bootstrap minified CDN-cached shit. If you mess up the order of linking, or z-index shit, then the site looks broken and it’s annoying yo debut even with browser dev tools. It might be dumb, but I use this for debugging CSS:
selector {
color: red;
background-color: red;
}To make problematic shit stand out. Sometimes I inspect element but I do this too. It’s the web dev equivalent to printf debugging.
And when you look up Bootstrap tutorials they have to be for the very same version you’re using or else it won’t work.
People say you should learn Sass (a CSS preprocessor) because it’s “easier” than doing manual CSS. But then you end up spending a lot of time learning the ins and outs of Sass (or some other preprocessor) and then you end up on working on a project where you’re dealing with preexisting CSS and they don’t use preprocessors so you still end up having to learn CSS anyway. Sometimes there is a quirks mode workaround but people tell you it has to pass with no errors in some validated or test that nobody gives a shit about. So what’s the point of an preprocessor if it’s supposed to streamline things but then you end up just learnings mode stuff anyway?
Now someone is telling me to learn w3.css because it’s even easier than Bootstrap. I already learned Bootstrap and manual CSS and Sass though. Why are there so many redundant ways of doing the exact same thing?
People say you should use jQuery because it’s better than regular JavaScript. But really, you have to remember the differences between regular JS and jQuery and you have to link to your minified jQuery JS file in addition to the million other scripts and CSS files and it just becomes a huge mess of cross-site requests and bloat. It can take so long to load that you have to experiment with asynchronous shit or make pretty loading icons with CSS3 animations.
And people say ES6 is better than ES5 like with things like class-based inheritance over prototypical inheritance but you end up using ES5 anyway because of support issues. Then some people say you should use React or Angular. And Express and Node and PugJS. But Pug used to be called Jade, so you have to search for multiple things when you need help. And old documentation doesn’t work on newer shit.
Your packages.json file inevitably has a zillion dependencies and it takes a while to npm install everything and you have a bigger attack surface and there are so many features you have to secure that aren’t always explained well in tutorials or books.
And I didn’t even get into supporting legacy browsers or ones that simply aren’t standards-compliant. Separate shit for different user agents.
Backend shit like databases isn’t hard, but you have to learn SQL and NoSQL because MongoDB is getting pretty popular but relational databases aren’t quite dead yet. At least JSON is cool though. Better than XML.
Then you spend all this time learning MEAN and Django and Flask and Bootstrap and then you end up being put on some LAMP stack project anyway because there’s still a lot of work to be done on legacy code even though PHP is a pile of shit.
Some people think web dev is easy, but man, nobody uses vanilla HTML5/CSS3/JS. You gotta use all this other shit too. People who diss web development don’t realize how there are a million things you need to be familiar with and the tools come and go very quickly compared to old-school programming languages and frameworks.