139 posts tagged with "Misc"

PoC, PoT, Prototype, MVP, Pilot - what do they all mean? What is the difference between them, and when should you use them?

Today, we are going to take a look at a technical Cloud Product Development lifecycle - in my eyes, understanding these terminologies is key to determining:

• What kind of resources (i.e., both technological and human) do you need to dedicate to a product?
• Where should you align lifecycle management with your application or service?
• How likely is it that the the product makes a good market fit or solves an issue?
• Keep your product lean to avoid wasting the wrong resources at the wrong time
• Shift to a product-based mindset
• Focus on innovation and early feedback loops

And, of course - what to expect when people start using these words, often thrown together in a conversation and sometimes even put in writing in Statement of Works and Requests for Proposals.

I had the privilege to be able to read and review the ‘Kubernetes - An Enterprise Guide’ book by Marc Boorshtein (Author), Scott Surovich (Author). Packt Publishing publishes the book and is available on Amazon.

This was the third edition of the book, but I feel there was no need to read the previous editions to understand the content of this book. Being the third edition also means that any mistakes or learnings from the past two editions have been considered.

I've written, about GitHub Codespaces before, in the article Coding on the Cloud - Getting Started with GitHub Codespaces, this article builds on it by supplying a Codespace setup for Infrastructure as Code (IaC) coding, including Bicep and Terraform, and Linting.

Cloud Design patterns help build reliable, scalable, secure applications in the cloud.

Today, we will cover common patterns, their use cases, and considerations.

The patterns we will cover today are only a small set of common patterns documented in the Azure Architecture Center.

Troubleshooting Azure Open AI and API calls to OpenAI can be challenging, especially when you may not know where to start!

The idea of this article is to give you not only a place to start with some common scenarios you may run into but also a way of thinking - to help you troubleshoot. This is not a technical 'get-your-hands dirty, delve into those logs' type article.

I am a big fan of the KT, or Kepner-Tregoe problem analysis methodology, and I have used it in many scenarios throughout my career to help discover and test the root cause of various problems. So, we will use the base of this problem analysis methodology to help us troubleshoot the scenarios we will discuss in this article.