Do Not Learn Frameworks – Learn the Architecture
1–10 of 86 posts
Re: Do Not Learn Frameworks – Learn the Architecture
#2One thing that I think is especially true with this mindset, is that being able to pull in just about any utility via npm has really changed the landscape for JS development.
Re: Do Not Learn Frameworks – Learn the Architecture
#3Totally agree. Frameworks may become obsolete or abandoned by their mantainers, but the key ideas of each one will remain.
Re: Do Not Learn Frameworks – Learn the Architecture
#4The problem is that job ads always say "We want experience in X, Y, Z." They never say "We want someone who can code without a framework, and could learn whatever we're using quickly."
Re: Do Not Learn Frameworks – Learn the Architecture
#5>Do I use frameworks? Only when it's not required to maintain a product in future.
I've been on the flip side of this too many times. Some outsourcing company developed a product using a framework (usually on a fixed-price bid), which enabled them to ship something that sort of mostly worked so they could get paid. Then, I'm stuck supporting and maintaining it, and it takes 3x-5x longer than it should because of the poor framework choice and poor usage of that framework.
Re: Do Not Learn Frameworks – Learn the Architecture
#6Good article, I agree with learning architecture first. No one should start learning by using framework first. But don't forget about "loosely coupled" frameworks like PhalconPHP. It allows you to code your own without using pre-built one.
Re: Do Not Learn Frameworks – Learn the Architecture
#7The problem is that job ads always say "We want experience in X, Y, Z." They never say "We want someone who can code without a framework, and could learn whatever we're using quickly."
Hi. We use Ruby on Rails, we want someone who can code without a framework and could learn whatever we're using quickly.
Re: Do Not Learn Frameworks – Learn the Architecture
#8The problem is that job ads always say "We want experience in X, Y, Z." They never say "We want someone who can code without a framework, and could learn whatever we're using quickly."
Good companies want you to be able to code well. They don't care if you know the framework or even the language.
Re: Do Not Learn Frameworks – Learn the Architecture
#9Let's say I'm building a web app and develop my own patterns and practices. Obviously it'll be a bad idea to have everyone working on my project create their own patterns and will make sense to mandate everyone follow one set of patterns so we don't have to keep context-switching whenever we're working on a different part of the app.
To an outsider who needs to now contribute code to my web app, what's the difference between following my patterns and following a framework's patterns if a framework was used instead?
What's good about most frameworks is the fact they come with documentation, tutorials, tests and all that good stuff so someone new to the framework can quickly get up to speed. The author even admits to having people have problems understanding his architecture.
My advice to the author is don't worry, people will eventually get better. JavaScript seemed inaccessible to a lot of people (including myself) until jQuery came along. The more jQuery code I wrote and gained more experience in JavaScript, the more I learned how little I needed to use jQuery to accomplish a ton of stuff. Backbone, Angular and other frameworks will probably have the same effect on people some day.
Re: Do Not Learn Frameworks – Learn the Architecture
#10Wondering where jQuery fits in the author's mind right about now.
Yes, it's a "library" but come on, all the framework versus principles narrative applies with that too.
Directly interacting with the DOM without abstraction seems way too risky, in exchange for some bloat.