Lessons from real projects, written down.

A practical guide to codebase readiness, task scope, version pinning, approval authority, verification evidence, and a 30-day pilot before applying AI-DLC to production maintenance.

We examine how persistent Blacksmith builders, serialized cache writers, and parallel image and CI jobs changed production performance and development-cycle economics.

We compared six configurations built from three models and three prompt stages on 200 production records without labeled ground truth. A model change added 14 percentage points of proxy agreement; a prompt revision added 37. The selected configuration costs $7.20 per month.

A comparison of direct OpenAI and Anthropic APIs, Amazon Bedrock, Microsoft Foundry, Google Cloud, VPC deployments, and on-premises hosting across network path, processing location, retention, and legal basis.

A practical framework for putting security, key exposure, departmental cost, guardrails, and observability behind one enterprise AI gateway, with four implementation paths compared.

How MCP's request-oriented model changes deployment and state ownership across AgentCore Runtime, Gateway, and targets, with a practical dual-version migration path.

How we validated manual content tagging and translation in a four-week PoC, then moved it into production at tens of thousands of items per month.

We re-read a six-year-old service's abandoned AWS account through API inventory and measured metrics, then executed an Aurora major upgrade and rightsizing with zero-downtime tooling. Monthly cost dropped to a quarter without touching application code.

An AWS alert put one day of S3 data transfer at $455,000. The estimate was wrong, but we still had to investigate account compromise. The incident shows why billing communication is part of cloud security.

A practical guide to modernizing legacy applications without a big-bang rewrite: assess the current estate, choose retain, replace, replatform, refactor, or rearchitect, then design phased cutover and outcome metrics.

Map South Korean website controls across DNS, IP, SNI, and CDN layers, with July 2026 DoH, DoT, and ECH support and international cases.

We used 30 questions and 8 follow-up sets to isolate retrieval, grounded generation, and conversation context, then turn the results into RAG release gates.

A six-gate method for moving an AI proof of concept into production. Decide with evidence across value, data, evaluation, risk, architecture, and operating readiness.

Nobody broke in, yet money leaks every month. Missing VPC endpoints, cross-AZ data transfer, always-billed public IPv4, logs kept forever. AWS hidden costs with real Seoul-region rates and how to claw them back.

One leaked access key can burn tens of thousands of dollars a day on Bedrock. How LLMjacking works, the AWS account-management essentials, Bedrock key management, and the guardrails that cap the blast radius.

An eight-person SI project ended with core issues unsolved; alone, I fixed them in three days. Talent alone does not explain the gap, so I examine communication paths, diffused responsibility, decision structure, and the ownership gaps around re-architecture.

isitagentready.com scored our site 29, Level 1. Instead of filling the scorecard, we filtered by substance: Content Signals, markdown negotiation, a real MCP server, DNS-AID and DNSSEC — reaching 71, Level 5 (Agent-Native). And a hard look at what agent scores actually measure.

A Claude skill that turns one chat line into a dev quote. Not a quote generator, but a human-in-the-loop skill inside the sales pipeline: the human keeps two gates (approve, send) while the skill handles the sheet, PDF, and email draft in between.

ECH hides the destination domain from observers on the path, but it cannot change the policy decision of the endpoint that decrypts it: the CDN. How SNI and ECH work, which network layer controls what, and how the failure fingerprints differ.

We pit a hand-built pgvector pipeline against Amazon Bedrock's fully-managed Knowledge Base for a school-health advisory chatbot. On Korean table documents, what decided it?

We moved a service locked into a single deployment and external CI onto NKS on Naver Cloud. How we split it into infrastructure, DB, API, and frontend — and made Git the single source of truth with Terraform, managed Cloud DB, and ArgoCD GitOps.