This problem is endemic in Stripe. I wanted to enable issuing on my account to test card issuing, but there was a bug where the ui was looping, not allowing me to sign up.
Asked support, got 2 weeks of "we're working on it"'... And finally a "You're using Opal, you can't enable issuing".
Twisp | Multiple Roles | USA | Full time | REMOTE | $160k-$220k + Equity + Sign On bonus Twisp is a team of fintech veterans (Simple, BBVA) working to build the next generation of financial data infrastructure for engineers.
The infrastructure we need to build and scale ledgers doesn't exist. With Twisp, developers can declare ledgers, reconciliation primitives, and financial calculation pipelines all via infrastructure-as-code, just like you would any other first class cloud resource.
We're a fully remote company with an affinity for the PNW. Pre-seed stage with $3M backed by top investors in our domain and a portfolio of fintech design partners with glowing reviews. We're looking for people eager to play a vital role in architecting and scaling developer-first financial tools that support money movement.
Twisp | Multiple Roles | USA | Full time | REMOTE | $160k-$220k + Equity + Sign On bonus
Twisp is a team of fintech veterans (Simple, BBVA) working to build the next generation of financial data infrastructure for engineers.
The infrastructure we need to build and scale ledgers doesn't exist. With Twisp, developers can declare ledgers, reconciliation primitives, and financial calculation pipelines all via infrastructure-as-code, just like you would any other first class cloud resource.
We're a fully remote company with an affinity for the PNW. Pre-seed stage with $3M backed by top investors in our domain and a portfolio of fintech design partners with glowing reviews. We're looking for people eager to play a vital role in architecting and scaling developer-first financial tools that support money movement.
Twisp | Multiple Roles | USA | Full time | REMOTE | $160k-$220k + Equity + Sign On bonus
Twisp is a team of fintech veterans (Simple, BBVA) working to build the next generation of financial data infrastructure for engineers.
The infrastructure we need to build and scale ledgers doesn't exist. With Twisp, developers can declare ledgers, reconciliation primitives, and financial calculation pipelines all via infrastructure-as-code, just like you would any other first class cloud resource.
We're a fully remote company with an affinity for the PNW. Pre-seed stage with $3M backed by top investors in our domain and a portfolio of fintech design partners with glowing reviews. We're looking for people eager to play a vital role in architecting and scaling developer-first financial tools that support money movement.
Twisp | Distributed Systems Engineer | Portland, OR | Full-Time | Remote | https://twisp.com
At Twisp, we’re a team of fintech veterans developing primitives to help engineers confidently build systems that handle financial transactions, balances, and insights at any scale. We’re a fully remote company with a mission to transform arcane financial protocols and complex ledger systems into simple, well-crafted developer experiences.
We’re fully funded and backed by top investors in our domain.
At Seamless circa 2010 we were asked to make the default sort order for restaurants appear by how close they were to the next tier of the contract. More orders = More Margin.
The tech team at the time was entirely located in Utah at the time, and all of us were repulsed at the idea. We countered with suggestions for improvement and made it clear the project would not be worked on:
- You can make a "promoted" restaurant section above the fold
- The UX concerns since users expect some reasonable ordering. Like distance from location or alphabetical.
We didn't get fired, and it was really scary. I appreciate standing up for ethics and principles. bravo.
This is the way. We've given multiple clients very similar stacks for "api layers" and it's by far the most cost effective way to do AWS from both productivity and opex point of view.
A fair question, and we’ve done it this way before at simple.com. When looking at the options for a pay-per use database, with global replication, streams and managed for you; We felt that if you could build a ledger on dynamo for these use cases, it’d be pretty compelling and fun.
Agreed. This is a limitation we ran into trying to implement a critical accounting ledger on top of DynamoDB. The transaction model we came up with is formally verified w/ TLA+. We're turning our work into a product: txlayer.com
I've been using about the same amount of time. Have you tried using python and bazel? Now there's some real weeping and gnashing of teeth ;) Lot's of bad code depending on python == python2 type of non-sense.
From the issues I've read on github, anecdotally, is that the approach of the gazelle and rules_go teams is to leverage the standard go tooling and not make changes to go itself.
Also anecdotally, bazel and golang work really well together IME. The community seems pretty active, and the upsides of using gazelle/bazel with golang seem to outweigh any downsides (though I'd be hard pressed to name a downside, that isn't inherit to golang itself).
Let's just look at one (expensive) idea proposed in the GND:
>Upgrading all existing buildings and building new ones so that they achieve maximum energy efficiency, water efficiency, safety, affordability, comfort, and durability.
How is a directive to upgrade all existing buildings, anything but central planning of an entire industry?
Asked support, got 2 weeks of "we're working on it"'... And finally a "You're using Opal, you can't enable issuing".
They're losing thread fast.