Live data from Hacker News

Viewing profile — henrikn

henrikn

HN member
Joined
Tue, Mar 04, 2014, 8:18 PM UTC
HN karma
3
Public activity
10 items

About henrikn

No profile information was provided.

Recent public activity

  1. comment
    Comment #47748271

    Recipe and accompanying video here: https://www.tastinghistory.com/recipes/switchel Tried making it. Certainly interesting! But not something I’ll make again.

  2. comment
    Comment #47731253

    I was going on a train journey, wanted something to read and wondered if there was anything with the premise "someone secretly invented Claude Code before LLMs were a thing and use…

  3. story
  4. comment
    Comment #39536072

    Speaking of random third-party JS code, do you know of anything supporting this is actually being run by Fastly, other than it being in the domain name? I did some minor sleuthing …

  5. comment
    Comment #25067743

    Agreed, this can be difficult. An approach like BEM can help somewhat because you rely less on cascading. But then again, because it's tediously explicit, one may generate BEM clas…

  6. comment
    Comment #25067725

    Hi! Blog post author here. I agree that tests are super valuable for many things, but it isn't enough here – at least not with the way my team writes tests. (Our) tests wouldn't ca…

  7. comment
    Comment #12041513

    Another option is to do away with blocking on pull requests altogether and review after the fact. It has some benefits (and some downsides). I blogged about that here: http://thepu…

  8. comment
    Comment #7348969

    Wrong: I'm sure it is. I did it without tests and didn't go through the logic carefully since that wasn't at all the point. The design was. Performance: could be. If your context i…

  9. comment
    Comment #7343067

    Also glanced at the load_from_v1 code. I can't argue with the "deprecated code" bit – if you never need to understand or edit that code again, by all means leave it. There will be …

  10. comment
    Comment #7342930

    > They're wrong: it's the smallest it can possibly be while still correctly performing the necessary goal; any smaller, and you have to break it into multiple smaller methods that …