What is The Problem with Learning Development Frameworks?

Software development frameworks are a plenty! There are especially many front-end JavaScript based frameworks to choose from. This leads to many a nervous young developers trying to decide if they should learn:

- ReactJS
- AngularJS
- VueJS
- EmberJS
- MithrilJS

... Do they have a HobbitJS?

I go over in this video why you should not be too concerned with JS frameworks.

Learn all about my Mentoring program:

My popular courses:

My business courses:

My new business channel StudioWeb:

Experienced one of my courses? Please leave a Google review:

My social links:

Thanks!
Stef

#reactjs #vuejs #angularjs #javascript

[bjornarmar]

Dude what the heck falls from your tree at 4:19? Hope it was just a dead leaf and not a big-ass spider...

[FISS]

When you learn how to drive a manual car, it's a matter of seconds for you to be able to know how to drive an automatic one. But the other way around will always be wrong.
Same for the fundamentals, when you learn HTML/CSS/JS and master them, beeing able to use a frontend framework would be a matter of reading through the DOC (could be a couple of hours, a day or two grand max). Whereas, if you learn a framework as a first step (like a parrot learning how to repeat words), good look getting your head out of the mess you've put your self into.

[FISS]

Everyone who is selling "Everything should be microservices" has never delt with "transactional" operations and all the state validations that come with it. Managing "transactional" operations where a single operation is composed of multiple microservices targetting different servers and behaving all asynchronously is a pain if not impossible at all (for those who can't seem to understand this yet, try to roll back an already sent post request to a microservice if one of the upcoming ones has failed ... Try to think about reverting back 10 of them if the eleventh one failed ...)

[techedzee]

Micro service approach is actually a good modular pattern to follow.

[riccardopolacci]

Interesting points. I'm a Front End developer, I have commercial experience with Angular, React and Vue. I think what helped me learn these frameworks was the fact that I focused on 1, and after I "mastered" it, when I eventually jumped to the others the transition was smoother and faster. I've also invested more time into actually learning JavaScript (internally, details), and this actually taught me a lot about programming in general.

I agree that focusing on 1 thing will make you better in the other things. But, the issue is that nowadays the industry doesn't look for a "Capable developer", it mostly looks for "React Developer", "Angular Developer", etc. Like if a person with 5 years of experience in X framework would have issues learning a new framework based in the same language (JS). This industry pushes people wanting to learn all the new stuff in order to have an edge in the market.

I would also say that every day, Front End evolves more and more, it has become a specialised role in my opinion, where you need to learn stuff like: Flux pattern, Dumb vs Smart components, 100 flavours and patterns of CSS, transpilers, etc.

Indeed JavaScript ecosystem right now is overwhelming, that's why I just learnt Svelte. 🤣🤣🤣

[dannyyang]

I agree! Learn the fundamentals and don’t get too caught up in frameworks. Use what works for you in certain situations. On that note I still use jQuery, it’s lightweight and requires less code sometimes than vanillaJS.

[codezero]

I have seen a lot of this framework burn out. On the RTC live chat, this was a big topic. We DO need to focus on the fundamentals HTML, css, and JS. We should also know basic data structures and meaningful algorithms (not crazy leetCode puzzles). I am also a big fan of Martin Fowler and Bob Martin. Hey, they are old guys like me :-)

[owainharris]

React came out in 2013, and has been popular since 2014/2015. The whole framework burnout used to be a thing, but it’s settled down now.

[johnspencer]

Excellent video!! (hell, as always). The 'focus' portion of the video is just so true -- regarding any activity desired to be mastered.

[alexrafter]

Hey Stef, just an idea but timestamps or editing down to highlights/ best bits from the livestreams would be awesome 😎

[rossthemusicandguitarteacher]

Much love! These principles apply to music too.

[samarioantonio]

3:58 "I am not invested in the frameworks so much. I enjoy using Flutter though". I love Flutter.

[AgentZeroNine]

My focus

Front-end: Semantic HTML, CSS (with Flexbox and Grid for RWD), vanilla JavaScript basics and beyond, OOP, design patterns, data structures, and algorithms. Adding native web components and PWAs to the list at some point.

Back-end: Node.js, Express, MongoDB, MySQL.

Future: Rust or Java.

[IINoirII]

“I fear not the man who has practiced 10, 000 kicks once, but I fear the man who has practiced one kick 10, 000 times.” (c)

[divyanshsharma]

True design principles are important it helps to think a software in architectural way.

[agnostimous]

Hello, great video! Any book/ressource you recommend to learn best coding practices?

[davidbasil]

It depends on the task at hands.
Let's say your client/manager needs to add contact form to a static page with some ajax. Should you do it with Laravel and Angular?
No of course. It should be done with vanilla php and a little of jquery (oh, sorry, vanilla javascript) because the task is small and doesn't require any sophisticated architecture.
There is no best framework/tool for EVERY and EACH project/task in the world. But some tools are better for a particular work.

[pascavlad]

Whould you recommend to a 15 years boy to learn web development if he wants to get into programming?Can i get interships during my colleague if i know web development?

[Jollyprez]

As a contractor, the main thing you have to do is be able to pick-up new frameworks quickly. Because - you'll be stuck with whatever the company's guru decided upon before you got there. I've ended-up learning all kinds of bizarro things over the years - more than half of which are no longer "hot" - such as ColdFusion, MFC, TCL, Swift, CakePHP, CodeIgniter, and a dozen others I can't remember. Things are more fragmented on browser-side development. The main difference between them seems to be what I call the "Shell" vs "Skeleton" styles of frameworks. Shells are more constrictive and require close adherence to the framework designer's ideas. Skeletons are less didactic - you just hang stuff on the skeleton, so-to-speak, and have far more flexibility. That way, you can REALLY screw things up. :)

[neutralface]

In the end, it all comes down to giving bunch of 0's and 1's to computer's CPU to process. All the thing we use today are essentially just tools for making it more efficient to give these instructions for the computer.