Live data from Hacker News

Viewing profile — gregmfoster

gregmfoster

HN member
Joined
Fri, Jun 30, 2017, 10:40 AM UTC
HN karma
90
Public activity
49 items

About gregmfoster

No profile information was provided.

Recent public activity

  1. comment
    Comment #36792594

    Thanks for writing this up! I really enjoyed the comparison. My team is considering moving some of our data to elastisearch out of postgres, and this analysis helps confirm some of…

  2. comment
    Comment #36792567

    To me, the critical points here are: > PostgreSQL has a single master and multiple read replicas, Elasticsearch has horizontal scalability via sharding. > if you have a large data …

  3. comment
    Comment #36785472

    I love the idea of more book-focused social networks! Curious what the motivation here is to make it federated, instead of focusing on high-velocity user-focused product developmen…

  4. comment
    Comment #36785426

    I'm curious how much people prefer TUIs over editor-plugin-GUIs these days. I'm getting more and more persuaded by the plugin model personally - perhaps partly by how easy it is to…

  5. comment
    Comment #36785349

    I imagine this would be brutally hard for guitar - so often, my fingers are "touching" the correct strings, but not pushing down hard enough to trigger the note. Piano might be mor…

  6. comment
    Comment #36779534

    yeah, it's really interesting, I've seen this confusion before

  7. comment
    Comment #36779420

    Congrats on the launch! How are you thinking about building an open-source company vs a closed-source?

  8. comment
  9. comment
    Comment #36778909

    nah, not real, I was just being silly :)

  10. comment
    Comment #36778842

    I like adopting a merge queue as a forcing function to deal with flaky tests.

  11. comment
    Comment #36778786

    It's like a rebase queue, but with more ref-log, and less tree inversion. Pull queues counter-intuitively lean on force-push-with-lease sub-commands, whereas monorepo merge queues …

  12. comment
    Comment #36778746

    FWIW, graphite.dev's MQ supports GitHub Enterprise Server

  13. comment
    Comment #36777669

    If a merge queue is light and fast, all repos could benefit from having it enabled by default

  14. comment
    Comment #36775856

    Seeing 421 on our AWS amplify splash page as well

  15. comment
    Comment #36450301

    This comment seems off topic?

  16. comment
    Comment #36202307

    I wonder if folks can trade in dev kits for the first version when it's released next year. That was the case for me with the Apple TV dev kit.

  17. comment
    Comment #35817628

    We're seeing this from graphite.dev's API calls to GitHub

  18. story
    GitHub API slow this morning

    Looks like GitHub's site and API are performing slowly this morning. Doesn't appear to be down, but appears to be experiencing some trouble since around 9:30-10am

  19. comment
    Comment #31855783

    Sounds like have some really thoughtful opinions regarding code review tools! > "Being able to comment on character-level granularity is cool!" This is something that I really like…

  20. comment
    Comment #31249354

    Proud to be working with friends to improve the world of dev tools. There's a massive community of engineers on Slack who have been beyond generous with feedback, bug reports, and …

  21. comment
    Comment #30182528

    graphite.dev (alternative frontend to github code review) still up, it appears to be just their frontend.

  22. comment
    Comment #29567338

    Love to see the manually updated status page not updating

  23. comment
    Comment #29567220

    Down for us (graphite.dev) as well, running on us-west-2

  24. comment
    Comment #29421294

    Im a fan of keeping my git branches clean locally (only having a couple active branches) and aggressively deleting merged/abandoned ones, though I know that this can be contentious…

  25. comment
    Comment #29258025

    Thank you for the kind words!