21: learning to love 'bad' code

 Let's face it: modern web frameworks are pretty bloated. Most people do not need 1000+ packages to achieve what they need to do. Yes, sometimes those frameworks are the best way to solve a problem, but more often than not you could get the job done far better with far less. 

... That being said, i feel like some devs have kind of gone too far in rejecting "unnecessary" complexity. You don't need to code everything in c or rust. Computers have gotten a lot better over the years: You might say that's an excuse for writing unoptimized code, but i feel like that's looking at it the wrong way. In the end, programming is about problem solving and choosing the right tool for the job. Often people forget that and start calling languages like python, js or php bad because they're slow. When actually using the software that only matters up to a certain point. Does your software run well enough to do what you need it to? Congrats, its good software. It all depends on your use case. Writing an os? Obviously use a lower level language for that. Making a personal blog? Screw it, python is fine! It all depends on what you are actually doing. There's a surprising amount of people that tend to forget that and start needlessly complaining about languages like php or JavaScript because they're not c. 

Go ahead, try out PHP or JavaScript sometime. They might not be the peak of efficiency, (though both _can_ be surprisingly fast) but they're fun, and help you actually get stuff done when you just need to make something quickly and don't care about squeezing out as much performance as possible.