sgarland

26 ms·

631.
by sgarland 1y ago
> read-only DML Technically DQL, if you want to be pedantic.
632.
by sgarland 1y ago
> dashes I am forever angry that LLMs have ruined em-dashes. They’re a wonderful part of punctuation.
633.
by sgarland 1y ago
Yup. I was flying SFO -> SEA last year to visit family after a work trip, and Alaska Air had a screaming deal on first class, so I bought it. So nice to just walk on, sit (in a decently comfortable seat!) down, and do whatever you want w
634.
by sgarland 1y ago
Me, because nearly every time I see it used, it’s for a trivial request or two that can easily be handled with stdlib. If you need it, sure, it’s great, but let’s not encourage pulling in 3rd party libs unnecessarily.
635.
by sgarland 1y ago
Same. It’s mostly because if I have a shell script, while I’ll add some comments for tricky bits if needed, and maybe a `-h` function, that’s about it. In Python, though, I use the language’s features to make it as readable and safe as poss
636.
by sgarland 1y ago
> no modules Ish. You can source whatever files you want, so if you split up your functions into logical directories / files, you can get modules (-ish). > no tests BATS [0]. [0]: https://github.com/bats-core&#x2F
637.
by sgarland 1y ago
I’m positive you know this already, but for anyone else, this section [0] of the lddecode project has a wonderful example of all the visible and non-visible portions of an analog video signal. The project as a whole is also utterly fascinat
638.
by sgarland 1y ago
/r/restofthefuckingowl
639.
by sgarland 1y ago
Maybe I don’t understand what you’re trying to do, but you can directly control how frequently commits occur. BEGIN INSERT … —- batch of N size COMMIT AND CHAIN INSERT …
640.
by sgarland 1y ago
> Ceph / Rook Not sure I follow here; why would I want Rook involved? I generally don’t want my orchestration layer - which is also consuming storage - to be involved with the management of said storage. > Virtualizing vs. bare-m
641.
by sgarland 1y ago
> Oh man, having a 25U rack sounds really fun. For certain definitions of the word “fun,” yes. I have a 35U (I don’t need that many slots, but at the time I did need it tall enough that my kids couldn’t reach the top, where I put the key
642.
by sgarland 1y ago
Conda is its own beast tbf. Not saying that Python packaging is perfect, but I struggle to imagine a package pulling in 200K files. What package is it?
643.
by sgarland 1y ago
> Just because everything else is bad, doesn't invalidate the idea that you should do better. I get this all the time at my job, when I recommend a team do something differently in their schema or queries: “do we have any examples o
644.
by sgarland 1y ago
> way too complicated for what they do Notably, this is subjective. I’ve had devs tell me that joins (in SQL) are too complicated, so they’d prefer to just duplicate data everywhere. I get that skill is a spectrum, but it’s getting to th
645.
by sgarland 1y ago
Agreed, though containers and K8s aren’t themselves to blame (though they make it easier to get worse results). Debian Slim is < 30 MB. Alpine, if you can live with musl, is 5 MB. The problem comes from people not understanding what cont
646.
by sgarland 1y ago
Depending on the physical distance, it can be much more than a few msec, as TFA discusses.
647.
by sgarland 1y ago
This. A million times this. Performance isn’t seen as sexy, for reasons I don’t understand. Devs will be agog about how McMaster-Carr manages to make a usable and incredibly fast site, but they don’t put that same energy back into their own
648.
by sgarland 1y ago
The Gang Learns About Fsync.
649.
by sgarland 1y ago
> You're up against millions of engineering hours in this space. Tangential, but the fact that many orgs choose to not use native DB features like foreign key constraints, saying that “they’ll handle it in application code,” has alw
650.
by sgarland 1y ago
Not Invented Here; the desire to always build your own rather than buy / borrow existing tools.
651.
by sgarland 1y ago
The problem, IMO, is that the trade-offs seem to always land on the side of “what ships faster.” That may well be the fault of PMs rather than SWEs, but either way, it doesn’t usually make for a sustainable product.
652.
by sgarland 1y ago
Does this do tone? That is the single largest feature of Grammarly’s Slack plugin that I absolutely loved, and if my work allowed it, I’d have it again.
653.
by sgarland 1y ago
Welcome to modern development, where no one gives a shit about binary size. It’s awful.
654.
by sgarland 1y ago
Agreed. What’s worse is when they confidently proclaim that they had to scale up N times “to handle the load,” but then a brief reading of of their schema and queries reveals that an RPi could probably handle it if they’d designed a better
655.
by sgarland 1y ago
> Of course, this is sometimes abused and taken to extremes in a microservices architecture where each service has their own database and you end up with nastiness like data duplication and distributed locking. Not to mention the difficu
656.
by sgarland 1y ago
FK Constraints on partitioned tables has been a solved problem for years for Postgres. MySQL still doesn’t support them, unfortunately. For sharding, Vitess kind of supports them; Citus fully supports them. You’re correct that they do impac
657.
by sgarland 1y ago
Postgres lets you write stored procedures out of the box in pgSQL, C, Tcl, Perl, and Python. There are also 3rd party extensions for most languages you might want, including Rust and JS. More broadly, not knowing how to write SQL is a very
658.
by sgarland 1y ago
Every ORM I’m aware of allows you to drop down to raw SQL. Write your stored procedure, store it in VCS, add it as a migration, and then call it. If you want to make it friendlier, wrap the call in a function in your language so you can add
659.
by sgarland 1y ago
Every company I’ve been at that relied on application code to handle referential integrity had orphaned rows, and incidents related to data errors or the absurd pipelines they had built to recreate what FK constraints and triggers already d
660.
by sgarland 1y ago
Disagree; these issues come up when people use more advanced features of DBs without having the requisite DB expertise on staff. I’ll give OP that Postgres’ docs do not mention this gotcha (and props to them for drilling down to source code

More ›