I’m wondering why is “Zero to One” such a widely used term the | Not boring, and a bit of a condescending prick
I’m wondering why is “Zero to One” such a widely used term these days, and yet its counterpart, one to zero, is hardly discussed.
I want zero extra actions to have to be performed so that:
• the tests are run,
• the code deploys,
• the schema is respected,
• the paycheck is sent,
• the event is in my calendar, with the proper link to join the meeting,
• access permissions are granted upon being asked for, and
• non-engineers are not messing with well-functioning engineering processes.
Each of the above billet points by itself deserves a good book.