Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 86
  1. A single unbuffered channel send without an active receiver is enough to silently lock up a production worker pool, leaking memory until your service gets killed by the OS kernel.

  2. Generating a raw matrix of integer tiles gives you a map layout, but it doesn’t give you a living environment.

  3. Linux crontab is one of the most elegant pieces of software ever written for single-host automation.

  4. Building a terminal-based engine in pure ASCII looks cool for about five minutes.

  5. When I started building Derelict Facility, my initial instinct for game actors was standard Object-Oriented design: create an Entity struct, add pointers for position, sprite, and stats, and store them in a slice ([]*Entity).

  6. In How Multi-Tenant SaaS Actually Works, I left one major promise unfulfilled at the end: “Billing is an entire system design on its own.

  7. Most Couchbase performance tickets I have seen end the same way: someone adds more nodes, the dashboard looks a little better for a week, and the same query shows up in the slow log a month later.

  8. A few weeks ago I designed Relay, a multi-tenant AI API gateway, as a system design exercise.

  9. There is a moment in every backend engineer’s life when their database starts refusing connections.

  10. There is a class of bugs that only happen at midnight.

  11. For the past month I have been reading about multi-tenant SaaS architecture.

  12. There is a funny truth in software engineering: almost nobody reads the docs.

  13. There is a famous programmer joke that always gets me: “What is DRY?

  14. I wanted to upgrade the RAM in my PC.

  15. I spent a Saturday afternoon benchmarking a concurrent inverted index and discovered that a single sync.RWMutex starts to break down at roughly 4 concurrent readers.

  16. I recently spent four hours staring at a benchmark that didn’t make sense.

  17. Wireless ADB keeps timing out if you run a VPN or something like Cloudflare WARP.

  18. Privacy & Terms

    This is a personal blog.

  19. “Can we just add a real-time visitor counter to the homepage?

  20. Time is an illusion.

  21. The marketing for “schemaless” architecture was brilliant.

  22. Application code is stateless.

  23. A while back, I was tinkering in the Cloudflare dashboard and accidentally fat-fingered a DNS configuration.

  24. Filter by Era/Domain: All Records Frameworks Hardware Infrastructure Protocols & Standards Services Social Google Reader 2005 - 2013 Services Cause of Death Strategic shift towards Google+; lack of direct monetization.

  25. TL;DR: The Critical Rendering Path (CRP) is how browsers convert code into pixels.

  26. TL;DR: I achieved 95+ Lighthouse scores by removing abstractions and automating browser fundamentals.

  27. TL;DR: Spawning go func() without a limiter is a recipe for system collapse.

  28. At the end of generating a procedural map for the Derelict Facility engine, I had a sprawling interconnected maze of rooms and corridors.

  29. The biggest architectural mistake you can make when building a game engine is letting the game know how it is being drawn.

  30. Most game development stories start the same way: install Unity, drag some sprites onto a canvas, and press Play.

  31. TIL how ClickHouse works with Parquet beyond just reading files.

  32. This post tracks four architectural rewrites of my personal site over ten years: moving from managed platforms (Blogger) to dynamic backends (Django), static site generators (Jekyll/Hugo), and finally to a custom, zero-dependency architecture built for ab…

  33. My Reading List

    All Analytics Backend Database Design DevOps General Hacking Hardcore Linux Design Knitting Bullshit by Kate Davies Kate Davies' blog.

  34. TL;DR: I run k3s on a Windows gaming PC via WSL2 to master Kubernetes networking without cloud costs.

  35. If you’re running a production observability stack, you’ve already leaked PII.

  36. When you’re building Go services that handle millions of operations per second, the hardware beneath your abstractions starts to matter.

  37. This blog teaches almost all about typography.

  38. Postgres is the most reliable tool in my stack.

  39. WSL2 (Windows Subsystem for Linux) has been a godsend for developers who love Linux tools but need/have a Windows environment.

  40. What is a Mutex?

    Read more: https://nrecursions.blogspot.com/2014/08/mutex-tutorial-and-example.html

  41. “Write a REST API with authentication”.

  42. I used to rebuild my Docker image every time I fixed a typo.

  43. I thought processing audio in the background was simple: spawn a thread, run the script, save the file.

  44. You write a struct to represent a database entity.

  45. I’ve been using aider as my primary AI coding assistant for a while now.

  46. Everyone’s building AI apps now.

  47. We often talk about “fast” code in terms of Big O notation or algorithmic complexity.

  48. At a recent ClickHouse conference in New Delhi, I attended this Saturday.

  49. What to expect New Deep Dives: Breakdown of backend architecture, Go internals, and systems thinking.

  50. In the world of high-throughput backend services, we often obsess over the usual suspects of performance: database indexing, network latency, and algorithmic complexity.