Live data from Hacker News

Viewing profile — wvanbergen

wvanbergen

HN member
Joined
Mon, Jul 19, 2010, 2:27 PM UTC
HN karma
131
Public activity
29 items

About wvanbergen

No profile information was provided.

Recent public activity

  1. comment
    Comment #48870822

    Sounds like a similar setup to GAIA on Galiano Island in BC, described here: https://www.galianonet.org/about

  2. comment
    Comment #21589202

    > Being as we use different tools, we wouldn’t allow a pull to be merged if it wasn’t up-to-date with master which is similar but a different approach That wouldn't work for us due…

  3. comment
    Comment #21588659

    > I guess I’m not fully understanding how a queue prevents this. Since you don’t have a full picture of the state of master until something is merged from the queue, how do the CI …

  4. comment
    Comment #21587497

    Generally our metrics and exception reports are tagged with the sha and the deploy stage.

  5. comment
    Comment #21587469

    We generally require 2 reviewers, and no sign-off on deploys. For PCI-compliant code things work a bit differently, but tries to follow this as closely as possible.

  6. comment
    Comment #21587431

    A `develop` branch has several disadvantages. You will want to make your `develop` branch the default branch in git and on GitHub, to make sure pull requests automatically are targ…

  7. comment
    Comment #21586398

    The branches that are being merged are tested, also in the first version. However, different branches can conflict with each other, and break the master builds. This was happening …

  8. comment
    Comment #16596520

    Start by reading this: http://wiki.c2.com/?WhyIsPayrollHard

  9. story
  10. comment
    Comment #8686766

    As a Dutch immigrant to Canada and a Shopify employee, I can assure you that the Germany-Netherlands rivalry is alive and well at this side of the ocean :) All kidding aside, I can…

  11. story
  12. story
  13. comment
    Comment #8527751

    We actually evaluated other options as well, including Angular, but found them not the best solution for our problem. We documented our experiments and evaluations at the time here…

  14. comment
    Comment #8526951

    This. We ended up creating models for the exact same stuff in both Ruby and JS. Lots of code duplication, and losing client-side performance due to deserializing JSON all the time.…

  15. comment
    Comment #8526930

    fidz: should be fixed now. Thanks for reporting this.

  16. comment
    Comment #8526911

    Ah, this is a bug in our redirect system. I will look into it.

  17. comment
    Comment #8471017

    MattyMc: sure. Primarily: be yourself, show what you are passionate about, and be willing to adopt change. When applying: cover letter > resumé, and try to stand out because we get…

  18. comment
    Comment #8470586

    At Shopify, we have moved to Docker for deploying our main product. Primary advantages for us are faster deploys, because we can do part of the old deploy process as part of the co…

  19. story
  20. story
  21. story
  22. story
  23. comment
    Comment #3776129

    Textmate.

  24. comment
    Comment #3775999

    My point is not so much that REST is wrong, but that RESTful thinking can be harmful if it comes before thinking about the process you're supporting.

  25. comment
    Comment #3775986

    Must have disappeared when I transferred the article. Fixed, and thanks for reporting.