Status Updates From The Unicorn Project: A Nove...

Technology needs to be embedded in the business, not external to it or merely “aligned with it”.

Infrastructure is messy work, almost the opposite of the pure functional programming she loves—in infrastructure, almost everything you do has a side-effect that mutates the state of something in the environment, making it difficult to isolate and test changes, as well as diagnose problems when things go wrong.

Software is like a city, constantly undergoing change, needing renovations and repair.

A healthy software system is one that you can change at the speed you need, where people can contribute easily, without jumping through hoops. This is how you make a project that’s fun and worthwhile contributing to, and where you often find the most vibrant communities.

Creating software should be a collaborative and conversational endeavor—individuals need to interact with each other to create new knowledge and value for the customer.

Punishing failure and “shooting the messenger” only cause people to hide their mistakes, and eventually, all desire to innovate is completely extinguished.

Honestly the writing is mediocre at best so far, and it really doesn’t feel like it was written by someone in the industry. Lots of buzzwords thrown around on top of a very cringe main character that I struggle to imagine as anything resembling a real person