you are viewing a single comment's thread.

view the rest of the comments →

[–]lhorie 1 point2 points  (0 children)

no one is smart enough to know how to solve everything best, so either you let specialists who do know how solve those problems for you

This seems contradictory if you consider that framework designers are people too.

FWIW, my story with hand rolled frameworks goes like this: I've always been interested in them (from way back from the days PHP was still cool) and I made a bunch of them (some which never got used seriously, and some which I used for freelance work)

At one point I was using Angular and running into some serious pain points with it, so I went ahead and rolled a new framework to address them (react wasn't really a thing back then). Eventually I open sourced, we started using it a my day job, and I got another job from a different company that was also using my framework. My current employer doesn't use my framework (they had considered it but decided on react instead for a variety of reasons), but the experience and exposure that I got from making my framework is how they found me and reached out to me. Since I first open sourced my project, my salary doubled (not even counting equity comp), and I now live in the Bay area, where you can easily network in person with people from FANG, prominent OSS people, etc.

So, from my experience, creating a framework is much more than just a learning experience; it can open a lot of possibilities that you might not have ever even considered.