All Code Encounters

A complete collection of real-world examples to learn from

Showing 10 of 10 posts

Fire and Forget (Your Sanity)

Using async void for background operations turns unhandled exceptions into application-ending surprises

A custom exception wrapper that throws exceptions while trying to safely handle exceptions

AsyncConnection has close() method but no __aenter__() - it's a context manager that only knows goodbye

Auth middleware with no fallbacks creates a single point of failure - when the central service goes down, your entire app stops, even health checks.

Regex-driven file parser with empty catch blocks and no validation becomes a production disaster.

God class violates Single Responsibility by handling connections, validation, logging, and control in one place.

A monolithic IIFE doing prototype hacking, browser detection, and module loading all at once.

Bare except clauses catch everything including KeyboardInterrupt, making code impossible to debug or stop.

A singleton pattern without thread safety creates race conditions and multiple instances.

Explicitly setting all properties to null defeats TypeScript's type safety and creates runtime bombs.