Development Experience(s)

Transitioning to a new role in my organization, I'm reading a whole lot of books from categories I hadn't been previously. Here are my thoughts on High Output Management (linked below). I was introduced to the book from a YouTube video (recommended to me by a colleague), basically saying that this book contains the source ideas of many other works. My colleague also ensured me that it was an easy read. Filled with applicable, hands-on advice, the book starts off by teaching you about The Basics of Production: Delivering a Breakfast (or a Colleague Graduate, or a Compiler, or a Convicted Criminal...) , introducing concepts such as limiting steps, optimizations (and their constraint on flexibility), using indicators, trends/forecasts, and so much more. Have you heard of OKRs before ? The book discusses paired indicators early, stating that "a measurement - any measurement - is better than none" and goes on to say "a genuinely effective indicator will cover the out

Here are my highlights from Succeeding with OKRs in Agile (linked below). Once set, OKRs should be the focus of all work. Whether OKRs are met or not is almost secondary. OKRs are a hypothesis for the coming quarter, a best effort guess at what will advance purpose. At the end of the quarter, review and adapt - what could be more agile? ARPANET became the internet in 1981, the same year IBM launched the PC. Managers must look at outcomes. Enhance independence even at the cost of redundancy and duplication. Goals bring focus, and focus is powerful. But focus also means blinkered vision, which carries dangers - but if we aren't blinkered we may be overwhelmed. Software engineers might recognize this as abstraction. Outcome is described in terms that speak to the customers. Achieving a key result should deliver some benefit - some value - to someone. A team may have a long-term plan or a roadmap, a mission oar vision statement, a business plan or statement of the market opportunity, m

I recently got my hands on a pre-release copy of Blazor WebAssembly by Example (linked below) by Toi B. Wright. As I've previously been quite biased towards Blazor Server, I appreciated reading about the merits of BWA, such as using it as a conduit to Progressive Web Applications and using PWAs as a means to publish your web application to app stores, like Starbucks, Uber and Spotify have done . The book does not go into how to publish your application, but teaches you about the PWA manifest and service workers as it discusses JavaScript interoperability. Another thing I appreciated about the book, was the way it set expectations in its preface. Toi outlines what her book covers, chapter by chapter, giving you a sense of what you're about to learn.  Speaking of the preface, however; in the section Who this book is for , it said something I didn't recognize throughout the book: This book is for experienced web developers who are tired of constantly learning the latest new J