Software engineer by day, tinkerer by night. I write about code, career lessons, side projects, and the human side of building software.
I spent the better part of two years on an enterprise AWS cluster migration that started without a proper plan. Here is a first-person account of what went wrong, what could have been done differently, and the lessons I'm carrying into every project from now on.
Injection sits at A03 of the OWASP Top 10 and still ships in production code more often than any of us would like to admit. Here is a practical, first-person walkthrough of how injection works, where it hides in modern stacks, and how I keep it out of my own code.
Cryptographic failures are the silent data leaks behind most modern breaches. Here is what they are, why OWASP ranks them A02, and how I prevent them in production.
Broken access control is the number one OWASP risk because it is silent, easy to ship, and devastating to recover from. Here is how it happens, how attackers exploit it, and how I prevent it in production code.
Work-life balance is the deliberate division of time and energy between professional work and personal life. For developers, it is the single biggest predictor of long-term productivity, mental health, and career longevity. Here is why it matters and how to actually protect it.
Understand Drupal caching: compare page and render caches, use cache tags, contexts and max-age, and debug stale content with response headers.
Integrating a code review and security analysis platform like SonarQube into your development lifecycle catches bugs early, prevents security vulnerabilities, and keeps your codebase maintainable as it scales.
Vibe coding with AI tools like Copilot and ChatGPT can dramatically speed up development, but the quality of your output depends entirely on how clearly you define your requirements. Here is how to get the best of both worlds.
The OWASP Top 10 was updated in 2025 with new categories like Software Supply Chain Failures and Mishandling of Exceptional Conditions. Here is a beginner-friendly guide to every category, a 2017 to 2025 mapping, and code examples you can apply today.
Clean code is code that is easy to read, maintain, and extend. Here are the essential principles - meaningful names, single responsibility, avoiding magic numbers, DRY, tests as documentation, and the Boy Scout Rule.