2,619 karma · joined January 22, 2015
The author there does the absolute minimum of interaction.
Issues not following exactly the template or lack a repro gets closed immediately without any comment, actual bugs also see very limited comment or openness to discussion.
It felt a bit weird at first, but I do get the author and the library is succesful, maybe exactly because of this approach.
It made me reconsider some of the effort I spend in my open source projects with useless issues / comments.
In bed, phone out of reach and reading one hour, sleeping half an hour was super efficient for me. You only process material while sleeping anyway.
I haven't read eloquent JS though, you say it's a different level of learner. Can you expand a bit? Is Eloquent for after "you don't know js" or vice-versa?
Edit: nevermind, reading the TOC of eloquent JS gave me a good enough idea
Never in the history of software has one lost a sale due to how the buttons of their product look like.
And I guarantee you that their internal library will be worse than popular options out there. The amount of time I've been in meetings where 10 smart, well-paid people from 10 different products in a company are endlessly discussing paddings on an input field... It's just a complete waste of time.
There's zero value in reinventing how buttons and inputs should look like.
I've worked for many companies, big and small, and they all had the arrogance to believe they need their own component libraries, reinventing the wheel out of ego.
My advice: you're not that special, just pick a component library and spend your precious time building actual value.
- 'knots' is faster to say on the radio than 'kilometers per hour'
- the way the world is divided in wgs84, maked it so that 1 degree of latitude equals exactly 60 miles. So that makes quick measurements a bit easier.