Jump to ratings and reviews
Rate this book

Debugging the Development Process: Practical Strategies for Staying Focused, Hitting Ship Dates, and Building Solid Teams

Rate this book
In Debugging the Development Process, Maguire describes the sometimes controversial but always effective practices that enabled his software teams at Microsoft to develop high-quality software - on schedule. With the refreshing candor reviewers admired in Writing Solid Code, Maguire talks about what did and what didn't work at Microsoft and tells you how to energize software teams to work effectively - and to enjoy their work; why you might want to kick your star programmer off your team; how to avoid corporate snares and overblown corporate processes; which tiny changes produce major results; how to deliver on schedule and without overwork; how to pull twice the value out of everything you do; how to get your team going on a creative roll; and how to raise the average programmer level at your company.

183 pages, Paperback

First published August 1, 1994

Loading...
Loading...

About the author

Steve Maguire

21 books14 followers

Ratings & Reviews

What do you think?
Rate this book

Friends & Following

Create a free account to discover what your friends think of this book!

Community Reviews

5 stars
66 (39%)
4 stars
72 (42%)
3 stars
26 (15%)
2 stars
5 (2%)
1 star
0 (0%)
Displaying 1 of 1 review
Profile Image for LY.
8 reviews4 followers
December 8, 2021
雖然大部分的觀點現在已經有很多自我成長書會提,例如保留大塊專注時間,只拿早上剛開始的時間、中午的午休時間、下班前來處理雜事、回email或是開重要的會議,請教別人時要先提出自己的觀點而不是當伸手牌,但這本書還是有些值得參考的地方,包括
• 學習要專注於能夠帶著走的能力/專案
• 學習能夠立即應用的技能(個人成長+可以對公司產生貢獻)
• 多寫能造福整個產品的程式,而非用一次就丟了或是只能給特定小組用的
• 有做得不好的地方就制定目標,立刻改進(例如採取自動除錯方式),不要等到年度考核才在挑毛病
• 有問題發生時,問「未來如何避免」,而不是「為什麼做錯」,這兩個問題獲得的答案截然不同
• 發現問題就立刻記錄,誰幫你的、學到什麼、未來如何改善
• 不是什麼事情都非得要開會才能解決,有時候簡短的訊息(text message)就可以達到效果
• 會議一定要得到結論,不然以後也不會有「比較不忙,能夠好好思考問題」的時候
• 合理壓力與時限,而不是「達不到的 deadline」,增長工時只會讓員工開始在公司處理他們的雜事(因為回家也沒時間)
This entire review has been hidden because of spoilers.
Displaying 1 of 1 review