Showing posts from May, 2019

RIF Notes #54

"You know, I’ve been in the software development business for more than 40 years now, and there is one thing that I know for a solid fact: Nobody knows how to build software. Yes, sometimes it gets built, but it’s a random, unrepeatable event. A lucky accident." - Alan Cooper QA in Production What do you mean by “Event-Driven”? Events, Data Points, and Messages - Choosing the right Azure messaging service for your data Waste (and production efficiency) Is High Quality Software Worth the Cost? – “High internal quality reduces the cost of future features, meaning that putting the time into writing good code actually reduces cost” WHEN TECH KNOWS YOU BETTER THAN YOU KNOW YOURSELF

RIF Notes #53

"’When will you be done’ When it comes to Agile dev, the best metaphor is life. You're not done until you're dead. Up till then, it's an ongoing and dynamic process where you learn things and adapt based on what you learn. Project thinking is not useful; think product." - Allen Holub The Fallacies of Enterprise Computing 11 Fallacies of Distributed Computing Introducing .NET 5 .NET Core is the Future of .NET End-to-End Encryption Isn’t as Safe as You Think – “The WhatsApp hack shows how supposedly secure messaging apps have a basic vulnerability” Amazon Workers Are Listening to What You Tell Alexa How to Track Your Kids (and Other People's Kids) With the TicTocTrack Watch

RIF Notes #52

“Most corporate planning is like a ritual rain dance. It has no effect on the weather, but those who engage in it think it does. Much of the advice and instruction is directed at improving the dancing, not the weather” - Russel L. Ackoff GDPR in the USA – “GDPR enforcement began in May of 2018, but if you are doing business in the US, you may not think it applies to you. Grant Fritchey explains why you might be wrong about that and why you need to act now” Domain-Oriented Observability – “ Observability in our software systems has always been valuable and has become even more so in this era of cloud and microservices. However, the observability we add to our systems tends to be rather low level and technical in nature, and too often it seems to require littering our codebase with crufty, verbose calls to various logging, instrumentation, and analytics frameworks. This article describes a pattern that cleans up this mess and allows us to add business-relevant observability in a clean,