1,552 karma · joined August 6, 2011
https://getfriendlyreminder.com https://clintonblackburn.com https://dev.clintonblackburn.com
Stripe has dabbled in Golang. There is also a growing Java monorepo.
PCI-related/vaulting code lived in its own locked-down repo. I think that was a mix of Go and Ruby.
Once you have the foundations in place for account balances and the ledger, processing a payment isn’t that daunting. Those foundations, however, took a lot to build and evolve.
Refreshing the content on an electronic shelf label (ESL) takes about 30 seconds, and multiple people can view a product simultaneously. Unless the store is giving everyone AR glasses, people will notice the price discrepancy.
This assumes you have sufficient data to actually recognize a shopper such as facial ID or some form of iBeacon for every single product for which you wish to implement price discrimination. Basic ESLs cost $3 to $12, depending on size and use very little energy. Adding a camera means more energy, so a bigger battery and more cost.
Using in-app discounts is the most likely way to implement this, which I am okay with. Shoppers are willingly trading their data privacy for a discount.
The bill in question is about per-shopper pricing (e.g, you and I pay different prices in the same store). This is something Lyft and Uber do, but it's not really possible in retail.
I flew Spirit a few times. The first time sucked because it was an emergency and I had no other option. The last few flights were great. We got the large seats up front for $75 extra. That plus parking at SJC was still cheaper than flying Southwest out of OAK.
The staff were friendly, and the gate was conveniently across from a lounge, so we had a truly great experience for those couple flights to Dallas.
This has been a godsend over the past week while deploying a couple services. One is a bridge between Linear and our Coder.com installation so folks can assign the work to an agent. Claude Code can do most of the work while I sleep since it has access to kubectl, Linear MCP, and Coder MCP. I no longer have to manually build, deploy, test, repeat. It just does it all for me!
My company is currently trying to rollout shared MCPs and skills throughout the company. The engineers who have been using AI tools for the past 1-2 years have few, if any, issues. The designers, product managers, and others have numerous issues.
Having a single MCP gateway with very clear instructions for connecting to Claude Desktop and authenticating with Google eliminates numerous problems that would arise from installing and authenticating a CLI.
The MCP is also available on mobile devices. I can jot down ideas and interact with real data with Claude iOS and the remote MCP. Can’t do that with a CLI.
I'm happy for competition, but this seems a bit foul since we users aren't getting anything tangible beyond the promise of improvements and investments that I don't need.
You don’t need to listen for all event types if you aren’t using _every_ Stripe feature.
Can I “just call the API”? Yeah, but that takes extra work, and my goal is to reduce extra work.
Is a collision possible? Yes, but the likelihood of a collision is so low that it's not worth agonizing over (although I did when I was designing the system).
When I was a kid we had Book It. I got a free personal pan pizza from Pizza Hut for every 10(?) books I read. I read a lot of books! I also learned a lot along the way, and continued the habit of reading for fun through college.
- DataGrip sporadically stops working when returning from sleep. I have to force-kill it to continue.
- Take a relatively empty file with 10 lines. WebStorm is supposed to reformat on save. It hangs for 10+ seconds or until I cancel reformatting.
- I saw a low memory alert for the first time in months this week. My workflow hasn't changed drastically and I wasn't running anything, just editing a few files.
- Overall everything feels a little slower than it did a couple weeks ago with the older version.
I don't think it's worth filing issues in YouTrack because I've seen those go nowhere in the past.
This means, yes, when validating access, you must load the data you want to access and compare its attributes against the user's authorization. One advantage of doing this is that the system can either return a 404 if the object belongs to a completely different domain, or, if the object belongs to a sub-domain, return a 403 and sufficient data to power a request for temporary privilege escalation.
I'm open to ideas for improving this.