Live data from Hacker News

Viewing profile — nulltrace

nulltrace

HN member
Joined
Tue, Mar 10, 2026, 12:00 AM UTC
HN karma
86
Public activity
58 items

About nulltrace

No profile information was provided.

Recent public activity

  1. comment
    Comment #48986485

    I think your concrete treehouse counts too though. Add a shower and suddenly you need plumbing, drainage, the structure has to hold more weight. The overcomplicated part drags the …

  2. comment
    Comment #48838691

    That loop reads like a bug to anyone who hasn't memorized the wrapping rules. while (i-- > 0) on a signed index does the same thing.

  3. comment
  4. comment
  5. comment
    Comment #48317131

    The SKIP LOCKED pattern is fine until the worker count climbs. Then vacuum can't keep up. Dead tuples pile up, visibility map turns to swiss cheese. Queue table is tiny on disk but…

  6. comment
    Comment #48273229

    Compiler mode won't catch the `extern "C"` thing though. Both sides compile happily, link blows up on mangled names. What I do is just keep a throwaway .cpp in tests that #includes…

  7. comment
    Comment #48200897

    Being a generalist isn't easy.

  8. comment
  9. comment
    Comment #48030372

    Most IAM policies start as "whatever made the deploy pass." Need rds:CreateDBInstance? Fine, rds:* it is. Ship it. Months later that same role can wipe the cluster and nobody remem…

  10. comment
    Comment #48015971

    There's a GitHub issue for the freeze thing. Their security scanner passes the full dep list as CLI arguments, large monorepo on Linux and you blow past ARG_MAX. Spawn silently han…

  11. comment
    Comment #48002809

    designed, but never tested

  12. comment
    Comment #48002633

    We went through the same switch. Half our alerts had been firing for a while and nobody ever acted on them.

  13. comment
    Comment #47970151

    Firefox at least randomizes extension IDs per install. Chrome hands all of that to extension devs, basically a "your problem now".

  14. comment
    Comment #47969591

    Stale training data is part of it. But even a current model can't tell what setup.py is going to run on your box. Nothing actually inspects the package before it executes. You'd wa…

  15. comment
    Comment #47939773

    Common mistake is trusting the repo instead of the workflow. Then any workflow inherits the same cloud access.

  16. comment
    Comment #47928498

    Browsers already treat the same SVG differently depending on how you embed it. strips scripts and external resource loads. and inline don't. People test with img tags, looks fine, …

  17. comment
    Comment #47928143

    We added a preflight curl against registry.npmjs.org before the install step in CI. Not surprising they went down together.

  18. comment
    Comment #47883521

    Downtime is one thing. Silently reverting commits on your default branch is something else entirely.

  19. comment
    Comment #47856326

    Preview deploys are even worse. Every PR spins one up with the same env vars and nobody ever cleans them up. You rotate the key, redeploy prod, and there are still like 200 zombie …

  20. comment
    Comment #47841888

    Catching accidental drift is still worth a lot. It's basically the same idea as performance regression tests in CI, nobody writes those because they expect sabotage. It's for the b…

  21. comment
    Comment #47828674

    Right, metaclass is a ways off. But even without it, just the core reflection is going to save a ton of boilerplate. Half the template tricks I've written for message parsing were …

  22. comment
    Comment #47828584

    Rebalancing is what really kills you. A CAS loop on a flat list is pretty straightforward, you get it working and move on. But rotations? You've got threads mid-insert on nodes you…

  23. comment
    Comment #47800980

    Yeah pricing seems okay with batching. The 128MB memory cap per Durable Object is what I'd watch. A repo with a few thousand files and some history could hit that faster than you'd…

  24. comment
    Comment #47772538

    Fair, but from the user side it still hurts. Setting up an Ed25519 signing context used to be maybe ten lines. Now you're constructing OSSL_PARAM arrays, looking up providers by st…

  25. comment
    Comment #47758965

    Lockfiles help more than people realize. If you're pinned and not auto-updating deps, a package getting sold and backdoored won't hit you until you actually update. The scarier cas…