出版社: The Effective Bookshelf, Palo Alto, CA.
副标题: How to Leverage Your Efforts in Software Engineering to Make a Disproportionate and Meaningful Impact
出版年: 2015-3-19
页数: 260
定价: USD 39.00
装帧: Paperback
ISBN: 9780996128100
内容简介 · · · · · ·
The most effective engineers — the ones who have risen to become distinguished engineers and leaders at their companies — can produce 10 times the impact of other engineers, but they're not working 10 times the hours.
They've internalized a mindset that took me years of trial and error to figure out. I'm going to share that mindset with you — along with hundreds of actionable t...
The most effective engineers — the ones who have risen to become distinguished engineers and leaders at their companies — can produce 10 times the impact of other engineers, but they're not working 10 times the hours.
They've internalized a mindset that took me years of trial and error to figure out. I'm going to share that mindset with you — along with hundreds of actionable techniques and proven habits — so you can shortcut those years.
Introducing The Effective Engineer — the only book designed specifically for today's software engineers, based on extensive interviews with engineering leaders at top tech companies, and packed with hundreds of techniques to accelerate your career.
For two years, I embarked on a quest seeking an answer to one question:
How do the most effective engineers make their efforts, their teams, and their careers more successful?
I interviewed and collected stories from engineering VPs, directors, managers, and other leaders at today's top software companies: established, household names like Google, Facebook, Twitter, and LinkedIn; rapidly growing mid-sized companies like Dropbox, Square, Box, Airbnb, and Etsy; and startups like Reddit, Stripe, Instagram, and Lyft.
These leaders shared stories about the most valuable insights they've learned and the most common and costly mistakes that they've seen engineers — sometimes themselves — make.
This is just a small sampling of the hard questions I posed to them:
What engineering qualities correlate with future success?
What have you done that has paid off the highest returns?
What separates the most effective engineers you've worked with from everyone else?
What's the most valuable lesson your team has learned in the past year?
What advice do you give to new engineers on your team?
Everyone's story is different, but many of the lessons share common themes.
You'll get to hear stories like:
How did Instagram's team of 5 engineers build and support a service that grew to over 40 million users by the time the company was acquired?
How and why did Quora deploy code to production 40 to 50 times per day?
How did the team behind Google Docs become the fastest acquisition to rewrite its software to run on Google's infrastructure?
How does Etsy use continuous experimentation to design features that are guaranteed to increase revenue at launch?
How did Facebook's small infrastructure team effectively operate thousands of database servers?
How did Dropbox go from barely hiring any new engineers to nearly tripling its team size year-over-year?
What's more, I've distilled their stories into actionable habits and lessons that you can follow step-by-step to make your career and your team more successful.
The skills used by effective engineers are all learnable.
And I'll teach them to you. With The Effective Engineer, I'll teach you a unifying framework called leverage — the value produced per unit of time invested — that you can use to identify the activities that produce disproportionate results.
Here's a sneak peek at some of the lessons you'll learn. You'll learn how to:
Prioritize the right projects and tasks to increase your impact.
Earn more leeway from your peers and managers on your projects.
Spend less time maintaining and fixing software and more time building and shipping new features.
Produce more accurate software estimates.
Validate your ideas cheaply to reduce wasted work.
Navigate organizational and people-related bottlenecks.
Find the appropriate level of code reviews, testing, abstraction, and technical debt to balance speed and quality.
Shorten your debugging workflow to increase your iteration speed.
Use metrics to quantify your impact and consistently make progress.
作者简介 · · · · · ·
For the past decade, Edmond Lau has worked as a software engineer in some of the top technology companies in Silicon Valley, including Google, Ooyala, Quora, and Quip.
He's passionate about building great engineering teams. He's interviewed over 500+ engineering candidates throughout his career as well as spoken to teams across the country on how to build great engineering cult...
For the past decade, Edmond Lau has worked as a software engineer in some of the top technology companies in Silicon Valley, including Google, Ooyala, Quora, and Quip.
He's passionate about building great engineering teams. He's interviewed over 500+ engineering candidates throughout his career as well as spoken to teams across the country on how to build great engineering cultures. At Quora, he built out the onboarding and mentoring programs used to train dozens of new engineering hires and helped grow the team from 12 to over 70.
His engineering and career advice has been featured on Forbes, Time, Slate, Inc., and Fortune. He's also guest lectured at both MIT and Stanford on software design.
He holds a Bachelor's and Master's in Computer Science from MIT.
目录 · · · · · ·
Part 1: Adopt the Right Mindsets 7
1. Focus on High-Leverage Activities 9
2. Optimize for Learning 19
3. Prioritize Regularly 41
Part 2: Execute, Execute, Execute 61
· · · · · · (更多)
Part 1: Adopt the Right Mindsets 7
1. Focus on High-Leverage Activities 9
2. Optimize for Learning 19
3. Prioritize Regularly 41
Part 2: Execute, Execute, Execute 61
4. Invest in Iteration Speed 63
5. Measure What You Want to Improve 83
6. Validate Your Ideas Early and Often 107
7. Improve Your Project Estimation Skills 127
Part 3: Build Long-Term Value 153
8. Balance Quality with Pragmatism 155
9. Minimize Operational Burden 173
10. Invest in Your Team's Growth 193
Epilogue 215
Appendix 217 Acknowledgments 221 Notes 223 About the Author 247
· · · · · · (收起)
喜欢读"The Effective Engineer"的人也喜欢的电子书 · · · · · ·
喜欢读"The Effective Engineer"的人也喜欢 · · · · · ·
The Effective Engineer的书评 · · · · · · ( 全部 11 条 )
希望新的一年里,做一个有效率的工程师
How to be an effective engineer (全书摘要)
这篇书评可能有关键情节透露
Effective engineers focus on value and impact—they know how to choose which results to deliver. Part 1: Adopt the Right Mindsets 1. Focus on High-Leverage Activities Leverage = Impact produced/Time invested. It's the return on investment (ROI) for the effo... (展开)对职场新人挺有帮助的
这篇书评可能有关键情节透露
我看的第一本此类书籍, 花了10个小时, 看的比较仔细, 也很有收获. 作者主要说了两方面: 心态想法和实际行动. 心态想法方面, 第一个为时间是有限的,要做high-Leverage的事情.这点是我比较欠缺的,其实2017年开始我逐渐有些认识到这个问题.当面对一个问题时,认为自己可以完成,... (展开)> 更多书评 11篇
论坛 · · · · · ·
在这本书的论坛里发言这本书的其他版本 · · · · · · ( 全部2 )
-
电子工业出版社 (2022)8.5分 135人读过
以下书单推荐 · · · · · · ( 全部 )
- 6.大脑学习法--如何思维 (葡萄)
- Books for professional developer (figure9)
- To be a better developer (Nova)
- 后端程序员成长阅读书目 (YigWoo)
- book2do (wishUhere)
谁读这本书? · · · · · ·
二手市场
· · · · · ·
- 在豆瓣转让 有1173人想读,手里有一本闲着?
订阅关于The Effective Engineer的评论:
feed: rss 2.0
0 有用 薇莱 2017-11-07 13:43:17
真的戳了很多痛点。
1 有用 Breeze 2019-09-05 21:28:24
【藏书阁打卡】作者首先从何为高效工作以及为什么要高效工作开始谈起,提出High-leverage的概念,即单位时间内产出的价值最大化。然后从迭代速度、目标衡量、A/B 测试、项目时间评估等几个方面探讨了提高工作效率的措施和方法。要是刚开始工作的时候,能够看到这本书的话,工作习惯和工作方法会比现在有很大的改善吧。此外,作者从团队的角度,谈了如何在代码质量和迭代速度之间作出权衡,以及如何进行自动化流程... 【藏书阁打卡】作者首先从何为高效工作以及为什么要高效工作开始谈起,提出High-leverage的概念,即单位时间内产出的价值最大化。然后从迭代速度、目标衡量、A/B 测试、项目时间评估等几个方面探讨了提高工作效率的措施和方法。要是刚开始工作的时候,能够看到这本书的话,工作习惯和工作方法会比现在有很大的改善吧。此外,作者从团队的角度,谈了如何在代码质量和迭代速度之间作出权衡,以及如何进行自动化流程,如何不断提高团队的整体实力。作者的这些经验还是挺有参考价值的。 (展开)
0 有用 memorykeeper 2019-12-27 18:57:15
时间才是你最有限的资源!
0 有用 豆友1094556 2018-08-18 10:28:06
在码农鸡汤算是很好的一本了。
0 有用 蓝石头 2017-11-11 21:01:51
对我感觉像老生常谈了,todo list,move fast,善用编辑器等等
0 有用 开觉 2024-01-12 19:10:51 美国
翻了一遍,有两点印象深刻,一个是对leverage的定义,另一个是用最简单最基本的方法测试project ideas。这个也是我最近正在尝试的。Priortization的重要性怎么强调都不为过。一开始对前言有偏见,认真读了感觉句句深得我心。刚开始工作的时候看到周围的人title都非常高多少有点惶恐,呆到现在发现title高的效果于我而言只有被他们指挥搞一些有的没的。上面一串领导,加别的组的若干找... 翻了一遍,有两点印象深刻,一个是对leverage的定义,另一个是用最简单最基本的方法测试project ideas。这个也是我最近正在尝试的。Priortization的重要性怎么强调都不为过。一开始对前言有偏见,认真读了感觉句句深得我心。刚开始工作的时候看到周围的人title都非常高多少有点惶恐,呆到现在发现title高的效果于我而言只有被他们指挥搞一些有的没的。上面一串领导,加别的组的若干找存在感的领导,而真正干活只有一两个最底层的员工。越是没有价值,越是要体现价值,那我们到底有什么可惶恐的呢 (展开)
0 有用 Roy 2024-01-05 00:18:41 加拿大
看了所有的 key takeaways 和样章。对于已经工作了几年的 developer 感觉没啥用。。
0 有用 容安 2024-01-04 04:00:49 芬兰
很工具很有用的一本书,但真要学会里面的东西,需要更多时间的沉淀和有意识的练习。
0 有用 doubin 2023-10-17 23:47:36 北京
追求高杆杠,学习也有复利,越早越好。if then对抗拖延症,不要项目中途开始冲刺。终于找到适合英文电子书阅读的方式了。
0 有用 飞羽醉月 2023-09-12 02:19:42 美国
建议先看目录,如果目录里的话题你不太熟悉,那值得一看。又或者可以去看看对这些主题探讨更深入更原创的书籍,比如Mindset、人月神话、高效能人士的七个习惯