Sponsor: Using RabbitMQ or Azure Service Bus in your .NET systems? Well, you could just use their SDKs and roll your own serialization, routing, outbox, retries, and telemetry. I mean, seriously, how hard could it be?
While I was attending Agile & Beyond last year, David J. Anderson did a great keynote on “stop doing agile, start thinking agility”. In that keynote he said something that has stuck with me: Making progress through imperfect information. There seems to be a stigma with refactoring. It might not be refactoring, but getting it right the first time mentality. We want to create the right solution and fear making the wrong decision because we don’t have all the information we think we need. Make progress with imperfect information and refactor later when more is known or wait for better information? I believe the best option is to deliver working software earlier. This now leads into Continuous Delivery… maybe a post in the future. Remember, you can only make a decision based off of the information you have at that moment. Is it possible that you will see a flaw in your decision and have to refactor? Of course, but embrace change!