sgarland

8 ms·

151.
by sgarland 6mo ago
> It seems to me that infra management is inherently suited to declarative logic. I'm pragmatic enough to understand why SWEs with little infra experience might prefer an imperative approach, but I tend to think you should pick one
152.
by sgarland 6mo ago
Never heard of this before. In looking through docs, honestly it looks like Ansible, but for people who don’t know Ansible, and with way more footguns. The fact that you can import any existing Python library means you’re now relying on tho
153.
by sgarland 6mo ago
And don’t forget to quote your port assignments and version strings.
154.
by sgarland 6mo ago
This is the best example of Poe’s Law I’ve ever seen. Well done…?
155.
by sgarland 6mo ago
Years ago I had found his channel and liked it, and then some video (I don’t remember the title or even subject at this time) came up on a subject I happened to know quite a bit about. He got to some point in an explanation, bungled it, and
156.
by sgarland 6mo ago
It is, but everyone is entitled to beliefs. Anecdotally, I feel the same way. Everywhere I’ve been, there has always been a legacy monolith that was stable as a rock, with dozens of new microservices scattered around it in an attempt to exi
157.
by sgarland 6mo ago
We just piped the backups through pigz for compression; rapidgzip also exists for parallelized decompression (or any other compression algorithm you’d like to use, of course).
158.
by sgarland 6mo ago
I've used barman on somewhat large-ish DBs (30+ TB), and had no complaints with it. I am a DBRE, if that holds any weight.
159.
by sgarland 6mo ago
If it’s an incident, it’s usually manually run after review, with an audience. If it isn’t, it’s run as a script that goes through normal PR review.
160.
by sgarland 6mo ago
To be fair, to delete an RDS / Aurora DB, you have to either pass it a final snapshot identifier (which does not disappear with the DB), or tell it to skip the final snapshot. They give you every possible warning about what’s going to
161.
by sgarland 6mo ago
The article describes idempotency keys and then completely misses making them the PK. The example is already using UUIDv4 as a PK, so they’re clearly not optimizing for performance. If you’re using the first 32 characters of a SHA256 hash,
162.
by sgarland 6mo ago
I’m a DBRE. I spend a good portion of my day with a shell into one or more prod databases. The schema definitions in code are scattered between ORM model definitions, Alembic migrations, and Liquibase migrations, so the only reliable way I
163.
by sgarland 6mo ago
Generally I agree, though for lighter-weight stuff like personal config management, I’ve grown fond of chezmoi [0]. It has templating support, so I can do things like auto-detect if it’s a work machine or personal, and render the appropriat
164.
by sgarland 6mo ago
Yes, and I hate it so, so much, and frankly don’t get the appeal. You want one-click installation of hooks? Bundle a shell script called run_first.sh that symlinks the hooks into .git.
165.
by sgarland 6mo ago
Yep. Nothing I hate more than some trivial formatting error that could easily fix itself halting CI. I am all for consistent formatting and linting, I just think it should be silently handled without fuss.
166.
by sgarland 6mo ago
There’s almost certainly a way to make VS Code use --no-verify.
167.
by sgarland 6mo ago
I think parent was saying it’s a benefit, not the original purpose. If I store a FK to a table containing my company’s corporate address, that is a tremendous savings in storage (and memory pressure), and it also eliminates update anomalies
168.
by sgarland 6mo ago
That is a practical benefit, absolutely. A different way of looking at it is that you’re eliminating data anomalies (generally, update anomalies).
169.
by sgarland 6mo ago
THANK YOU. I was confused at the normalization example given, and had to think through it. (id, name, age) is already at 5NF, and the only one it doesn’t satisfy is 6NF.
170.
by sgarland 6mo ago
Upon re-reading the article, I must apologize - you’re correct, the native bloom extension doesn’t help here. I misread the constraints. With that, hopefully it doesn’t come across as insincere or groveling to say this is an extremely cool
171.
by sgarland 6mo ago
Unless your role is DB-specific, at which point people stare at you blankly as you’re raging about B+trees and sort buffers, and then ignore you when you tell them for the Nth time that they should refactor their schema.
172.
by sgarland 6mo ago
Wait until they find out that Postgres has native bloom filters [0]. 0: https://www.postgresql.org/docs/current/bloom.html
173.
by sgarland 6mo ago
> Imagine you need to add an index to a table with a few million rows. On a seeded database with 200 rows, the migration runs in milliseconds. Obviously. But on a branch with realistic data, it takes 40 seconds and needs CREATE INDEX CON
174.
by sgarland 6mo ago
Not that I ever had confidence in his technical knowledge, but it went to zero when he confidently asserted that there was no possible way a single server could handle the massive traffic some NextJS app he had made was serving. He then pos
175.
by sgarland 6mo ago
Did you mean to reply to someone else? This seems awfully defensive for a reply to parent’s comment.
176.
by sgarland 6mo ago
Unless I’ve missed something, Postgres doesn’t have automatic index creation, nor does it have JSON introspection to automatically convert it to a normalized schema (which is insane; I love it). It also doesn’t do any kind of sharding on it
177.
by sgarland 6mo ago
If you’re going to do something bizarre like this, then why store it as human-readable? If you have fixed-size fields as they do here, make your own serialization format. You’re still doing byte-offset seeks, but it’ll be much faster. At th
178.
by sgarland 6mo ago
They will learn eventually, and then they’ll get to write a blogpost describing something that any sysadmin or kernel dev could’ve told them. Win-win!
179.
by sgarland 6mo ago
> joining through a junction table for a single multi-valued data field I may be misunderstanding you, but to me it sounds like you're conflating domain modeling with schema modeling. If your domain is like most SaaS apps, then Phon
180.
by sgarland 6mo ago
> Your database disk usage by table report is going to be dominated by junction tables, foreign key constraints, and indexes, and all you're really buying with that disk space is academic satisfaction. FK constraints add a negligibl

More ›