Pongsak Khamdee

Business Outcomes Lean Canvas: The Definitive Guide to Organizational Transformation

Pongsak Khamdee — Fri, 29 May 2026 08:58:25 +0000

Business Outcomes Lean Canvas: The Definitive Guide to Organizational Transformation

Most digital transformation initiatives fail — not because of bad technology choices, but because nobody took the time to clearly articulate why the change is needed, what success looks like, and how the pieces connect. The Business Outcomes Lean Canvas is a structured one-page framework that forces a team to answer all of those questions before a single line of code is written or a single vendor is selected.

This guide is the exhaustive reference — from the theory behind the canvas to a workshop you can run next week.

Nutanix Cloud Platform Overview

Pongsak Khamdee — Fri, 29 May 2026 08:58:25 +0000

Nutanix Cloud Platform Overview

Most enterprises still run their workloads on a tangle of separate systems — one vendor for compute, another for storage, another for networking, yet another for virtualization. Managing all of that is expensive, slow, and fragile. Nutanix was founded on one radical idea: collapse all of those layers into a single, software-defined platform that runs on commodity hardware and is as simple to operate as a public cloud.

In 2026, Nutanix Cloud Platform (NCP) has grown from that original idea into a comprehensive stack spanning private cloud infrastructure, multi-cloud management, enterprise Kubernetes, database-as-a-service, AI infrastructure, and unified storage — all managed through a single pane of glass.

What Is DevOps? The Complete Guide

Pongsak Khamdee — Fri, 29 May 2026 08:58:25 +0000

What Is DevOps? The Complete Guide

Ask ten engineers what DevOps is and you'll get ten different answers.

"It's CI/CD." "It's automation." "It's when developers do operations." "It's a culture." "It's a job title." "It's a toolchain." "It's a movement."

They're all partially right. And because DevOps touches culture, process, and technology simultaneously, it resists simple definition.

Git Workflow for Release Management: Branches vs Tags

Pongsak Khamdee — Fri, 29 May 2026 08:58:25 +0000

Git Workflow for Release Management: Branches vs Tags

Most teams invent their Git strategy as they go. One developer starts tagging releases. Another uses branches. A third creates a hotfix branch and never deletes it. By the time you need to patch a six-month-old release, nobody remembers what release-final-v2 means or where hotfixes actually landed.

A clear branching strategy prevents this. This post covers a battle-tested Git workflow built around two parallel approaches — version control with branches and version control with tags — and tells you exactly when to use each.

Engineering Standards for DevOps: The Complete Guide

Pongsak Khamdee — Fri, 29 May 2026 08:58:25 +0000

Engineering Standards for DevOps: The Complete Guide

A team without standards is a team that reinvents everything — every time, in every project. Standards are not bureaucracy. They are the codified answers to questions your team has already solved, so you can spend your energy solving new ones.

This guide covers thirteen engineering standards that separate high-performing DevOps teams from the rest. For each standard, we go beyond the "what" to explain the "why" and the "how" — with concrete tooling, configuration examples, and the decision frameworks you need to implement them in your organisation.

DevOps Project Example: From Code Push to Production with GitOps, FluxCD, and Kubernetes

Pongsak Khamdee — Fri, 29 May 2026 08:58:25 +0000

DevOps Project Example: From Code Push to Production with GitOps, FluxCD, and Kubernetes

Most DevOps tutorials show you a pipeline diagram. This one shows you a real pipeline, built on a real application, running on real Kubernetes clusters — with every tool, every workflow, and every design decision explained.

This post walks through the complete CI/CD system behind Slotmachine — a real-time multiplayer tournament app — from the moment a developer pushes code to GitHub, through six security and quality gates, all the way to automated deployment on both Nutanix on-premise clusters and AWS EKS. No hand-waving. No "and then magic happens."

The full source code is available in two repositories:

Application repo: github.com/pkhamdee/slotmachine
Deployment repo: github.com/pkhamdee/slotmachine-deployment

The DevOps Delivery Pipeline: End-to-End Framework

Pongsak Khamdee — Fri, 29 May 2026 08:58:25 +0000

The DevOps Delivery Pipeline: End-to-End Framework

A DevOps framework is not a single tool or process — it is an end-to-end system that connects your product idea to production software, with quality and security built in at every step.

Cloud Engineer vs DevOps vs SRE vs Platform Engineer: Who Does What?

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

Cloud Engineer vs DevOps vs SRE vs Platform Engineer: Who Does What?

