Dead poets society

эти ваши контейнеры с нами в одной комнате?

2026-05-02T22:21:56+00:00

эти ваши контейнеры с нами в одной комнате?

wtf, map[name: Will Larson]? Is this hugo? p.s. huh, it IS hugo https://github.com/lethain/staff-en

2026-05-02T12:29:16+00:00

wtf, map[name: Will Larson]? Is this hugo?

p.s. huh, it IS hugo https://github.com/lethain/staff-eng

ok, so I'm reading https://staffeng.com/, I'll be shitposting cool stuff that I find along

2026-05-02T12:27:02+00:00

ok, so I'm reading https://staffeng.com/, I'll be shitposting cool stuff that I find along the way, so first

There’s a well-worn model of genius encapsulated in the Feynman algorithm: “1) Write down a problem. 2) Think very hard. 3) Write down the solution.”
I love this cuz writing down the solution straight away doesn't leave any room for historical context/review/discussion and shit. You might look like a genius to yourself, but it would be fucking useless for the folks who inherit whatever you've done

https://docs.zen-browser.app/user-manual/shortcuts

2026-05-02T11:41:19+00:00

https://docs.zen-browser.app/user-manual/shortcuts

https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/

2026-04-12T09:50:53+00:00

https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/

https://github.com/sqlc-dev/sqlc/discussions/364#discussioncomment-16447398

2026-04-04T13:22:46+00:00

https://github.com/sqlc-dev/sqlc/discussions/364#discussioncomment-16447398

I made something https://github.com/fira42073/valkyrie

2026-02-25T19:49:10+00:00

I made something
https://github.com/fira42073/valkyrie

FUCK THIS IS SO AMAZING https://github.com/ajroetker/go-highway

2026-02-13T19:58:03+00:00

FUCK THIS IS SO AMAZING
https://github.com/ajroetker/go-highway

https://o16g.com/

2026-02-12T11:07:15+00:00

https://o16g.com/

https://jyn.dev/remotely-unlocking-an-encrypted-hard-disk > The takeaway here is the same as in a

2026-01-31T08:59:26+00:00

https://jyn.dev/remotely-unlocking-an-encrypted-hard-disk
> The takeaway here is the same as in all my other posts: if you think something isn't possible to do with a computer, have you considered applying more violence?

https://youtu.be/PBVMYjh0wmc

2026-01-28T12:48:33+00:00

https://youtu.be/PBVMYjh0wmc

https://lorentz.app/blog-item.html?id=go-shebang

2026-01-10T18:05:41+00:00

https://lorentz.app/blog-item.html?id=go-shebang

https://antonz.org/accepted/modernized-go-fix/

2026-01-04T21:51:07+00:00

https://antonz.org/accepted/modernized-go-fix/

if you are interested in difference between bitmap and index scans in your explain plan https://www.

2026-01-04T14:05:44+00:00

if you are interested in difference between bitmap and index scans in your explain plan
https://www.crunchydata.com/blog/postgres-scan-types-in-explain-plans

https://hashrocket.com/blog/posts/postgresql-18-temporal-constraints

2025-11-15T21:24:03+00:00

https://hashrocket.com/blog/posts/postgresql-18-temporal-constraints

https://internals-for-interns.com/posts/sql-query-roadtrip-in-postgres/

2025-11-09T22:46:37+00:00

https://internals-for-interns.com/posts/sql-query-roadtrip-in-postgres/

https://sazak.io/articles/visual-guide-to-go-maps-hash-tables-2025-10-26

2025-11-08T11:03:25+00:00

https://sazak.io/articles/visual-guide-to-go-maps-hash-tables-2025-10-26

https://blog.cloudflare.com/how-we-found-a-bug-in-gos-arm64-compiler/

2025-10-25T12:12:47+00:00

https://blog.cloudflare.com/how-we-found-a-bug-in-gos-arm64-compiler/

> Thinking in terms of legibility and illegibility explains so many of the things that are confus

2025-10-16T07:15:17+00:00

> Thinking in terms of legibility and illegibility explains so many of the things that are confusing about large software companies.

В таких текстах начинаю лучше понимать своего прошлого работодателя.

Seeing like a software company

streaming some homelabbing https://www.twitch.tv/fira42073

2025-10-02T21:00:52+00:00

