Abstract
I don't know whether you'll have picked this up from the foregoing chapters, but I'm a pessimist. A cynic. A glass-half-empty kind of a guy. I've cultivated this outlook very deliberately over the last few years, because I find it to be extremely useful, professionally speaking.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
See “The Estimation Problem” in Chapter 2.
- 2.
See “The sad truth about software projects” in Chapter 2.
- 3.
Retrospectives are discussed in Chapter 3.
- 4.
To the dismay and consternation of my Irish relatives.
- 5.
- 6.
- 7.
See Chapter 3.
- 8.
Flight booking websites know this, and will spend lots of money tweaking the look of, for example, the button that you click to see details of a particular flight, because even a fractional conversion rate bump can have a huge effect on their bottom line.
- 9.
In my defense, I said most of these things after the first failed launch, but was overruled.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2017 Patrick Gleeson
About this chapter
Cite this chapter
Gleeson, P. (2017). When It All Goes Wrong. In: Working with Coders. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2701-5_10
Download citation
DOI: https://doi.org/10.1007/978-1-4842-2701-5_10
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-2700-8
Online ISBN: 978-1-4842-2701-5
eBook Packages: Business and ManagementApress Access BooksBusiness and Management (R0)