Fixed some typos. I'm not sure how I feel about this. On the one hand, it's a bunch of devs reviewing something on Github, so you expect a bunch of comments about syntax. On the other hand, the content is basically a blog, so you'd expect comments about the ideas. I just don't know how to respond! FWIW: I didn't produce the content present here. Thank for producing that high-quality post Can I get permission to translate it to my mother tongue Haitian Creole Of course, you will get the credit.
You wrote about growth mindset but didn't recommend Carol Dweck 's great book Mindset on the reading list. I believe it would be a great addition. BTW: Thanks for this gist, it's awesome. I agree with the majority.
Skip to content. Sign in Sign up. Instantly share code, notes, and snippets. Last active Nov 25, Embed What would you like to do? Embed Embed this gist in your website. Share Copy sharable link for this gist. Learn more about clone URLs. Download ZIP. Focus on high leverage and not just easy wins. Optimize for Learning Change jobs if you have to. Optimizing for learning is high leverage. Adopt a growth mindset. Talk to people. Become good at telling stories.
It gets better with time. Those with a growth mindset believe that they can cultivate and grow their intelligence and skills through effort. Own your story. Invest in the rate of learning Learning compounds.
Compounding leads to exponential growth. Earlier the compounding starts, the better. Working on unchallenging tasks is a huge opportunity cost. You missed out on compounded learning. Prioritize learning over profitability. Invest your time in activities with the highest learning rate. Opportunity to choose high impact work. Make sure you are working on high priority projects. Openness: Look for culture with curiosity, where everyone is encouraged to ask questions.
Fast Paced. People smarter than you. Autonomy: Freedom to choose what to work on. While on Job Make a daily habit of acquiring new skills. Read code written by brilliant engineers. Jump fearlessly into code you don't know. Always be learning. Invest in skills that are in high demand. Read Books.
Attend Conferences. Build and maintain strong relationships. Prioritize Regularly Opportunity cost of working on wrong ideas can set back growth by years. Prioritize tasks based on ROI. Regular prioritization is high leverage activity. Don't try to remember stuff. Brain is bad at remembering. It's rather good at processing. Ask yourself regularly: Is this the most important thing I should be working on?
Focus on what directly produces value. Learn to say no. Focus on the important and non-urgent. Find ways to get into flow. Limit the amount of Work in Progress. Cost of context switching is high. Prioritizing is difficult. Prioritization is high leverage.
It has huge impact on your ability to get right things done. Invest in Iteration Speed Continuous Deployment is high leverage.
Move fast to learn fast. Move fast and break things. Moving fast enables us to build more things and learn at faster rate. Invest in time saving tools.
If you have to do something more than twice, write a tool the third time. Tools are multipliers that allow your to scale your impact beyond the confines of a day. Faster tools get used more often. Faster tools can enable new workflows that previously weren't possible. Productivity skyrockets with tools. Time saving property of tools also scale with team adoption. Shorten your debugging and validation Loops. Extra time spent in optimizing debugging workflow can help you fix annoying bugs with less headache.
Debugging is hard. It's time consuming. Upfront investments to shorten debugging loops are worth it. High test coverage to reduce build and site breakages.
Fast unit tests to encourage people to run them. Fast and incremental compiles and reloads to reduce development time. Master you programming environment. One editor. One high level language. Automate manual workflows. Use interactive shell.
Make running specific tests easy. Faster you can iterate, faster you can learn. Measure what you want to Improve Use metric to drive progress. If you can't measure it, you can't improve it.
Good metric. Helps you focus on right things. Drives forward progress. Helps you guard against future regressions. Performance ratcheting : Any change should strictly improve the metric. Bad metric can lead to unwanted behavior. Metric you choose influences your decisions and behavior. Look for metric that, when optimized, maximizes impact for the team. Actionable metric - Whose movement can be casually explained by team's effort.
Choosing a metric is high leverage. Dedicate time to pick right metric. Instrument everything to understand what's going on. Measure anything, measure everything. Graphite, statsd. A single line of code lets you define a new counter or timer on the fly.
Measuring goals you want to achieve is high leverage. Internalize useful numbers. Knowledge of useful numbers provide a valuable shortcut for knowing where to invest efforts to maximize gains. Need upfront work. Need not be accurate, ballpark idea suffices. Knowing useful numbers enables you to do back of the envelope calculations to quickly estimate the performance properties of a design without actually building it.
Internalizing useful number help you spot anomalies. Be skeptical about data integrity. Log data liberally. Build tools to iterate on data accuracy sooner. Examine data sooner. When numbers look off, dig in to it sooner. Validate your ideas early and often. I share everything that I've learned from the world's best engineering leaders in my newsletter, so that you can create the most meaningful impact you're capable of.
Join me, and discover what's possible. I can't recommend edmondlau's Effective Engineer mailing list enough. The first email alone was life changing. Wow, edmondlau's new book is chock full of actionable techniques and proven habits to help engineers succeed. I hope more people embrace Edmond's philosophy and techniques to make their companies and careers more successful. Accelerate your career growth. Spend less time grinding on tedious tasks.
Turn your effort into impact. Get hundreds of actionable tips and habits in The Effective Engineer — a book that has already become required reading for many engineering teams.
0コメント