Index
A
- action / Action
B
- bad ideas
- recognizing / Recognizing Bad Ideas
- barriers
- bug
- defining / Hardware
- compound complexity / Compounding Complexity
- clarifying / Clarify the Bug, Look at the System, Find the Real Cause, Four Steps
- Bugzilla
- URL / Retaining Contributors
- limitations, fixing / Why is it that this worked?
C
- codebase
- issues, solving / Make it Never Come Back – An Example
- code complexity
- handling, in software company / Step 3 – Bug Reports, Step 4 – Prioritization, Step 5 – Assignment, Step 6 – Planning
- complexity
- accepting / So What Should You Do?
- about / The Solution
- credibility / Credibility and Solving Problems
- changing / The Blocker
- productivity, improving / Moving Towards the Fundamental Problem
- compound complexity / Compounding Complexity
- contributors
- retaining, ways / Retaining Contributors, 1. Don't freeze the trunk for long periods, 2. Turnover is inevitable, 3. Respond to contributions immediately, 4. Be extremely kind and visibly appreciative, 5. Avoid personal negativity
- obtaining / Getting People Interested, Be written in a popular programming language
- counter-examples / Are there Counter-Examples to this Rule?
- Cycle of Observation
- speed / Development Processes and Productivity
- completeness / Development Processes and Productivity
- accuracy / Development Processes and Productivity
D
- design
- beginning / Starting the Right Way
- determinism
- about / Determinism
E
- Eiffel
- end to end testing
- about / End to End Testing
- excellent software
- users intention, carrying out / 1. Does exactly what the user told it to do
- behaving, as user expects / 2. Behaves exactly like the user expects it to behave
- user friendly / 3. Does not block the user from communicating their intention
- user intention, communicating / 3. Does not block the user from communicating their intention
- complexity, adding / Excellence is senior to (but is not in conflict with) code simplicity
F
- fakes
- about / Fakes
I
- information
- providing, to developers / Trust and Information
- instant gratification
- avoiding / Solving for the long term
- integration testing
- about / Integration Testing
- ISAR
- in single line of code / ISAR in a Single Line of Code
K
- keys, to fast programming
- understanding / Understanding
- drawing / Drawing
- starting / Starting
- step, skipping / Skipping a Step
- physical problems / Physical Problems
- distractions / Distractions
- self-doubt / Self-Doubt
- false ideas / False Ideas
- caveat, for writing code / Caveat
M
- Mozilla
O
- ODA cycle
- about / The First ODA
P
- power of no
- bad ideas, recognizing / Recognizing Bad Ideas
- about / Having No Better Idea
- clarifications / Clarification: Acceptance and Politeness
- privacy
- of space / Privacy of Space
- of information / Privacy of Information
- about / A Summary of Privacy
- programmer / If You're Going To Do It Then Do it Well
- programmers
- reasons, for creating complexity / What to Study
- programming
- productivity, defining / The Definition of "Productivity"
- lines of code / Why Not "Lines of Code?"
- valid metric, determining / Determining a Valid Metric
- product is code / What About When Your Product Is Code?
- developer productivity, working / What about People Who Work on Developer Productivity?
- software engineers / What about People Who Work on Developer Productivity?
- developer productivity, measuring / Conclusion
R
- rabbit hole / Down the Rabbit Hole
- real systems
- testing / Reality
- refactoring
- about / Being Effective
- determining / Refactoring To Clarity
- results / Results
- right way / The Right Way
S
- software design
- software systems
- about / Software is about People
- example / An Example of Kindness
- code, reviewing / An Example of Kindness
- implementing / Be Kind, and Make Better Software
- structure / Structure
T
- TDD cycle
- about / Examples of ODA
- development processes / Development Processes and Productivity
- productivity / Development Processes and Productivity
- technology
- advance of technology, importance / Is the Advance of Technology "Good"?
- testing
- boundaries / Test Boundaries
- assumptions / Test Assumptions, Test Design
- end to end testing / End to End Testing
- integration testing / Integration Testing
- unit testing / Unit Testing
- reality / Reality
- fakes / Fakes
- determinism / Determinism
- speed / Speed
- coverage / Coverage
- conclusion / Conclusion – The Overall Goal of Testing
- trust
- providing, to developers / Trust and Information
- Two is Too Many rule
- refactoring, scenario / Refactoring
U
- unit testing
- about / Unit Testing
- users
- issues, arising from / Problems Come from Users
W
- wrong way
- about / The Wrong Way
- analysis / Analysis of The Wrong Way
- group, bringing / Bringing It To a Group