6d ago · 4 min read · There's a moment every developer eventually recognizes: code that works perfectly but makes no sense. You didn't write it, you can't explain it, and now you need to change it. This is the quiet crisis emerging across engineering teams as AI coding as...
Join discussion
Apr 19 · 15 min read · Peer review is not paperwork. When a reviewer tells you "unchecked derivations are your highest-risk failure class," they are handing you the exact failure that will bite you if you skip the checklist. On April 15 a FLOPs figure in pre-filing patent ...
Join discussionApr 10 · 3 min read · The Problem of Vibe Coding in Software Engineering In recent years, we have seen a significant surge in discussions surrounding the use of AI in software development. While the benefits of AI tools are undeniable, they have also given rise to a dange...
EEthan commented
Mar 29 · 10 min read · Finding a bug in production costs significantly more to fix than catching it during development. This is the core argument behind shift-left testing, the practice of moving quality checks earlier in t
Join discussionMar 22 · 6 min read · Originally published on my blog Last weekend I shipped two repositories from scratch: an opinionated full-stack template for PHP 8.4 + Symfony 8 + SvelteKit 2, and a complete habit tracking application built on top of it. 51 commits, 6 GitHub Action...
Join discussionMar 22 · 6 min read · Originally published on my blog Last weekend I shipped two repositories from scratch: an opinionated full-stack template for PHP 8.4 + Symfony 8 + SvelteKit 2, and a complete habit tracking application built on top of it. 51 commits, 6 GitHub Action...
Join discussionMar 22 · 6 min read · Originally published on my blog Last weekend I shipped two repositories from scratch: an opinionated full-stack template for PHP 8.4 + Symfony 8 + SvelteKit 2, and a complete habit tracking application built on top of it. 51 commits, 6 GitHub Action...
Join discussion
