“As much as I’d love our code to be fully compliant with the great programming practices of this world, I’d rather have it working — if possible before the heat death of the Universe.”
Well I get the point of “you should learn what’s behind”, but no one ever said that because they were using a framework, they’d never need to learn the underlying technology.
I started with AngularJS and progressively learnt how it works behind the scene. I learned new patterns and coding good practices, I learned its strengths and shortcomings, what to watch out for when coding things on my own (even outside of AngularJS).
So in retrospect, I’d encourage newcomers to actually use a framework so that they get a glimpse of what is recommended to do, what is comfortable to use, so they can slowly get up to speed on what they need to know about the web without shoving their head into a wall of bricks, because right now that’s what webdev is to the unwarned newby.
If I said “Don’t use any of that, do your own stuff to better understand”, I’d expect them to probably do shit, get frustrated at their unmaintainable and buggy mess, do some more shit, get frustrated again, quit and go become a carpenter or something.
“I’m fascinated by wood. I’d like to decorate my appartment with wooden furniture then later maybe make my own, where could I buy som…
— Pffrt, don’t buy wooden furniture, you’ll never truly understand the beauty of wood. Start by making your own furniture, so that you really understand what you’re getting into, the implications behind every table and chair you see. Feel the underlying material, if IKEA is making wooden stuff, so can you!
— Ugh, maybe I’ll become a programmer instead.”
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Bollocks.
Well I get the point of “you should learn what’s behind”, but no one ever said that because they were using a framework, they’d never need to learn the underlying technology.
I started with AngularJS and progressively learnt how it works behind the scene. I learned new patterns and coding good practices, I learned its strengths and shortcomings, what to watch out for when coding things on my own (even outside of AngularJS).
So in retrospect, I’d encourage newcomers to actually use a framework so that they get a glimpse of what is recommended to do, what is comfortable to use, so they can slowly get up to speed on what they need to know about the web without shoving their head into a wall of bricks, because right now that’s what webdev is to the unwarned newby.
If I said “Don’t use any of that, do your own stuff to better understand”, I’d expect them to probably do shit, get frustrated at their unmaintainable and buggy mess, do some more shit, get frustrated again, quit and go become a carpenter or something.