You're browsing job boards and you see four different titles: Cloud Engineer, DevOps Engineer, Site Reliability Engineer, Platform Engineer. The salaries are similar. The required skills overlap. Some listings seem interchangeable.

Are these the same job? Is one better than the others? Which should you aim for?

They are not the same job — but they are deeply related, and the confusion is completely understandable. Each role grew from a different pain point in how software gets built and run, and in 2026, all four exist inside most engineering organizations at the same time.

9 Essential Components of a Production Microservice App

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

9 Essential Components of a Production Microservice App

So you've built a microservice. It works on your laptop. Now your manager says "take it to production" — and suddenly you realize a working service and a production-ready service are two very different things.

This guide walks through all 9 essential components that every production microservice system must have, using the architecture diagram below as our map. By the end, you'll understand not just what each component is, but why it exists, how it works, and how to implement it in real code.

Tech Stack of a Modern AI App in 2026: The Complete Layer-by-Layer Guide

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

Tech Stack of a Modern AI App in 2026: The Complete Layer-by-Layer Guide

Everyone wants to build an AI app. Most people start with the same two lines:

python import openai response = openai.chat.completions.create(...)

That works for a demo. It does not work for a product. The moment you try to serve real users, you run into a wall of unanswered questions: Where does your data live? How do you keep the model's knowledge fresh? How do you know when it starts giving bad answers? How do you deploy it without rewriting everything from scratch every time the model changes?

A production AI application in 2026 is not a Python script. It's a 10-layer system — each layer solving a specific class of problem, each with its own ecosystem of tools.

This post is the map. We'll walk every layer from the ground up: what problem it solves, which tools the industry has standardized on, and how the layers connect. By the end, you'll be able to look at any real-world AI product and name exactly what's running inside it.

AI Agent Application Demo: Putting a Brain Inside Your App

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

AI Agent Application Demo: Putting a Brain Inside Your App

Source code: github.com/pkhamdee/coffee-agent

There's a quiet revolution happening in how we write software. For decades, we've built applications the same way: write a function, call the next function, handle each case with an if statement, repeat. The logic is explicit, deterministic, and completely predictable — a flowchart carved into code.

That model still works. But it has a hard ceiling.

When a user wants to do something that doesn't fit neatly into your flowchart — when they say something ambiguous, change their mind mid-conversation, or combine requests in ways you didn't anticipate — the rigid-logic app breaks down. You end up writing more and more special-case handling until the code becomes unmaintainable.

AI agents flip this model. Instead of programming every decision upfront, you give your application a reasoning engine — a brain — and let it figure out what to do. The application stops being a flowchart and starts being a collaborator.

This post walks through a real, runnable example: a coffee shop ordering chatbot called Coffee Agent. It's a full-stack app built with NestJS, React, LangGraph, and a local LLM running on Ollama. By the time you finish reading, you'll understand exactly what an agent is, why this architecture is powerful, and how to build one yourself.

PostgreSQL Server Tuning: The Complete 2026 Configuration Guide

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

PostgreSQL Server Tuning: The Complete 2026 Configuration Guide

A freshly installed PostgreSQL server is configured to run safely on a shared laptop from 2005. shared_buffers = 128MB. work_mem = 4MB. max_connections = 100. These defaults have not changed in over a decade — and they are deliberately conservative so the server starts without crashing on anything.

Your production server is not a 2005 laptop.

This guide covers every postgresql.conf parameter that matters, the OS-level settings that underpin them, and a ready-to-use configuration reference for common server sizes — all updated for PostgreSQL 17 on Linux in 2026. It is the server configuration companion to the query and index tuning guide, which covers EXPLAIN, indexes, and PgBouncer.

PostgreSQL Performance Tuning for Application Developers (2026 Edition)

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

PostgreSQL Performance Tuning for Application Developers (2026 Edition)

Slow queries are not a database problem. They are a design problem.

A query that takes 4 seconds on a table with 100 million rows almost always has a fixable root cause: missing index, wrong index type, table bloat, exhausted connection pool, or configuration defaults that were set for a 1GB dataset and never updated. Most performance problems are found — and solved — at the query and schema level before any hardware needs to be touched.

PostgreSQL High Availability with Patroni: 2026 Edition

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

PostgreSQL High Availability with Patroni: 2026 Edition

Running a single PostgreSQL instance in production is a liability. When it goes down — and it will — so does your application. High availability is not optional for production databases; it is the baseline.

