Because I'm a lazy bastard. Only in a few personal projects I've built things from scratch (backend), And I did that because I was really interested on building those systems the best way I could and because that specific feature was really the core of my project and the one I thought it should not depend on third party software.
When you have deadlines and you are going to forget everything about that project after 12 months. It does not really matter how you build it and how much effort you spent on it. You just need to finish it.
Only when you are your own client you are critical enough to build things from scratch.
Frameworks make product teams less productive over time. As the system grows in complexity, the boundaries of the framework go from being a productivity boost to a constraining factor in developing maintainable solutions. twitter.com/Atrix256/statu…
21:55 PM - 29 Nov 2019
Alan Wolfe
@Atrix256
Quote this tweet with an opinion about programming that will get you unjustly dunked on. 😂
(I'm going first)
31
215
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.
This is why I think I use frameworks...
Because I'm a lazy bastard. Only in a few personal projects I've built things from scratch (backend), And I did that because I was really interested on building those systems the best way I could and because that specific feature was really the core of my project and the one I thought it should not depend on third party software.
When you have deadlines and you are going to forget everything about that project after 12 months. It does not really matter how you build it and how much effort you spent on it. You just need to finish it.
Only when you are your own client you are critical enough to build things from scratch.
I like this reply, as it focuses on where frameworks shine: short term, quick project based work for a client to a deadline.
But then I remember this tweet...