Introducing DevGuessr! A daily tech stack guessing game for software engineers

Building DevGuessr started as a fun idea but quickly evolved into the most technically demanding project I have ever shipped. To get this daily puzzle suite ready for the software engineering community I had to solve some serious architectural and design challenges.

Here is a look under the hood at exactly what it took to bring this stack to production.

1. Engineering the Core Game Mechanics

• Langdle Logic: Building the comparison engine required mapping out technical specs like memory management and scope syntax for a massive dataset of programming languages. I wrote complex evaluation logic to provide accurate green, amber, and red feedback based on the distance from the correct answer. The daily engine handles case insensitive lookups, historical puzzle retrieval, and bulk creation with strict database constraints.
• Mythdle Balance Tuning: Early versions of the logic puzzles were too random. I implemented a strict split of two easy, two medium, one hard, and one fake to ensure the daily drops were accessible to students but still challenged engineering veterans.
• Race Condition Safety: The game creation endpoints needed to be bulletproof. I ensured race condition safe puzzle generation using unique indexes and exception handling. This meant managing everything from duplicate dates to empty tables, all backed by 100 percent test coverage.

2. Mastering the Visual Data Pipeline

• The Pixel Leak Pipeline: For Logodle, visual data abstraction was incredibly tricky. Logos needed to transform through a specific five tier pixelation scale. I had to solve SVG to PNG conversion issues while maintaining transparency for the dark UI. On the backend I had to cap the blur strength because ImageSharp would throw errors on large sigma values for smaller images.
• Frontend Synchronization: Keeping the image reveal system fluid required cache busting tokens to prevent stale images from loading. I also had to sync static constants directly with the backend CSVs and ensure all dropdowns were fully accessible for keyboard navigation.

3. Enforcing Architecture and Resilience

• Clean Architecture Constraints: Placing new features like the daily engine required strict adherence to architecture buckets. Everything had to sit perfectly within Services, DTOs, and Repositories rather than bleeding into top level folders. Controller validation was locked down using globally registered filters.
• Infrastructure Hardening: To make the API production ready I built in idempotency for daily puzzle submissions to prevent duplicate entries. I layered on strict throttling and rate limiting to stop brute force attempts and integrated structured logging with Seq for reliable debugging in the wild.

4. Taming the Deployment Infrastructure

• Docker Orchestration: The goal was to let anyone clone the repo, run a single docker compose up command, and have the entire stack spin up seamlessly. This meant carefully managing environment variables and dependency injection across the API, PostgreSQL, Redis, RabbitMQ, Seq, Nginx, and the Angular frontend.
• Gateway Routing: Correctly proxying the frontend and backend services brought its own headaches, specifically handling Docker DNS and avoiding stale IP addresses after Nginx or service restarts.

5. Aesthetics and The Human Element

• Precision Glitch Design: Maintaining the Cyber Zen design language across the application was a continuous effort. Even static pages like the Privacy Policy had to follow aggressive typography scales and intentional asymmetry without breaking mobile responsive layouts.
• SEO and Authentic Voice: The final pass was refining the project voice. I stripped away formalisms and typical AI generated patterns to ensure the documentation felt authentic to a human led engineering project while pushing dynamic SEO metadata for search visibility.

It has been a massive journey of full stack problem solving. You can play today’s challenges at https://devguessr.site and check out the complete source code and architecture on my GitHub.