I think some people are reading what was said too literal here.
I know what the post says but don't read it too literal. Think about what it says.
He's not saying you go out and write your own parser. He's not saying you go out and write your own web socket implementation. He's not saying you go out and write everything in pure machine language.
He's saying to think about what you're coding. Think about what is going on. Think about things before you even write code. Think how it fits with what you're currently doing.
When you start to do this then you actually can pick the right tool for the job. There is no 100% rule them all framework. Don't think there is or think you HAVE to do it in this.
That is what the post is actually saying. I know what it looks like it is saying if you just read it word for word, but like most things there is more too it.
Yes. But it's also tagged #beginners who don't have the experience or confidence to read between the lines and get at the gist. They will read it literally and be dismayed because it makes it sound like they need to write their own everything before being a good developer.
That is where I think I'll have to disagree.
I've been a beginner (we all have) and I remember vividly being a beginner. I remember the advice I got as a beginner. I've had some of my favorite nentors and even the one person who changed my entire life and got me interested in software development in the first place give me advice very similar to how this is written.
I believe part of being a beginner and learning is figuring out and taking the time to think about what your should do vs. researching "how do I do X an Y in Z framework."
So I'll stand by and say I've had similar advice when I was beginning and it was some of the best advice I ever got.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.