jelder

7 ms·

31.
by jelder 11mo ago
Underrated point. Looking for performance issues on a machine with different baseline IO and CPU load, buffer state, query plans, cardinality, etc. is just theater and will lead to a false sense of security. RegreSQL is approaching a statef
32.
by jelder 11mo ago
Using the right language for the problem domain is a good thing, but what I can't stand is when people self-identify as the one language they are proficient in. Like, "I'm Staff JavaScript developer" no buddy, you aren&#
33.
by jelder 11mo ago
My recollection is that this happened pretty much immediately after Twitter became X.
34.
by jelder 11mo ago
That would be equivalent to demonetizing the entire web. Free content would win out over paid content regardless of quality. As the old adage goes, "when you're getting something for free, you're the product being sold."
35.
by jelder 1y ago
You updated _production_ before _testing_? Sorry but that just sounds like asking for a disaster.
36.
by jelder 1y ago
> On GitHub Actions, we’re planning to use uv to quickly build a Python environment and run our unit tests. In production, uv already manages Python for all of our servers. Does that mean they aren't running unit tests _at all_ in C
37.
by jelder 1y ago
No, that's pretty rare, and generally means you can't count on any features more sophisticated than VMs and object storage. On the other hand, it's pretty embarrassing at this point for something as fundamental as Docker to b
38.
by jelder 1y ago
I really appreciate that they bothered to set an artificial timestamp for these git commits, roughly 30 years before Git itself existed. The thing is, the other files do, too, and the .gitignore is full of hilariously anachronistic referenc
39.
by jelder 1y ago
What it actually looks like: https://fonts.google.com/specimen/B612
40.
by jelder 1y ago
“Viable?” It’s been in production for almost twenty years at one of the most profitable companies on the planet. I think it’s viable.
41.
by jelder 1y ago
I have been building web apps for long enough to remember when it was commonplace to SSH (or Telnet!) into the server and just vim index.php. As you can imagine, it was pretty easy to bring the site down like that, so we started doing what
42.
by jelder 1y ago
Linux supports two different in-memory filesystems, ramfs and tmpfs. It should be easy enough to set up tests to use paths on such a mount point. Wonder why OP didn't mention these.
43.
by jelder 1y ago
What others do you know of?
44.
by jelder 1y ago
Except, no it doesn’t. In the case of a pull request, I am not about to trust some LLM that has no business context and can only pretend to guess at the “why” of a change. To understand the “what” of a change, you have to actually read the
45.
by jelder 1y ago
Whenever I see a README or worse, PR description that was obviously generated by an LLM, my immediate response is "if you couldn't be bothered to write this, why should I bother reading this?"
46.
by jelder 1y ago
Did I miss in the article where OP reveals the magic database that actually does this? 3rd party solutions like https://readyset.io/ and https://materialize.com/ exist specifically because databases don’t a
47.
by jelder 1y ago
Strongly agree! Rust’s sqlx is also insanely great, and I like sqlc for Go as well. I’ve written a lot about this particular topic: https://www.jacobelder.com/2025/01/31/where-shift-left-fails...
48.
by jelder 1y ago
I grew up in a Tercel family, and we too had a “parts car” in the back yard. Reliable, safe, repairable car the likes of which simply don’t exist anymore.
49.
by jelder 1y ago
Well, good, because these things make bad friends and worse therapists.
50.
by jelder 1y ago
100% this. I’ve been doing this for a long time and have never once “shared code between front end and back end” but sharing types between languages is the sweet spot.
51.
by jelder 1y ago
Worse punishments for bribery. Higher rewards and lower risks for reporting bribery. Whistleblower protections. Government isn't the problem here, it's the victim.
52.
by jelder 1y ago
Worst possible take. The government sucks _because_ of decades of slip into corporate control and manufactured consent.
53.
by jelder 1y ago
"Nightly?" Iteration speed can never be faster than the testing cycle. Unless you're building something massive (like Windows or Oracle maybe) nobody is relying on "nightly" integration tests anymore.
54.
by jelder 1y ago
Preference for typed languages may be the one and only good thing to come out of this bubble.
55.
by jelder 1y ago
The best Slack culture I ever saw also had a strict “No DMs” policy. All discussions had to take place in public or semi-public channels. DMs were reserved for “hey you’re missing standup” or similarly trivial stuff.
56.
by jelder 1y ago
> doing anything that starts gravitating the knowledge toward a person instead of a topic creates problems for discoverability, searchability Channels aren’t searchable. Messages are. > risks creating the impression (for new employees
57.
by jelder 1y ago
I use something similar, but call them “Rubber-duck channels.” http://www.jacobelder.com/2025/02/25/habits-and-tools-effect...
58.
by jelder 1y ago
This is written for the Linux-on-the-Desktop crowd, and good for them. But tmux really shines for folks using MacBooks with iTerm2. Its tmux integration is so good that it simply disappears into my workflow. With this in my `~/.ssh&#x2
59.
by jelder 1y ago
I frequently reach for IIFE when I use switch/case. It's a very convenient (if maybe a bit weird looking) way of turning a statement into an expression. In other words, `return 1` instead of `foo = 1; break` for a trivial example.
60.
by jelder 1y ago
This is an excellent point about pipes. There seems to be no other language which lets you stitch together pipes like Bash does. It's incredibly powerful, and worth putting up with all of Bash's warts. Thanks for fzf, by the way.

More ›