Promoted your best developer to manager? Congratulations. You just destroyed two careers. by Matt Watson

Engineers optimize for code quality. Managers optimize for human potential. These are fundamentally different skill sets.

I once watched a team’s velocity drop by half after hiring their best engineer. by Alex Di Mango

Teams don’t scale through individual brilliance. They scale through collective momentum.

The engineers who actually multiplied output never looked like rockstars. They wrote boring, obvious code that anyone could maintain. They approved pull requests that were good enough, not perfect. They spent time pairing with people who were stuck instead of cranking out features alone.

Amazon S3 quietly became a concurrency control system. by Raul Junco

People often ask how we balance speed and quality at @tryramp. by Eric Glyman

We don’t. Because speed is how you get to quality.

December 2025

On Metastable Failures and Interactions Between Systems by Aleksey Charapko

Fault-tolerance is hard, and in the case of metastable failures, maybe next-to-impossible and/or expensive. I have a hunch that we may not be able to avoid metastable failures entirely in large, non-trivial systems that are also economical to operate, because of these “forced” actions that systems sometimes have to take. However, the three strategies above remain effective mitigation approaches. Just replace “avoid” with “avoid as much as possible.”

A catastrophic accident has struck the Mars outpost. Communication with Earth is completely severed. Only a handful of survivors remain.

Marsettler is a simulation where players shape the story of these survivors. Your journey becomes a narrative—a story worth sharing.

What’s in v0.0.0

• Autonomous AI: Characters find iron mines, extract ore, and haul it to the warehouse on their own
• Behavior Tree System: The architecture powering AI decision-making
• Resource Management: Mines deplete and disappear when exhausted

Run Simulation

How we found a bug in Go’s arm64 compiler by Thea Heinen

A release? Infrastructure changes? The position of Mars?

Our investigation stalled for a while at this point – making guesses, testing guesses, trying to infer if the panic rate went up or down, or if nothing changed.

A reproducible crash with standard library only? This felt like conclusive evidence that our problem was a runtime bug.

• https://github.com/golang/go/commit/f7cc61e7d7f77521e073137c6045ba73f66ef902

Index

• Performance
• Concurrency
• Distributed Systems
• Generics
• Reiaibility
• Others

Performance

We tried Go’s experimental Green Tea garbage collector and it didn’t help performance by Zach Musgrave

Parsing Protobuf Like Never Before by mcyoung

Deep dive into a go binary by Jesús Espino

If you want to know how high performance systems written in Go were built, read VictoriaLogs: https://github.com/VictoriaMetrics/VictoriaLogs by Phuong Le

1. Custom bloom filters to reduce disk I/O and CPU cycles for redundant logs.
2. Column-oriented block storage for better compression ratio and cache locality.
3. Memory-mapped files with automatic pread fallback for zero-copy reads.
4. Lock-free object pools and arena allocators to reduce heap allocations.
5. Reflection-free JSON parsers for streaming at hundreds of MB/s per core.
6. Compile-time templates replace text/html parsing with near-printf speed.
7. Dictionary-aware Zstd compression balancing CPU cost against bandwidth savings.
8. Multi-core parallelism everywhere with adaptive concurrency limits.
9. Scatter-gather fan-out writes with adaptive concurrency for network saturation.
10. Fast hashing and lock-free randomization for minimal contention.

How Go 1.24’s Swiss Tables saved us hundreds of gigabytes by Nayef Ghattas

Finding performance problems by diffing two Go profiles by Zach Musgrave

Optimising and Visualising Go Tests Parallelism: Why more cores don’t speed up your Go tests

Leveraging benchstat Projections in Go Benchmark Analysis!

Benchmarks and performance testing

New unique package by Michael Knyszek

This work also led us to reexamine finalizers, resulting in another proposal for an easier-to-use and more efficient replacement for finalizers. With a hash function for comparable values on the way as well, the future of building memory-efficient caches in Go is bright!

In the AI Era, Focusing on Essentials Instead of JPA Complexity by 백명석 (Translated from Korean)

The bigger problem was that JPA’s relationship mapping feature was too good.

JPA is overkill.

The problem of domain logic becoming dependent on JPA

Investment

When do VCs start seriously thinking about exits? by Demo Day (Translated from Korean)

For VCs, exits are not about “greed” but a “structural inevitability.”

As a founder, you must always check the ‘fund maturity date’ of your VC.

Human Resources

Things to watch out for when expanding team size by Seunghoon Lee (Translated from Korean)

1. Speed (e.g., product update speed, new technology development/launch speed, etc.) must increase compared to the past. (The idea that speed can slow down for the sake of stability and structure is 99% wrong. You must add stability and structure while making things even faster.)

News

November 2025

I Believe Rocket Lab Could Lose Half Its Value, Buy It Then by David H. Lerner

Summary

• Rocket Lab is a high-potential space company led by visionary CEO Peter Beck, expanding into defense and satellite markets.
• RKLB posted record Q2 revenue of $144M, up 36% YoY, and is executing well on contracts, including a $515M Space Development Agency project.
• The upcoming Neutron rocket launch is a major catalyst, but repeated delays and high expectations create significant short-term risk for the stock.
• RKLB is currently priced for perfection (P/S 52x); a failed Neutron launch could drive shares lower, presenting a potential buying opportunity.