APPropriate Behaviour

Introduction

1. What’s this book about?
2. Why are you writing it?
3. These are the ramblings of one person
4. Who should read it?
5. Something you said was rubbish
6. About the Author
7. Acknowledgements

Tools that support software development

1. Version control / Source code management
2. Continuous Integration and Deployment
3. Build Management
4. Bug and work tracking
5. Integrated Development Environment
6. Static Analysis
7. Code Generation

Coding Practices

1. Test-Driven Development
2. Domain-Driven Design
3. Behaviour-Driven Development
4. xDD
5. Design by Contract
6. Development by Specification
7. Pair programming
8. Code Reviews
9. Programming paradigms and their applicability

Testing

1. A Philosophy of Testing
2. Black and White boxes
3. Test case design
4. Automate all the things
5. Getting someone else in
6. Other benefits of testing

Architecture

1. Non-functional requirements are essential
2. Defer when appropriate; commit when necessary
3. Justify your decisions
4. When to fix and when to replace
5. Know when to nitpick, and when to leave it
6. Support, don’t control

Documentation

1. Documentation is more useful than you might think
2. While there is value in comprehensive documentation
3. The up-to-dateness problem
4. Automatically Generated Documentation
5. Analysis Paralysis
6. How to Document
7. Summary

Requirements Engineering

1. Study People
2. You shouldn’t necessarily build what the client asks for
3. Avoid asking what you want to hear
4. Understand the problem domain
5. Uncover tacit requirements
6. You shouldn’t build what your client wants
7. Human factors in software systems
8. Prioritising Requirements
9. Is it really “engineering”?

Learning

1. Do As Much As You Can
2. Don’t Stick to Your Own Discipline
3. Put it into Practice
4. Collaborate and Share what you Learn
5. Opportunities to Learn
6. Rediscovering lost knowledge
7. The teaching of software creation
8. Reflective Learning

Critical Analysis

1. Criticism is often uncritical
2. How to form an argument
3. Forms of fallacy
4. Further Reading on Arguments
5. Debates and Programmers
6. Software as Essays

Business

1. Evaluate risks dispassionately
2. Find out what you need to know, and how you can know it
3. What you discover may not be to your liking
4. How to interview a programmer
5. Be transparent and honest with your business partners
6. Choose Appropriate Technology
7. Manipulation and Inspiration
8. You don’t need to be a founder to be a programmer

Teamwork

1. Focus vs Interruption
2. Working environment
3. Prioritising Work
4. Tell experts what needs to be done
5. Working with junior programmers
6. Working with managers
7. Patterns of Software Project Management
8. Negotiation
9. Empathy
10. Shared language and shiny buzzwords

Ethics

1. Examples of ethical codes
2. Application of the ethical code
3. Ethical Ambiguities
4. Respecting Privacy
5. Epilogue

Philosophy

1. Software as a pursuit
2. An economic philosophy of software
3. A management philosophy of software
4. A social philosophy of software
5. A pedagogic philosophy of software
6. What does it mean to be “good” at making software?

Conclusion