You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
There's a lot of thought and effort that go into large frameworks. You can't invest 0.01% of the effort & brain power and expect to come out on top. The best developers are those that know how to capitalize on collective past efforts. Those that stand on the shoulders of giants.
You don't need to solve problems that are already solved, just because you don't 100% like or understand the built-in solutions. A good framework will get the known problems out of the way to let you focus on what you're really trying to achieve.
A noticeable transition (during the 90s) has occurred according to G. J. Sussman: "The “analysis-by-synthesis” view of SICP — where you build a larger system out of smaller, simple parts — became irrelevant. Nowadays, we do programming by poking." See: http://lambda-the-ultimate.org/node/5335
say it again louder for the engineers in the back
For products or research, I agree. Although for learning it's great to rebuild certain aspects of a framework. It reduces cognitive load, increases intuition of the entire model, and leads to better use of the framework.
I've actually experienced cases where building the product without a framework was better, sure it needed a lot of refactorings but people could understand how everything worked instead of going around the framework all the time
Also later on when they do use a framework they are much more concious, use it better and understand the reasoning behind the decisions that framework took
Yes, yes & yes personally know few who were even admired for reinventing the wheel, their justification is often 'we don't the bloat that a framework comes with, we only need functionality X'
I’m gonna save this as my wallpaper for good measure. I am a culprit and I need to fix this.
Also open source project in particular and enterprise frameworks in general were not favoured for potential bugs & support issues, lack of documentation. I remember when Microsoft Linq to SQL came out and we used a method that didn't cater to null variables which another one did
So when this caused an issue in production and it had to be quickly fixed, boy that conversation with our manager wasn't pretty, use your imagination
I'm that kind of person. I think our value in a team lies in figuring out the frameworks ("is it buggy?" "no, we just don't use it the right way) and otherwise working on highly specific and self contained components. But just don't leave us in charge 
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
