This was created 15 years ago. What has changed since?

Go has the easiest profiling tooling I’ve used with `pprof`. A few other tips: * Use `net/http/pprof` to enable a web server that can be used to capture profiles at anytime: https://t.co/fb8cWUapqz * Clicking on a function in the flamegraph aligns all stacks on the function.

https://t.co/Axx7PiYirt

Data centers in orbit? Of course that’s your contention. Of course it is. You just finished watching a Scott Manley video on radiative heat transfer and now you think you’re gonna disrupt AWS with a few solar panels and a rideshare slot. You’re gonna believe that right up until

From:

Another argument that web development peaked around 2010:

Don’t buy a Jeep unless you love the car enough to put up with poor quality and terrible customer service *sigh* 😂😭

https://t.co/AbR9r5zc2H

Two things always come for your schema: 1. Booleans become enums or timestamps (enabledAt) 2. “User has one team” becomes “user has many teams”

Good reminder to always add an empty file on your server: dd if=/dev/zero of=~/emptyfile bs=1M count=4096 Then if the disk fills up, you can delete this file to reliably free up some space.

A question I often ask top software engineers I meet is: “How often do you read research papers?” The most common answer is a silent grunt. Top engineers do read some research papers occasionally, but they mostly ignore 99.9% of the papers that are supposed to mark advancements

And if you want to learn about how to create great bash scripts like the ones in the 1BRC repo for automating the leaderboard, check out my blog post:

Never thought my face would show up on the GitHub Trending page for 1) a Java project and 2) creating bash scripts… but here we are 😂 In any case, great to see folks still seeking out @gunnarmorling’s 1BRC for its lessons in performance engineering!

All hallucinations are wrong, but some are useful

And check out my unique approach to 1BRC using a perfect hash function to parse temperatures here: https://t.co/PJSeU4uFzV Thinking of moving this into a blog post, let me know if you’d like to see that.

Link:

Fun reliving @gunnarmorling ‘s 1 Billion Row Challenge on stream with @cmuratori and @MarcoBehler! 1️⃣🐝🏎️ Casey nails the key principles behind performance engineering: * The idiomatic way provided by a language is often the worst way to do it (from a performance perspective).

Gunnar writes really accessible posts on postgres logical replication (from the CDC angle). It only just clicked for me I should go back and read all his posts on the subject since I work on a logical replication product and I could use the primer. This article is from today.