What I've Learned From Failure

What I've Learned From Failure

Reg “raganwald” Braithwaite
Buy on Leanpub

Table of Contents

What I've Learned From Failure

  • Preface
    • copyright notice
  • About The Author
    • contact
  • What I’ve Learned From Failure
    • Why does failure matter?
    • The four most important causes of failure
    • People
    • Action
    • Details
    • The Schedule
    • Software
    • Power
    • History
    • Finishing
  • The Not So Big Software Design
    • Lemons
    • Building Better, Not Buzzwordier
    • Where is the client?
    • Better Software Architecture
  • Which Theory Fits the Evidence?
    • why do theory p and theory d matter?
    • belief drives behaviour
    • so which theory fits the evidence?
    • d is for “d’oh! we should have gone with p!”
  • Interlude: The Programmer’s Dilemma
  • Project Management acts like a Marketplace for Information
    • what kind of information sells?
  • Bricks
    • software is not made of bricks
    • assumption: it’s all about moving bricks
    • software development is difficult to parallelize
    • software is transfinite
    • building software without treating it like a pile of bricks
  • Trial-and-error with a feedback cycle
    • trial and error
    • feedback
    • productization
    • the scarce resource
  • Software’s Receding Hairline
    • receding hairlines
    • the tyranny of the urgent
  • Interlude: The Mouse Trap
    • The New Guy
    • Excel, VBA, XML, XSLT, Java!
    • Epilogue
  • Duck Programming
    • prelude: the project
    • what is duck programming?
    • why duck tastes so good
    • dangerous but manageable
    • how to manage duck programming
    • summary
  • I Can’t Find Good Salespeople
    • Why I Can’t Find Good Salespeople
    • Solving Sarah’s Problem
What I've Learned From Failure/overview

What I've Learned From Failure

course_overview

count_chapters
begin_reading
download
p_implied_book_part_name

What I've Learned From Failure13 chapters

Begin ›
  1. Preface

  2. About The Author

  3. What I’ve Learned From Failure

  4. The Not So Big Software Design

  5. Which Theory Fits the Evidence?

  6. Interlude: The Programmer’s Dilemma

  7. Project Management acts like a Marketplace for Information

  8. Bricks

  9. Trial-and-error with a feedback cycle

  10. Software’s Receding Hairline

  11. Interlude: The Mouse Trap

  12. Duck Programming

  13. I Can’t Find Good Salespeople