1. The access collection black hole You need Figma access, Google Analytics, WordPress admin, GitHub, and the client's Slack. You ask. They forward a password email from two years ago. You ask again. Their developer says they'll get back to you. Three days pass. The fix: Send a single, complete access list on Day 1 — not "we'll need some access" but the exact list, with specifics for each tool,
Linux kernel source tree
This isn't an anti-Go post. Go is a great language. This is about what I want to understand. I just finished building an L7 HTTP load balancer in Go. It accepts connections. It parses HTTP headers. It forwards requests to backend servers using round-robin. It handles concurrent connections with goroutines. It has health checks. It works. And somewhere in the middle of it working, I realized I didn
Most developers use malloc without thinking much about what happens underneath. This project is an attempt to explore that layer by building a memory allocator from scratch in C. The allocator implements malloc, free, calloc, and realloc without relying on libc’s heap functions. It focuses on: Thread safety Per-thread caching (tcache) Efficient free block management using bins mmap-based memory g
Comments