<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Devops Monk</title><link>https://blog.devops-monk.com/tags/devops/</link><description>Recent content in DevOps on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.devops-monk.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>MonkKit — 106 Free Developer Tools in One Place</title><link>https://blog.devops-monk.com/2026/05/monkkit-developer-tools/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/monkkit-developer-tools/</guid><description>I was tired of bouncing between a dozen different sites just to format JSON or decode a JWT. One tab for a JSON formatter. Another for a Base64 decoder. Another for a DNS lookup. Another for an SPF validator. Browser full of bookmarks, half of them plastered with ads, most requiring an account to do anything useful.
So I built MonkKit — a single place for all of them. 106 free developer tools across 10 categories.</description></item><item><title>Claude Code Plugins: The Complete Guide to Building and Sharing Extensions</title><link>https://blog.devops-monk.com/2026/05/claude-code-plugins-guide/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-code-plugins-guide/</guid><description>Skills, agents, and hooks you add to .claude/ are powerful — but they are locked to one project. Every time you start a new repo you copy the same files, maintain them in multiple places, and drift out of sync. Claude Code plugins solve this: a plugin is a shareable, versioned package that carries all your customisations and can be installed in any project with one command.
This post covers what plugins are, when to use them, and how to build a real one from scratch — a DevOps helper that ships a deployment skill, a pre-deploy safety hook, and an MCP server connection to your Kubernetes cluster.</description></item><item><title>Building a Full-Stack Personalised Gifts E-Commerce Platform with Next.js 15</title><link>https://blog.devops-monk.com/2026/05/personalised-gifts-ecommerce-platform/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/personalised-gifts-ecommerce-platform/</guid><description>Building an e-commerce site is one of those projects that sounds simple until you actually start. Payments, authentication, inventory, personalisation, image handling, email notifications, admin tools, live chat — each piece is its own rabbit hole. I built PersonalisedGifts, a full UK-market personalised gifts store from scratch, wiring all of these together into a single cohesive product.
The site lets customers browse gifts by category (Mugs, Jewellery, Canvas Prints, Home Décor) or occasion (Birthday, Wedding, Christmas, New Baby), personalise their chosen item with custom text, images, fonts, or colours, and pay via Stripe (cards, Apple Pay, Google Pay, Klarna) or directly from their bank account via Tink&amp;rsquo;s open banking integration.</description></item><item><title>Claude Extended and Adaptive Thinking: Making Claude Reason Before It Answers</title><link>https://blog.devops-monk.com/2026/05/claude-adaptive-thinking-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-adaptive-thinking-guide/</guid><description>By default, Claude generates its response token by token without any deliberate planning step. For most tasks — answering a question, writing a function, explaining a concept — this is fine. The response comes quickly and it is good.
For some tasks, it is not enough. Complex multi-step reasoning problems, ambiguous architecture decisions, intricate security analyses — these benefit from Claude thinking through the problem before committing to an answer. That is what extended thinking and adaptive thinking provide.</description></item><item><title>Claude Managed Agents: Deploy AI Agents Without Managing Infrastructure</title><link>https://blog.devops-monk.com/2026/05/claude-managed-agents-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-managed-agents-guide/</guid><description>Building an AI agent that runs autonomously — browses the web, executes code, reads and writes files, persists memory across sessions — requires infrastructure. You need a sandbox, a process that can run for hours without your web server timing out, and a way to resume from where you left off after a network hiccup.
Claude Managed Agents, launched in public beta in April 2026, offloads all of that to Anthropic.</description></item><item><title>Claude Models in 2026: Opus, Sonnet, and Haiku Compared</title><link>https://blog.devops-monk.com/2026/05/claude-models-guide-2026/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-models-guide-2026/</guid><description>Picking the wrong Claude model is expensive. Opus on every task costs 5x more than Sonnet for comparable results on most work. Haiku on a complex reasoning task produces worse output than just asking Sonnet. And if you are still using models from early 2025, some of them are deprecated — or will be soon.
This guide covers every current Claude model, what each is good at, how much they cost, and a concrete decision framework for choosing the right one.</description></item><item><title>Claude Prompt Caching: Cut Your API Costs by 90%</title><link>https://blog.devops-monk.com/2026/05/claude-prompt-caching-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-prompt-caching-guide/</guid><description>If you are calling the Claude API repeatedly with a large system prompt, a big document, or a long codebase context — and you are not using prompt caching — you are paying full price every time for content that has not changed. Prompt caching stores a prefix of your prompt server-side and charges 90% less to read it back on every subsequent request.
For applications that repeatedly process the same context, this is the single highest-impact API optimisation available.</description></item><item><title>Spring Boot 4.0: Everything That Changed (Complete Guide)</title><link>https://blog.devops-monk.com/2026/05/spring-boot-4-complete-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/spring-boot-4-complete-guide/</guid><description>Spring Boot 4.0 was released on November 20, 2025. It is built on Spring Framework 7 and represents the most significant shift in the Spring ecosystem since the Jakarta EE migration in Spring Boot 3. The headline change is full modularisation — the single spring-boot-autoconfigure JAR has been split into 70+ granular modules. But that is just the start.
This guide covers every change that matters, what breaks on upgrade, and what is genuinely new and useful.</description></item><item><title>Spring Boot Docker: Multi-Stage Builds, Layered JARs, and Buildpacks</title><link>https://blog.devops-monk.com/2026/05/spring-boot-docker-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/spring-boot-docker-guide/</guid><description>There are three ways to containerise a Spring Boot application: a naive single-stage Dockerfile, a proper multi-stage Dockerfile with layered JARs, and Cloud Native Buildpacks. Each has different tradeoffs in build speed, image size, and maintenance overhead.
This guide covers all three approaches, explains why layered JARs matter for CI/CD speed, and shows how to produce small, secure, production-ready images.
The Problem with the Naive Dockerfile Most tutorials show this:</description></item><item><title>Spring Boot on Kubernetes: Health Checks, Graceful Shutdown, and Config Management</title><link>https://blog.devops-monk.com/2026/05/spring-boot-kubernetes-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/spring-boot-kubernetes-guide/</guid><description>Running Spring Boot on Kubernetes is not just packaging the app in a container and deploying it. You need to configure health probes correctly, handle graceful shutdown so in-flight requests don&amp;rsquo;t get dropped, manage configuration without baking secrets into images, and make sure the JVM respects container memory limits.
This guide covers the production-critical Kubernetes configuration for Spring Boot applications.
Health Probes Kubernetes uses three probe types to manage pod lifecycle:</description></item><item><title>Building a Zero-Cost Stock Market Intelligence Platform</title><link>https://blog.devops-monk.com/2026/04/stock-market-analysis-dashboard/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/stock-market-analysis-dashboard/</guid><description>Most stock screeners cost $30–$200 per month. Bloomberg Terminal costs $24,000 per year. I built something that does a meaningful fraction of what those tools do — analysing 220+ UK and US stocks every hour, scoring them across six dimensions, detecting bearish warning signals, running insider trading checks via SEC EDGAR, and presenting everything in a React PWA — at zero ongoing cost.
The platform is live at share.devops-monk.com. The full source is at github.</description></item><item><title>Claude Code as a Security Scanner: Beyond Pattern Matching</title><link>https://blog.devops-monk.com/2026/04/claude-code-security-scanner/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-code-security-scanner/</guid><description>Tools like ESLint, Semgrep, and Bandit catch what they are programmed to find: known patterns, common injection strings, deprecated API calls. They are fast, reliable, and deterministic. They are also blind to anything that requires understanding what your code is supposed to do.
Claude Code operates differently. It reads code the way a human security researcher would — tracing data flows across files, understanding business logic, and reasoning about what could go wrong given the specific context of your application.</description></item><item><title>Claude Code Hooks, Commands, Skills, and Subagents: The Complete Guide</title><link>https://blog.devops-monk.com/2026/04/claude-code-hooks-subagents-piping/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-code-hooks-subagents-piping/</guid><description>Most teams use Claude Code reactively — they type a prompt, Claude responds, they type another. That is fine, but it leaves significant value on the table. Claude Code has four automation layers that let you turn it from a reactive assistant into an active workflow participant:
Layer What it does When to reach for it Hooks Shell or HTTP calls that fire on lifecycle events &amp;ldquo;This must happen every time, without exception&amp;rdquo; Custom Commands Reusable slash commands for repeatable prompts &amp;ldquo;I type the same prompt repeatedly&amp;rdquo; Skills Context-aware instructions Claude loads automatically &amp;ldquo;Claude should always do X when working on Y&amp;rdquo; Subagents Separate Claude instances for isolated, parallel work &amp;ldquo;This task is noisy and the main session only needs a summary&amp;rdquo; This post covers how to create each one and when to use them.</description></item><item><title>Claude Computer Use for DevOps: When to Use It and When to Use an API</title><link>https://blog.devops-monk.com/2026/04/claude-computer-use-devops-workflows/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-computer-use-devops-workflows/</guid><description>Claude&amp;rsquo;s computer use capability — the ability to see your screen and interact with applications via mouse clicks, keyboard input, and scrolling — is one of the most discussed features in the AI space. It is also one of the most misapplied.
The correct mental model is not &amp;ldquo;Claude can now automate everything on my screen.&amp;rdquo; It is &amp;ldquo;Claude now has a flexible fallback layer for tasks that do not have a structured API integration.</description></item><item><title>Mastering Claude Code CLI: The Complete Guide for DevOps Engineers</title><link>https://blog.devops-monk.com/2026/04/mastering-claude-code-cli/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/mastering-claude-code-cli/</guid><description>If you have been using Claude in a browser tab to help with code, you are leaving most of its capability on the table. Claude Code CLI brings the full power of Claude directly into your terminal — it reads your actual codebase, runs real commands, edits files, commits code, and integrates with every tool in your DevOps stack. This guide covers everything from installation to advanced patterns that most engineers never discover.</description></item><item><title>MCP Servers Worth Installing: For Developers, Testers, and DevOps Teams</title><link>https://blog.devops-monk.com/2026/04/mcp-servers-for-devops-teams/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/mcp-servers-for-devops-teams/</guid><description>The MCP (Model Context Protocol) ecosystem now has over 14,000 servers. Most of them you do not need. Installing too many slows responses, inflates your context window with tool definitions that never get used, and turns debugging into a guessing game across a dozen integrations.
This guide applies a simple filter: only install a server if it replaces a daily copy-paste workflow. It is organised by role — developers, QA testers, and DevOps/platform engineers — because the right stack is different for each.</description></item><item><title>Writing a CLAUDE.md That Actually Works</title><link>https://blog.devops-monk.com/2026/04/writing-claude-md-that-works/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/writing-claude-md-that-works/</guid><description>Every CLAUDE.md file gets loaded into context on every session. Most teams treat it like documentation — a place to describe the project, list the tech stack, explain what the tests do. That is the wrong mental model and it is why most CLAUDE.md files are both too long and too ineffective.
CLAUDE.md is behavioral programming. Its job is to change how Claude makes decisions, not to describe facts that Claude can read from the codebase itself.</description></item><item><title>You Don't Need a Framework to Build an AI Assistant</title><link>https://blog.devops-monk.com/2026/04/build-ai-assistant-without-framework/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/build-ai-assistant-without-framework/</guid><description>There is a tendency in the AI tooling space to reach for frameworks — LangChain, AutoGen, CrewAI, OpenClaw — the moment you want an AI that does more than answer one question at a time. Most of the time, that is the wrong move. The framework adds complexity, dependencies, and debugging surface area for problems that a few shell scripts and cron jobs solve perfectly well.
Claude Code&amp;rsquo;s headless mode (-p flag) plus a markdown file for personality plus cron scheduling is a complete AI assistant stack.</description></item><item><title>Build Your Own DDNS Platform</title><link>https://blog.devops-monk.com/2026/04/build-your-own-ddns-platform/</link><pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/build-your-own-ddns-platform/</guid><description>If you run a home server — a Raspberry Pi, a NAS, a Kubernetes cluster in your garage — you have probably hit the same annoying wall: your internet provider gives you a different public IP address every few days, and suddenly nobody can reach your server anymore. This post explains how I solved that problem by building ddns.devops-monk.com, a fully self-hosted Dynamic DNS platform. I will walk through the idea from scratch, explain every moving part in plain English, and include full architecture diagrams for those who want the deep technical picture.</description></item></channel></rss>