About Dev Drunk
Dev Drunk is an independent engineering publication maintained by Kim, a backend software engineer focused on Java, Spring Boot, Kafka, databases, infrastructure, and applied AI.
Why this site exists
Reliable systems are built through constraints, tradeoffs, failed assumptions, and careful verification. Dev Drunk records those decisions in a form that another engineer can inspect and apply. The goal is not to publish the largest number of tutorials. It is to make each article useful when a real system is slow, unreliable, difficult to operate, or hard to understand.
What you will find here
- Java and Spring Boot implementation decisions
- Kafka delivery, consumer, and operational behavior
- Database performance and connection management
- Infrastructure, observability, and production safeguards
- AI engineering evaluated as a software system, not as hype
- Incident analysis and lessons when evidence is available
How content is reviewed
AI tools may assist with research, outlining, proofreading, or organization. They are not treated as a source of truth. Technical claims should be checked against current primary documentation, code examples should be validated where practical, and version assumptions should be stated. Older articles are being audited under a KEEP, REWRITE, NOINDEX, or DELETE review process.
When an article describes a lab or design exercise rather than a verified production incident, it should say so. Dev Drunk does not invent employers, traffic numbers, incidents, benchmarks, or operational outcomes.
Read the complete Editorial Policy or send a correction through the Contact page.