Protty
@kingprotty
System optimizer + concurrency geek. Also @ziglang guy.
Probably the smoothest conference I've attended so far. Was also great meeting old and new faces alike. Props to TigerBeetle again for setting it all up. #systemsdistributed
The fastest way to get good at something is to do it a lot while carefully fixing your mistakes. This should be obvious but many people downplay the importance of a massive volume of action-feedback-adjustment cycles.
The fastest way to get good at something is to do it a lot while carefully fixing your mistakes. This should be obvious but many people downplay the importance of a massive volume of action-feedback-adjustment cycles.
I agree. Recently experiencing this a lot, having to follow through layers of "helper" functions and abstractions only to realize it could've avoided intermediary allocations or just be a few LOC once inlined.
When you split a function to N different small functions, the reader also suffers multiple "instruction cache" misses (similar to CPU when executing it). They need to jump around the code base to continue reading. Big linear functions are fine. Code should read like a book.
I turn 30 next week and in lieu of other plans I'm doing a little fundraiser! If you've ever enjoyed or benefited from my writing or communities, consider a little present. :) I've kicked things off by donating $300 each to Scholarship America and Malala Fund.
I was blown away how clean the code for LSM compaction in TigerBeetle is, despite the complexity of callback model. Then @jorandirkgreef told me that they rewrote it once and are will maybe rewrite it again because they're totally happy with it. That's commitment to code quality!
Blog: Intuiting TLS The thought process of starting with "I want to talk privately on the internet" & ending up on something that looks like TLS. kprotty.me/2025/04/01/int…