Becoming a curious scientist
Conventional wisdom tells us that we have to design big and plan for worst case - that’s how we prepare for the unexpected. When we release to production, that’s the first time our users will see it and that’s ok....
A collection of 91 posts
Conventional wisdom tells us that we have to design big and plan for worst case - that’s how we prepare for the unexpected. When we release to production, that’s the first time our users will see it and that’s ok....
So I found out about greenfield project being developed on Kubernetes. It was a sizable project with microservices and the likes. It has been in development for a year.
The other day I spoke to some folks and they were wondering if they should use Service Fabric - Microsoft’s orchestrator. I get it. It powers a sizable chunk of Azure. Microsoft has been successful with it.
I’ve recently been listening a lot of audio books from Seth Godin. He talks about when and why to push through hard times, how to be a linchpin, and what makes a great marketing.
Deploying Azure Resource Manager (ARM) templates from Azure DevOps is very powerful. It encourages developers and operators to maintain a declarative file describing the infrastructure on Azure. Also helps prevent pesky environment drifts because of someone clicking from the portal...