Skip to content
loading...

Learning Frameworks and APIs vs Software design principles

twitter logo github logo ・1 min read  

Found it very interesting and informative to be discussed.
Frameworks and APIs change fast. Software design principles are evergreen. Learn principles that translate across language barriers

twitter logo DISCUSS (3)
markdown guide
 

I think a big part of this question is motivation.

I'm often more motivated by the tangible wins, the stuff that comes with frameworks and APIs usually. But then the long term gains come from the underlying stuff.

I think starting with the frameworks and working back to the fundamentals is a reasonable approach.

 

There's a learning style component as well. I've known people who want to read the manual before they use a new thing - which I see as analogous to principles thinking. Some folks prefer to jump in - frameworks.

You can get a lot done without understanding why it works in a framework, and you can understand a lot of theory without ever writing code that does something interesting. The trick, as usual, is to find a balance.

 

The frameworks "normally" already implement the design patterns very well. Learning to use them is a good decision.

The design patterns are also important and every developer should know them.

Which one to learn first?
If you want to start quickly writing code, go through the frameworks and then learn the patterns.
If time is not a problem, go for the design patterns, but do not forget the frameworks!

Classic DEV Post from Mar 20

What was your win this week?

Got to all your meetings on time? Started a new project? Fixed a tricky bug?

Oliver Mensah profile image
Software Developer, Developer Community Builder, Technical Speaker, Writer & Trainer, Currently a National Service Personnel at Agro Innova Company Limited

Sore eyes?

dev.to now has dark mode.

Go to the "misc" section of your settings and select night theme ❀️