I think there's a lot here that even as an experienced engineer I hate to start doing from scratch. Now combine that with time to focus on the business
* Where to deploy?
* Where to store the code?
* Which library to send emails with?
* Which 3rd service to send emails with?
A long time ago I spent 2-3 weeks building something to do all the above. After completion, I started going to customers and realised those 2/3wks were basically wasted time because I could have just put a google form and would've done just as good a job. Except now you get something a bit better than that.
I wrote an article[1] about this. It's aimed towards intermediate CSS peeps trying to understand how to organize CSS. It focuses on BEM mostly but still offers a decent look into managing CSS
How do you find Sapiens? I started reading it (about pg. 50 now) but I find it too full conclusions/statements that are not really founded on data. Basically, it tends sets up two or more premises and then somehow draws a conclusion that isn't in anyway related to the original premises (i.e: almost pseudoscience).
This is hands down the best book I read about node. As long as you're already comfortable with JS, this should be more than enough to have you write your own Node apps. Best thing about it: it doesn't limit your to writing node servers like most other intro books. You start seeing node as JS removed away from the browser to a standalone language and not just a way to write javascript web servers.
When I went through it, it was all in es5. So, like I said, if you're comfortable with JS - this shouldn't be a turn-off
I find most people who have gripes with JS prototypes are the ones who are used to classical inheritance. Overall, the more I understand JS, the more I'm convinces most issues raised are personal preferences.
You become exceptional by being curious and never satisfied. I don't think you can teach that. I mean, you can blurt it out to people all day but it takes intrinsic motivation to stay awake until 2am because you want to chase some random thing down the rabbit hole.
This is exactly how I felt when working with OSS. I wanted to increase my rep by contributing to OSS projects but most times I was looking for a problem that fits my solution. I was barely useful to a project as a result. Later on, I was working on a friends app (testing it) and I noticed bugs here and there. Fixed them and kept finding bugs on other projects that I was actually interested in.
Overtly bias portrayals to an extent that it becomes celebratory in nature. While I can understand the need to do so, it has become so ingrained that it is impossible find any historically objective documentary that allows viewers to understand the mindset of the period.
* Where to deploy? * Where to store the code? * Which library to send emails with? * Which 3rd service to send emails with?
A long time ago I spent 2-3 weeks building something to do all the above. After completion, I started going to customers and realised those 2/3wks were basically wasted time because I could have just put a google form and would've done just as good a job. Except now you get something a bit better than that.