Thread

1. digitallogic · 1790109636 · focus · HN ↗

   > You have enough budget for only the first floor, but you have a big family, and you know you’ll want a second one in a couple of years. > Adding the infrastructure to support a 2nd floor is MUCH cheaper right now than it will be when you actually want that 2nd floor.

   The problem with this thinking is it requires certainty about the future. It's much cheaper right now IF AND ONLY IF you end up needing the thing. If you don't need it, then you've threw time and money down the drain.

   Where I think this analogy weakens is you probably have far more certainty of whether or not you want a big family then you do on whether or not a new product line will see major adoption.

   1. mattmanser · 1790110271 · focus · HN ↗

      I am known for analogies. I use them all the time to try and explain things to less technical people.

      Sometimes it's building a house, sometimes it's writing a book, sometimes it's the difference between a Ford and a kit car, sometimes it's how you build a bridge.

      None of them stand up to full scrutiny. You can pick every single one apart.

      That's not the point of analogies. The point is to explain just one of the many aspects of software engineering in a more understandable format to the listener. Software engineering is nothing like building a physical thing. But some of the many, many problems and complexity you hit have physical product analogies.

      Don't stretch analogies too far as they all pop.

Unofficial Hacker News client; not affiliated with Y Combinator.