This guide builds a production-grade PostgreSQL HA cluster using the fully open-source community stack: PostgreSQL 17 from PGDG, Patroni 4.x, etcd 3.5, pgbackrest 2.58, and HAProxy. No vendor-specific packages. No proprietary repositories. Everything here runs on Rocky Linux 9 or AlmaLinux 9 and stays fully open-source.

CKA Mock Exam — Complete Questions & Solutions

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

CKA Mock Exam — Complete Questions & Solutions

Exam Rules Reminder

Use sudo to edit files in /etc/kubernetes/manifests/
Use sudo for kubelet restart and system-level debugging
Use documentation links provided in each question
SSH into the correct node as specified in the question
Always verify the correct namespace before applying changes

CKA Cheat Sheet 2026

Pongsak Khamdee — Fri, 29 May 2026 08:58:24 +0000

CKA Cheat Sheet 2026

Exam Domains: Storage 10% | Troubleshooting 30% | Workloads & Scheduling 15% | Cluster Architecture 25% | Services & Networking 20%

Kubernetes version on exam: 1.34+ — kubectl is pre-configured, sudo required for node-level tasks. Allowed docs: kubernetes.io/docs, kubernetes.io/blog, helm.sh/docs

Quick Wins — Always Do First

```bash

Set alias (saves time on every command)

alias k=kubectl export do="--dry-run=client -o yaml" # k run pod1 --image=nginx $do > pod.yaml export now="--force --grace-period=0" # k delete pod pod1 $now

Autocomplete

source <(kubectl completion bash) complete -o default -F __start_kubectl k

Context switching (exam has multiple clusters)

kubectl config get-contexts kubectl config use-context kubectl config current-context ```

The 12-Factor App: The Complete Guide

Pongsak Khamdee — Fri, 29 May 2026 08:58:23 +0000

The 12-Factor App: The Complete Guide

Every cloud-native application fails the same ways: it leaks config into code, stores state in memory that dies on restart, has a local dev environment that behaves nothing like production, or can't scale horizontally because it writes files to disk.

The 12-Factor App methodology is a set of twelve principles that prevent all of these failures. Written by engineers at Heroku in 2011, it remains the most practical and universally applicable guide to building software-as-a-service applications. This guide takes you through every factor with real code, real anti-patterns, and how each principle translates to modern cloud-native deployments.

Crossing the Chasm: The Complete Guide to Technology Adoption

Pongsak Khamdee — Fri, 29 May 2026 08:58:23 +0000

Crossing the Chasm: The Complete Guide to Technology Adoption

In 1993, Apple launched the Newton — a handheld personal digital assistant a full decade before the smartphone era. It was revolutionary. It was technically impressive. It bombed spectacularly.

In 2007, Apple launched the iPhone. Same company. Arguably less technically innovative than what competitors had already shipped. It went on to become the most successful consumer product in history.

Same company. Same category. Completely different outcomes.

The difference wasn't the technology. It was the timing — specifically, whether Apple understood where the market was in its adoption lifecycle and positioned its product accordingly.

This guide explains the framework that makes sense of that difference: the Technology Adoption Lifecycle and Geoffrey Moore's landmark insight about the chasm inside it. We'll go deep on the theory, explore the psychology of every adopter type, and apply it to cloud-native technologies that are reshaping software today.

Software Development Strategy: The Complete Guide

Pongsak Khamdee — Fri, 29 May 2026 08:58:23 +0000

Software Development Strategy: The Complete Guide

Most software projects fail for one of two reasons: they build the wrong thing right, or they build the right thing wrong.

Building the wrong thing right means you execute perfectly — on time, on budget, with clean code — but the product solves a problem nobody actually has. Building the right thing wrong means you deeply understand the user's pain but your delivery is so slow, brittle, and expensive that the opportunity is gone before the product ships.

The framework that fixes both failure modes: Design Thinking + Lean + Agile — applied together, not picked from a menu.

Principles of Software Design: The Complete Guide

Pongsak Khamdee — Fri, 29 May 2026 08:58:23 +0000

Principles of Software Design: The Complete Guide

Every senior engineer you admire follows a set of principles — not rules written in a style guide, but instincts built from hard experience. They look at code and immediately feel whether something is wrong, even before they can articulate why.

Those instincts are learnable. They're codified in the principles this guide covers.

Software design principles are heuristics — guidelines, not laws. No principle applies in every situation. But together they form a vocabulary for talking about code quality and a compass for navigating trade-offs. Internalize them, and you'll spend less time untangling the past and more time building the future.