streaming some homelabbing
https://www.twitch.tv/fira42073

If anyone wants to take over this channel, lemme know. My life has given me a new vector of motion,

2025-08-29T22:41:10+00:00

If anyone wants to take over this channel, lemme know. My life has given me a new vector of motion, and I don't think I'm gonna come back to this channel, or for that matter telegram. The resources and rss feed are still relevant

Feel free to propose posts etc. C:

2025-08-19T13:02:59+00:00

Feel free to propose posts etc. C:

2025-08-19T13:02:21+00:00

https://tech.instacart.com/how-instacart-built-a-modern-search-infrastructure-on-postgres-c528fa601d

2025-08-17T04:42:01+00:00

https://tech.instacart.com/how-instacart-built-a-modern-search-infrastructure-on-postgres-c528fa601d54

Recently I ran into a weird issue. I ran git rebase -i HEAD~~ on my branch to edit the last two com

2025-08-16T15:22:01+00:00

Recently I ran into a weird issue.

I ran git rebase -i HEAD~~ on my branch to edit the last two commits. Before rebasing, my git log looked like this (most recent commit first):


    
        commit A1B2C3D4  (HEAD -> branch)
Author: someone
Date: ...
    Commit message 1

commit E5F6G7H8  (merge commit)
Author: someone
Date: ...
    Merge branch 'feature' into 'branch'

commit I9J0K1L2
Author: someone
Date: ...
    Commit message 2{}

When I ran the interactive rebase, I saw only two commits in the todo list: the commit from the merged branch (I9J0K1L2) and the latest commit (A1B2C3D4). I decided to drop the latest commit by marking it with d, expecting only that commit to disappear. But after the rebase, both the latest commit and the merge commit disappeared from history.

You might ask yourself, why the fuck did dropping one commit during git rebase -i HEAD~~ delete two commits, including the merge commit?

---

This happens because of how Git handles merges during interactive rebases, especially when you specify HEAD~~ (two commits behind HEAD).

* HEAD~~ means you want to rebase starting two commits before the current HEAD.
* However, merge commits are not replayed as merges by default during a rebase; Git flattens the history.
* So, when your second commit is a merge commit, Git effectively skips showing the merge itself in the rebase todo list.
* Instead, it shows the commits *inside* the merge and the most recent commit.
* In your case, the interactive rebase todo list showed only two commits:
1. The commit that was originally part of the merged branch
2. The latest commit you wanted to drop
* By marking the latest commit with d (drop), you told Git to exclude that commit during the rebase.
* Since the merge commit isn’t replayed as a merge but flattened into those two commits, dropping the latest commit effectively lost the merge commit as well.
* The end result was your history jumped from the commit before the merge directly to the commit inside the merged branch, skipping both the merge commit and your dropped commit.

To avoid this:

* Use --rebase-merges or just -r to preserve merge commits during rebasing like git rebase -i --rebase-merges HEAD~~. This shows merges explicitly and lets you manipulate them.
* Or, if you only want to remove the latest commit, a simpler way is to reset the branch with git reset --hard HEAD~1 instead of rebasing.

---

This issue often surprises people because merges get “flattened” by default, so the interactive rebase doesn’t show them as separate commits, and dropping one commit can make it feel like multiple commits vanish unexpectedly.

An article on this:

https://mtyurt.net/post/2019/git-rebase-merges-option.html

btw this thingy is mostly generated by an llm, I did not have patience to write this, just fyi

https://mayallo.com/lateral-join/

2025-08-16T04:40:10+00:00

https://mayallo.com/lateral-join/

https://stormatics.tech/blogs/when-postgresql-performance-slows-down-here-is-where-to-look-first

2025-08-15T04:34:01+00:00

https://stormatics.tech/blogs/when-postgresql-performance-slows-down-here-is-where-to-look-first

https://www.jvt.me/posts/2025/01/27/go-tools-124/

2025-08-14T15:39:01+00:00

https://www.jvt.me/posts/2025/01/27/go-tools-124/

https://kmoppel.github.io/2025-08-06-no-you-dont-need-extensions-to-compact-postgres-tables/

2025-08-14T04:32:01+00:00

https://kmoppel.github.io/2025-08-06-no-you-dont-need-extensions-to-compact-postgres-tables/

