Sarcasm aside, it's insane that after this incident, it's being labeled as a "training accident" when it so obviously wasn't.
116 karma · joined September 30, 2013
Sarcasm aside, it's insane that after this incident, it's being labeled as a "training accident" when it so obviously wasn't.
Frameworks also establish a common way of doing things like tracking state. For example, in vanilla projects, one developer might implement it in a unique way that no one else understands. You want to work with code that works well with multiple developers on larger projects.
It's still fun and interesting using vanilla for personal projects. I built a bunch of apps with just a CSS framework and JS was vanilla. (my apps: https://lewdev.github.io)
For some reason, it helped me a lot. Also in my mid-30s.
You're probably pretty good at the things you know, just whip something you could easily do but useful and you'll get a lot of satisfaction.
I also think it's burn out. I personally struggled to learn React and perhaps had some burn out but persevered because I was building things on the side. It was fun and great distraction and motivator while struggling to learn React. I think I'm pretty good at it now but I felt like I was in a rut for a long time.
> Do your own thing.
The article points out "A delusion is created that progress is made." and I agree that consuming content should not be mistaken for progress, rather you should also actively act on the content you consume. Create something out of it.