Live data from Hacker News

Viewing profile — kevin_nisbet

kevin_nisbet

HN member
Joined
Wed, Jan 30, 2013, 3:26 AM UTC
HN karma
1,601
Public activity
440 items

About kevin_nisbet

No profile information was provided.

Recent public activity

  1. comment
    Comment #49197961

    Sorry, I didn't mean to imply tariff's were the exclusive cause, just a reminder that an additional factor is large tax increases.

  2. comment
    Comment #49197592

    >It's basically, because everything else has gotten more expensive. Labor + fuel + wear and tear on equipment + raw materials. Don't forget taxes (tariffs) have also increased subs…

  3. comment
    Comment #49162108

    > The strict academic definition hasn’t followed the colloquial usage for a long time. Maybe ever: This is my understanding as well, and as I recall the results of the research wer…

  4. comment
    Comment #48929568

    2am in Ontario

  5. comment
    Comment #48916567

    Good ol proxy arp, also ~20 years ago I took out all cellular internet access in Canada. Luckily it was in the maintenance window and I acted pretty quick, so hopefully no one noti…

  6. comment
    Comment #48605522

    And even if there are new ETFs like this, will ETF customers bother to move at enough scale. It's like the old quote for buying IBM, no one get's fired for returning the benchmark,…

  7. comment
    Comment #48374574

    And to try and expand on why an index would include a waiting period in it's rules, my limited understanding is it's to give the public markets time to follow the company and revie…

  8. comment
    Comment #48332734

    I'm a little bit more on the fence with the work sample interviews having designed them and also interviewed through them. I've also done my fair share of "traditional" tech interv…

  9. comment
    Comment #48269110

    And the way they verify you are doing what you say you are doing is by asking you to provide evidence, which is usually pretty easy to demonstrate that a policy was followed once o…

  10. comment
    Comment #48202498

    Yup, I thought it was great. Although one concern I always had in the back of my mind was where is the line drawn. Such as if an adversary gains access to one of my orgs accounts a…

  11. comment
    Comment #48202447

    >That’s assuming your vendor was pentesting AWS systems. If you meant you hired a vendor to pentest your own systems on AWS, that’s of course a totally different matter. Sorry for …

  12. comment
    Comment #48202144

    Do they? The only anecdotal thing I've seen is we hired a vendor to do a pentest a few years ago, and they setup some stuff in an AWS account and that account got totally yeeted ou…

  13. comment
    Comment #48187163

    singleflight and sync.Once handle slightly different use cases. sync.Once - Run exactly once, only the first call is invoked. singleflight - Merge concurrent requests into one requ…

  14. comment
    Comment #48125142

    Sometimes it's mostly about taking an interest, reading or understand the legislation, and making a really good case and argument to the government. I don't think I can claim credi…

  15. comment
    Comment #48012553

    I'm not an expert on the baseband implementations, but I have the same impression as the parent, that in the 3GPP protocols the devices location can be requested and it's processed…

  16. comment
    Comment #48008862

    Absolutely, I just don't know that this can be achieved over the Diameter/SS7 network between carriers, which the report was alleging access to the RAC/TAI and Cell ID's. So if the…

  17. comment
    Comment #48008791

    Yup, sorry I didn't bring this side up because the article was mainly talking from the perspective of pulling the LAC/TAI from generating messages in the SS7/Diameter networks. If …

  18. comment
    Comment #48002976

    This was a fairly interesting read, but some of the claims struck me as fairly circumstantial. I ended up almost writing a novel of a comment, but will try and save everyone from t…

  19. comment
    Comment #47978337

    On this side of the equation I think you start pulling in customer context and risk analysis on the downside. What is the churn risk for operation at 99% vs 99.9% availability. If …

  20. comment
    Comment #47939303

    The tables in the link do a good job of outlining this, 11.9% while an interesting headline number, 11.9% increase over nothing is still basically nothing. However, with the tables…

  21. comment
    Comment #47936510

    My team has been using https://runs-on.com/ for AWS instance runners, had a few glitches but largely been great for using AWS instances for runners.

  22. comment
    Comment #47924811

    I've operated at companies using both models, and have observed similar reactions to suggestions of using the cloud. To me it's like anything else in engineering, are the costs, ri…

  23. comment
    Comment #47766145

    I really wanted to like JJ, it was handy for a few months when I used it. But for me in the end I reverted back to regular git. What triggered me to go back was I never got a reall…

  24. comment
    Comment #47755880

    Agreed, and this is where I think some more nuanced and conscious use of tech debt can be used when applicable. It might be OK to place some bets on an initiative or feature, but i…

  25. comment
    Comment #47752004

    I'm not commenting too much on the details of the article, but the premise does resonate with me. I would argue all the engineering teams I've been on do not spend enough time thin…