let's gooooo (you can update, already, yeah) https://go.dev/doc/go1.25 https://go.dev/doc/inst

2025-08-13T10:11:08+00:00

let's gooooo (you can update, already, yeah)

https://go.dev/doc/go1.25
https://go.dev/doc/install

https://victoriametrics.com/blog/go-time-monotonic-wall-clock/

2025-08-13T04:08:01+00:00

https://victoriametrics.com/blog/go-time-monotonic-wall-clock/

https://antonz.org/go-concurrency/signaling/

2025-08-12T04:46:01+00:00

https://antonz.org/go-concurrency/signaling/

https://antonz.org/go-concurrency/semaphores/

2025-08-11T04:46:02+00:00

https://antonz.org/go-concurrency/semaphores/

https://antonz.org/go-concurrency/race-conditions/

2025-08-10T04:46:01+00:00

https://antonz.org/go-concurrency/race-conditions/

https://antonz.org/go-concurrency/data-races/

2025-08-09T04:46:01+00:00

https://antonz.org/go-concurrency/data-races/

upgrade me, Məzahir https://severalnines.com/blog/migration-and-upgrades-achieving-near-zero-downti

2025-08-08T04:24:01+00:00

upgrade me, Məzahir

https://severalnines.com/blog/migration-and-upgrades-achieving-near-zero-downtime-in-postgresql/

Important considerations about security of your database https://neon.com/blog/postgres-needs-bette

2025-08-07T04:18:01+00:00

Important considerations about security of your database

https://neon.com/blog/postgres-needs-better-connection-security-defaults

From galera to cern, always yours - postgresql https://www.tigerdata.com/blog/how-cern-powers-groun

2025-08-06T04:22:01+00:00

From galera to cern, always yours - postgresql

https://www.tigerdata.com/blog/how-cern-powers-ground-breaking-physics-with-timescaledb

You asked, I'm providing https://antonz.org/go-1-25/

2025-08-05T05:31:01+00:00

You asked, I'm providing

https://antonz.org/go-1-25/

2025-08-04T06:22:06+00:00

2025-08-02T22:42:15+00:00

This is so fucking sexy!! https://pgdog.dev/blog/sharding-postgres-at-network-speed

2025-08-02T04:06:01+00:00

This is so fucking sexy!!

https://pgdog.dev/blog/sharding-postgres-at-network-speed

https://github.com/frectonz/pg-when

2025-08-01T15:50:17+00:00

https://github.com/frectonz/pg-when

https://gavinray97.github.io/blog/postgres-sql-property-graphs

2025-08-01T04:38:01+00:00

https://gavinray97.github.io/blog/postgres-sql-property-graphs

https://www.cybertec-postgresql.com/en/who-are-the-pgdg/

2025-07-31T04:37:01+00:00

https://www.cybertec-postgresql.com/en/who-are-the-pgdg/

https://matrix.org/blog/2025/07/postgres-corruption-postmortem/

2025-07-30T04:34:01+00:00

https://matrix.org/blog/2025/07/postgres-corruption-postmortem/

This is fucking crazy cool https://www.rudderstack.com/blog/scaling-postgres-queue/ Prerequisites,

2025-07-29T04:57:01+00:00

This is fucking crazy cool

https://www.rudderstack.com/blog/scaling-postgres-queue/

Prerequisites, if you're not familiar with postgres "internals" that much
yesterday's https://www.cybertec-postgresql.com/en/making-the-postgresql-visibility-map-visible/
and previously mentioned
https://www.cybertec-postgresql.com/en/speeding-up-things-with-hint-bits
https://www.cybertec-postgresql.com/en/loading-data-in-the-most-efficient-way/

Have fun!!

https://byteofdev.com/posts/making-postgres-slow/

2025-07-28T16:06:01+00:00

https://byteofdev.com/posts/making-postgres-slow/

https://www.cybertec-postgresql.com/en/making-the-postgresql-visibility-map-visible/

2025-07-28T05:40:15+00:00

https://www.cybertec-postgresql.com/en/making-the-postgresql-visibility-map-visible/

https://www.rudderstack.com/blog/kafka-vs-postgresql-implementing-our-queueing-system-using-postgres

2025-07-27T05:36:01+00:00

https://www.rudderstack.com/blog/kafka-vs-postgresql-implementing-our-queueing-system-using-postgresql/