Re:How Does setState Know What to Do?
by danabramov on Sunday December 09, 2018 @07:41AM
(#18640595)
FWIW my job role is just software developer. I try to help people because I like being a part of the community and like explaining things to others that somebody explained to me. But I’m not officially a DevRel. Although I guess I fit the shoes.
Re:How Does setState Know What to Do?
by kaycebasques on Sunday December 09, 2018 @01:22PM
(#18642340)
Right, didn’t mean to imply that you only did DevRel. I think most React users know that you’re on the core team. Just wanted to suggest to the general HN community that your consistent efforts around helping the React community might be a factor of React’s success. Whenever there’s a post here on HN about why framework A is a success whereas framework B is a flop, the focus is usually on technical factors or developer ergonomics.
> But I’m not officially a DevRel. Although I guess I fit the shoes.
Those are usually the best DevRel folks imho. Love the work you do!
Re:How Does setState Know What to Do?
by mcintyre1994 on Sunday December 09, 2018 @08:44AM
(#18640815)
Taylor Otwell with Laravel definitely fits this category too.
Famous DevRel I know and what they've been promoting to great success:
- Dan Abramov, Redux and React.
- Evan You, Vue.js
- Lea Verou, Prism, Bliss and CSS in general.
- "@dhh", Ruby on Rails.
- Sindre Sorhus, npm and indie JS.
Note: I just say they have greatly helped to the success, no that these are their projects.
On the other hand, we all know some projects that succeed despite their founders being really bad at DevRel... but those are so rare and basically just put a lot of efforts in something related but not the same (marketing, first to the market, 10x better technically, etc).
My main focus right now is learning how to get better at this since I'd love to do OSS fulltime. Any tip on how to get there would be greatly appreciated. I'm trying to learn mainly from Dan and Evan since IMHO they are next-level in this specific area :)
PS, since you work for Chrome DevTools, I imagine you are in Google. I think, besides the issues of Angular 1->2, the real reason Angular stayed behind is that there were no highly visible DevRels.