It's great to see this blog post get published. Evan is one of the most creative engineers I've gotten to work with.
Go's structural interfaces are often harped on, but this is exactly a case where they are very useful. Perhaps an approach is to use named interfaces for variance in implementation strategy, and structural directives for usages as described in the blog post. I wouldn't discount how often this pattern comes up.
It's interesting to me that the article title names a "San Francisco tech firm" rather than "Stripe". I guess though it may be a ubiquitous name in the YC community, Stripe is not a household name.
I recently finished my what I thought to be my first non-trivial programming class, and found this project to be a great opportunity to explore and apply the design patterns I learned in the course. As a result, the project is meant to be more academic and explorative in nature, but is somewhat useful.
Check it out, and please let me know of any constructive criticism or improvements!
Go's structural interfaces are often harped on, but this is exactly a case where they are very useful. Perhaps an approach is to use named interfaces for variance in implementation strategy, and structural directives for usages as described in the blog post. I wouldn't discount how often this pattern comes up.