How to be a Programmer
  • How to be a Programmer: Community Version
  • LANGS
  • How to be a Programmer: Community Version
    • 2. Intermediate
      • Personal-Skills
        • How to analyze data
        • How to Balance Brevity and Abstraction
        • Heavy Tools
        • How to Learn New Skills
        • How to Stay Motivated
        • How to be Widely Trusted
        • How to Do Integration Testing
        • Communication Languages
        • How to Tradeoff Time vs. Space
        • Learn to Type
        • How to Stress Test
      • Judgment
        • How to Tradeoff Quality Against Development Time
        • How to Manage Software System Dependence
        • How to Know When to Apply Fancy Computer Science
        • How to Make a Buy vs. Build Decision
        • How to Talk to Non-Engineers
        • How to Grow Professionally
        • How to Decide if Software is Too Immature
        • How to Evaluate Interviewees
      • Team-Skills
        • How to Manage Third-Party Software Risks
        • How to Communicate the Right Amount
        • How to Manage Development Time
        • How to Disagree Honestly and Get Away with It
        • How to Manage Consultants
    • 1. Beginner
      • Team-Skills
        • Take Breaks when Stumped
        • Why Estimation is Important
        • How to Use Source Code Control
        • How to Deal with Difficult People
        • How to Document Wisely
        • How to Utilize People as Information Sources
        • How to Find Out Information
        • How to Unit Test
        • How to Work with Poor Code
        • How to Recognize When to Go Home
        • How to Estimate Programming Time
      • Personal-Skills
        • How to Manage Memory
        • How to Deal with I/O Expense
        • Learn to Debug
        • How to Debug by Splitting the Problem Space
        • How to Understand Performance Problems
        • How to Deal with Intermittent Bugs
        • How to Debug Using a Log
        • How to Fix Performance Problems
        • How to Remove an Error
        • How to Conduct Experiments
        • How to Learn Design Skills
        • How to Optimize Loops
    • Contributions
    • 3. Advanced
      • Compromising-Wisely
        • How to Fight Schedule Pressure
        • How to Get a Promotion
        • How to Understand the User
      • Serving-Your-Team
        • How to Grow a System
        • How to Deal with Organizational Chaos
        • How to Deal with Managerial Myths
        • How to Communicate Well
        • How to Tell People Things They Don't Want to Hear
        • How to Handle Boring Tasks
        • How to Get the Most From Your Team-mates
        • How to Divide Problems Up
        • How to Tell People Things They Don't Want to Hear
        • How to Gather Support for a Project
        • How to Choose What to Work On
        • How to Develop Talent
      • Technical-Judgment
        • Choosing Languages
        • How to Tell the Hard From the Impossible
        • How to Utilize Embedded Languages
    • Appendix A - Bibliography/Websiteography
    • Summary
    • Creative Commons Attribution Share-Alike
    • Appendix B - History
    • Glossary
  • How to be a Programmer: Community Version
    • 1. Beginner
      • Personal-Skills
        • How to Learn Design Skills
        • How to Deal with I/O Expense
        • How to Debug by Splitting the Problem Space
        • How to Manage Memory
        • Learn to Debug
        • How to Understand Performance Problems
        • How to Fix Performance Problems
        • How to Deal with Intermittent Bugs
        • How to Debug Using a Log
        • How to Remove an Error
        • How to Conduct Experiments
        • How to Optimize Loops
      • Team-Skills
        • How to Deal with Difficult People
        • How to Estimate Programming Time
        • Take Breaks when Stumped
        • How to Use Source Code Control
        • How to Document Wisely
        • How to Find Out Information
        • How to Utilize People as Information Sources
        • How to Unit Test
        • Why Estimation is Important
        • How to Work with Poor Code
        • How to Recognize When to Go Home
    • 2. Intermediate
      • Judgment
        • How to Tradeoff Quality Against Development Time
        • How to Manage Software System Dependence
        • How to Know When to Apply Fancy Computer Science
        • How to Talk to Non-Engineers
        • How to Grow Professionally
        • How to Make a Buy vs. Build Decision
        • How to Evaluate Interviewees
        • How to Decide if Software is Too Immature
      • Team-Skills
        • How to Communicate the Right Amount
        • How to Manage Third-Party Software Risks
        • How to Disagree Honestly and Get Away with It
        • How to Manage Consultants
        • How to Manage Development Time
      • Personal-Skills
        • How to Balance Brevity and Abstraction
        • Heavy Tools
        • How to Learn New Skills
        • How to Stay Motivated
        • How to Do Integration Testing
        • Communication Languages
        • How to be Widely Trusted
        • How to Tradeoff Time vs. Space
        • Learn to Type
        • How to Stress Test
        • How to analyze data
    • 3. Advanced
      • Serving-Your-Team
        • How to Deal with Organizational Chaos
        • How to Grow a System
        • How to Deal with Managerial Myths
        • How to Communicate Well
        • How to Get the Most From Your Team-mates
        • How to Divide Problems Up
        • How to Handle Boring Tasks
        • How to Gather Support for a Project
        • How to Choose What to Work On
        • How to Develop Talent
        • How to Tell People Things They Don't Want to Hear
      • Technical-Judgment
        • How to Utilize Embedded Languages
        • How to Tell the Hard From the Impossible
        • Choosing Languages
      • Compromising-Wisely
        • How to Get a Promotion
        • How to Fight Schedule Pressure
        • How to Understand the User
    • Glossary
    • Appendix A - Bibliography/Websiteography
    • Summary
    • Creative Commons Attribution Share-Alike
    • Appendix B - History
    • Contributions
  • How to be a Programmer 中文版
    • 3. 高级
      • Serving-Your-Team
        • 如何处理管理神话
        • 如何告诉人们他们不想听的东西
        • 如何有效地沟通
        • 如何发展一个系统
        • 如何让你队友的价值最大化
        • 如何划分问题
        • 如何为工程获取支持
        • 如何选择工作的内容
        • 如何发展才能
        • 如何处理无聊的任务
        • 如何处理组织混乱
      • Technical-Judgment
        • 如何从不可能中找到困难的部分
        • 如何使用嵌入型语言
        • 选择语言
      • Compromising-Wisely
        • 如何获得晋升
        • 如何与时间压力做斗争
        • 如何理解用户
    • 2. 进阶
      • Personal-Skills
        • 如何进行压力测试
        • 重型工具
        • 如何学习新技能
        • 如何保持活力
        • 如何做集成测试
        • 交流语言
        • 如何在时间与空间权衡
        • 如何在简洁与抽象间平衡
        • 学会打字
        • 如何被广泛信任
        • 如何分析数据
      • Judgment
        • 如何管理软件系统依赖
        • 如何判断软件是否太不成熟了
        • 如何决定什么时候使用奇妙的计算机科学
        • 如何与非工程师交谈
        • 如何专业地成长
        • 如何评估面试者
        • 如何做购买还是构建的决定
        • 如何在开发质量与开发时间权衡
      • Team-Skills
        • 如何适量交流
        • 如何直言异议以及如何避免
        • 如何管理咨询师
        • 如何管理第三方软件危机
        • 如何管理开发时间
    • How to be a Programmer 中文版
    • 1. 入门
      • Personal-Skills
        • 如何通过分割问题 Debug
        • 如何进行实验
        • 如何学习设计技能
        • 如何管理内存
        • 如何修复性能问题
        • 学会 Debug
        • 如何理解性能问题
        • 如何优化循环
        • 如何处理偶现的 Bugs
        • 如何使用日志调试
        • 如何处理I/O代价
        • 如何移除一个错误
      • Team-Skills
        • 如何在糟糕的代码上工作
        • 如何识别下班时间
        • 如何发现信息
        • 如何评估编程时间
        • 如何使用源代码控制
        • 毫无头绪？，休息一下
        • 如何睿智地写文档
        • 如何把人们作为信息源
        • 如何进行单元测试
        • 为什么评估很重要
        • 如何与不好相处的人相处
    • Creative Commons Attribution Share-Alike
    • 附录 B - 历史
    • 附录 A - 书目/网站目录
    • 词汇表
    • Contributions
Powered by GitBook
On this page

Was this helpful?

Team-Skills

Previous如何移除一个错误Next如何在糟糕的代码上工作

Last updated 4 years ago

如何在糟糕的代码上工作
如何识别下班时间
如何发现信息
如何评估编程时间
如何使用源代码控制
毫无头绪？，休息一下
如何睿智地写文档
如何把人们作为信息源
如何进行单元测试
为什么评估很重要
如何与不好相处的人相处