wvanbergen

7 ms·

1.
by wvanbergen 2mo ago
Sounds like a similar setup to GAIA on Galiano Island in BC, described here: https://www.galianonet.org/about
2.
by wvanbergen 7y ago
> 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 to the amount of changes we need to ship. If you re
3.
by wvanbergen 7y ago
> 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 checks in the queue prevent things that branch-based CI c
4.
by wvanbergen 7y ago
Generally our metrics and exception reports are tagged with the sha and the deploy stage.
5.
by wvanbergen 7y ago
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.
by wvanbergen 7y ago
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 targeted properly (not doing this would be a major UX pain). How
7.
by wvanbergen 7y ago
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 often enough for us to want to prevent this. The simple way
8.
by wvanbergen 9y ago
Start by reading this: http://wiki.c2.com/?WhyIsPayrollHard
9.
Bootsnap: Boot large ruby/rails apps faster(github.com)
6 points by wvanbergen 9y ago|0 comments
10.
by wvanbergen 12y ago
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 cannot upvote this enough. The difference in how immigrated is
11.
Docker at Shopify: How we built containers that power over 100,000 online shops(shopify.com)
10 points by wvanbergen 12y ago|0 comments
12.
The value of a pure Ruby library(chunkypng.com)
1 points by wvanbergen 12y ago|0 comments
13.
by wvanbergen 12y ago
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: https://gist.github.com/kristianpd/f4
14.
by wvanbergen 12y ago
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.
by wvanbergen 12y ago
fidz: should be fixed now. Thanks for reporting this.
16.
by wvanbergen 12y ago
Ah, this is a bug in our redirect system. I will look into it.
17.
by wvanbergen 12y ago
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 many applications. Email me at willem at shopify dot com
18.
by wvanbergen 12y ago
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 container build. Secondly: easier scalability, because we can
19.
Shopify's Kafka producer pipeline for Ruby on Rails(shopify.com)
21 points by wvanbergen 12y ago|3 comments
20.
Your App Pricing is Wrong(shopify.com)
3 points by wvanbergen 14y ago|0 comments
21.
Analyst, measure thyself(blog.noblemail.ca)
46 points by wvanbergen 14y ago|4 comments
22.
RESTful thinking considered harmful - followup(shopify.com)
15 points by wvanbergen 14y ago|2 comments
23.
by wvanbergen 14y ago
Textmate.
24.
by wvanbergen 14y ago
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.
by wvanbergen 14y ago
Must have disappeared when I transferred the article. Fixed, and thanks for reporting.
26.
by wvanbergen 14y ago
Thanks, will fix.
27.
by wvanbergen 15y ago
My post isn't meant as a description about state machines; I point to wikipedia for that. The Ruby gem also gives a very nice introduction indeed. However, the point I try to make is very much about state machines, because modelling state u
28.
by wvanbergen 15y ago
Indeed. If you do not use a state machine in a situation like that, you either get very complicated code as well, or you conveniently do not implement some of the state transitions. That will always get back to you: "how can this ever happe
29.
by wvanbergen 16y ago
My favorite issue in 1.9.2: "." is no longer included on the $LOAD_PATH.