jelder

This sounds an awful lot like https://en.wikipedia.org/wiki/Company_scrip, which has been illegal for a long time and for good reason.

This is not bad luck. It’s a structure.

Either AI wrote this, or the author thinks this is what humans sound like now.

Pour one out for anyone who hoped to start a new brand.

Is laser printing more feasible? I've had the same Brother black & white laser for almost a decade and it's more than adequate for everything I do. If I ever need color, I send it off to a service that has much nicer printers than most people would ever want in their homes.

Untrue since the introduction of zstd support in PostgreSQL 15.

If you encountered a cheetah in pre-industrial times (and survived the meeting), you might think it was impossible for anything to go faster.

Fun fact, there is no historical evidence of an adult human ever dying from a cheetah attack. They are naturally shy, and a lot smaller than you may realize.

LSPs are already miles better than grep-like tools. This was true for humans as much as it is for LLMs. It's a shame that Claude still treats it as a second-class citizen (both in the app itself and in the training). A simple "remember to use LSP instead of grep" is usually enough to get it on the right track.

There's a huge difference between a program which can be verified as correct by static analysis, and a program which can only be verified as correct by running it. Python is the latter (though maybe in between with gradual typing). The iteration loop just collapses when an agent is driving an LSP in a statically typed language.

Who goes out of their way to “star” a GitHub repo, and what does that even mean? Is it a “like” button, a tip jar, or a bookmark? Does this bare any relationship to the importance, quality, novelty, trustworthiness, or any other property of the repo other than number of stars?

What a dumb metric to focus on.

We did this with MotherDuck, and without introducing a new language. Every tenant has their own isolated storage and compute, so it’s trivial to grant internal users access to specific tenants as needed. DuckDB’s SQL dialect is mostly just Postgres’ with some nice ergonomic additions and a host of extra functionality.

It would be a shame if somebody modified this to trigger Bluetooth and Wi-Fi deauthentication attacks.

DuckDB had the right idea: just allow some flexibility in the relative order of the `select` and `from` clauses, and make a few other concessions for ergonomics. This then becomes valid:

    from events      -- table is first, which enables autocomplete
    select
        count(),     -- * is implied, easier to type
        customer_id, -- trailing commas allowed everywhere
    group by all     -- automatically groups by all non-aggregate columns
    order by all     -- orders rows by all columns in selected order

You can't trust a product that uses ads, because then you are the product.

If you were to rank all of the C compilers in the world and then rank all of the welfare systems in the world, this vibe-coded mess would be at approximately the same rank as the American welfare system. Especially if you extrapolate this narcissistic, hateful kleptocracy out a few more years.

Couldn't coding agents just run `tail -f *`?

Indie games don’t have a budget for playtesting, but they can probably swing a GA account.

I just today realized io_uring is meant to be read as "I.O.U. Ring" which perfectly describes how it works.

eTAXI is just one such solution

https://www.safran-group.com/videos/e-taxi-safran-unveils-it...

You’re already flying this route with a 300-seat plane where 80+ people in business class generate most of your profit. Give those passengers a supersonic plane, cut the flight time in half, and charge the same price.

What does that end up doing to the cost of a seat in coach?

Haven’t seen a loading progress spinner on a landing page in a while. The Ruby website now loads almost as slowly as Ruby on Rails boots up.

“Most people” is not even remotely accurate.

The necessity of using a JSON column was outside of my control, but Zod etc. are absolutely required, I think, in most projects. I wrote more about that here: https://www.jacobelder.com/2025/01/31/where-shift-left-fails...

That works for lookups but not for foreign key constraints.

I thought this was common practice, generated columns for JSON performance. I've even used this (although it was in Postgres) to maintain foreign key constraints where the key is buried in a JSON column. What we were doing was slightly cursed but it worked perfectly.

The purpose of software is to reduce the cost of change.

Of course “code” belongs here.

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 stateful problem as if it were stateless and deterministic. A linter like https://squawkhq.com is a good partial solution but only addresses DDL problems.

RegreSQL would be better served by focusing only on the aspects of correctness that tools like SQLx and sqlc fundamentally cannot address. This is a real need that too few tools try to address.

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't "Staff" anything if you only know one language.

My recollection is that this happened pretty much immediately after Twitter became X.

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." Only sites making money by, shall we say, "indirect" means would be able to survive. A search engine which prioritizes free content over paid would become nothing but a propaganda engine.

You updated _production_ before _testing_? Sorry but that just sounds like asking for a disaster.