146 karma · joined August 11, 2019
1. Reading academic papers.
2. Being very hands-on; always implementing something, even it means trial and error. (Re #1: A lot of times, I end up implementing ideas from interesting papers that I’ve read.)
3. Doing my best to be around smart folks and learn from them (i.e., going to technical events, developing mentors, etc.).
4. Never giving up! This seems cliché to say, but forcing that mindset on myself has helped me tremendously for especially hard topics/domains (e.g., distributed systems). (Even if I have to reread a paper 10x before I fully understand it, I’m willing to do that.)
This is quite debatable and hard to measure, given the problem that Standard solves. As an anecdote, I just started a new TypeScript-based project a few days ago and I’ve spent the past few days mostly dealing with configuration. That’s perfectly fine to me for a personal project where I’d like to decide every aspect of the configuration, but let’s say this was for a fast-moving startup, it’s probably a smarter idea, for most projects, to simply adopt Standard et al. and call it a day. Practically speaking, if you consider a software engineer’s salary and other important factors, I don’t think it’s fair, or accurate, to claim that Standard doesn’t save companies thousands of dollars; it almost certainly does