Live data from Hacker News

Viewing profile — blakehaswell

blakehaswell

HN member
Joined
Thu, Nov 28, 2013, 9:00 AM UTC
HN karma
154
Public activity
51 items

About blakehaswell

No profile information was provided.

Recent public activity

  1. comment
    Comment #44666375

    One thing that might not be obvious about checklists is how they're used. I used to think checklists were used by reading the item, then doing the thing. I literally thought of the…

  2. comment
    Comment #33539905

    I feel for everyone working there who is suffering whiplash from being pulled from one direction to the other. What can you possibly learn about a new feature in a few hours apart …

  3. comment
    Comment #33103621

    Yes, WIP (work on progress) limits are a key feature of Kanban.

  4. comment
    Comment #32933600

    Citation needed. Whether the server is serving HTML or JSON it still needs to serialise the data, so I don't think serialising JSON is going to be significantly faster than seriali…

  5. story
  6. comment
    Comment #30761261

    To clarify, are you saying up to two-dozen services for a development team with ~12 developers on it?

  7. comment
    Comment #30707279

    I really enjoyed this, I think looking the organisational structure through time is a good take that I haven't really seen addressed so clearly before. I would have liked to see an…

  8. comment
    Comment #30535809

    > did Facebook, Apple, Amazon, Netflix, Google, etc all make a terrible engineering mistake? Is that so impossible? There are many other considerations that go into technology choi…

  9. comment
    Comment #30002512

    What exactly do you mean by multiple entry points? Do you have multiple processes which run independently but are co-located in the same repository or are you talking about somethi…

  10. comment
    Comment #29222136

    > great speed in iterating new features […] makes our customers happy For me this is a leap. I can't think of many examples of software which I use where new features have actually…

  11. comment
    Comment #29007410

    Back in 2014 Spotify released some videos[1][2] about their engineering culture. From what I understand these were widely cited by consultants and the squad/tribe/chapter model was…

  12. comment
    Comment #28954480

    Not the person who asked, but I'm interested in the first two.

  13. comment
    Comment #28940073

    > Exactly what I did. After reaching top still somewhat technical position at the company I got so fed up and burned out that I quit. Went on my own and been this way ever since fo…

  14. story
  15. comment
    Comment #27034675

    At the end of the day our software is going to run on real machines, sending data across real networks. I feel like we'll always be leaving performance on the table if we don't und…

  16. comment
    Comment #27034654

    C++ provides programmer control over memory layout, which is something managed languages don't provide. So although C++ is an older language and it isn't designed for modern machin…

  17. comment
    Comment #26469809

    Me too. I was trying to browse HN on my phone earlier and my first instinct was that my WiFi was having a moment. It's a testament to how reliable HN is.

  18. comment
    Comment #26246810

    Given their previous post about technology choices[0], I'd say modern C++ is probably ticking most of those boxes for the author. [0]: http://rachelbythebay.com/w/2020/09/24/feedba…

  19. comment
    Comment #26246792

    I was thinking "modern C++" is potentially a good fit for avoiding most of these complaints (i.e. if you solely use smart pointers). Given their other post about technology choices…

  20. comment
    Comment #25996888

    > If you actually don't need it (i. e., your hot methods are never overridden), then the JIT will trivially compile those "virtual" method calls as non-virtual ones. But isn't that…

  21. comment
    Comment #25805924

    I agree. I don’t think lines of code is necessarily the right thing to budget, especially if you limit it to “lines of code written by our team”. But there is something interesting…

  22. comment
    Comment #25743134

    My concern with this is that it gives the "rain skeptics" a platform to spread their views, and presents "rain skeptics" as a legitimate alternative to the "rain scientists". The p…

  23. comment
    Comment #24927103

    I'm not sure that's such a huge problem. HTTP routing provides a wonderful architectural seam so that we can use different solutions for different domains like `/profile` and `/doc…

  24. comment
    Comment #24561810

    > to write off GraphQL or React as "cancerous" on account of someone having made a less than optimal decision in how to use them seems premature. Apologies, cancerous isn't how I'd…

  25. comment
    Comment #24561417

    > From a purist perspective, this has a "cancerous" feel (as opposed to being "encapsulated") I have the same feeling about much of the React ecosystem (edit: though I'd say "tight…