As a senior software engineer, only a fraction of your time is spent in actually writing code. The majority of the time, you will be _talking_ about your code. If you want to grow in your career, you need to invest in those skills that make you a better communicator and influence others more effectively.
At Google, I was involved in a project where we instrumented the desktop of engineers at Google. We measured all the things they did during the work day to figure out what workflows makes them the most productive.
I learned a few things from the Tempo project at Google:
- Productivity is hard to measure.
- Happiness is an excellent proxy metric for productivity.
- Context switches take us out of the flow and hurt productivity.
- Engineers hate meetings (see previous bullet).
- Most engineers have barely done any communication training.
- Only 30% of time spent by Google engineers goes to coding.
- Communication skills are key to career growth as an engineer.
Learn how to communicate better at chrislaffra.com/c4e
At Google, I was involved in a project where we instrumented the desktop of engineers at Google. We measured all the things they did during the work day to figure out what workflows makes them the most productive.
I learned a few things from the Tempo project at Google:
- Productivity is hard to measure.
- Happiness is an excellent proxy metric for productivity.
- Context switches take us out of the flow and hurt productivity.
- Engineers hate meetings (see previous bullet).
- Most engineers have barely done any communication training.
- Only 30% of time spent by Google engineers goes to coding.
- Communication skills are key to career growth as an engineer.
Learn how to communicate better at chrislaffra.com/c4e
No comments:
Post a Comment