I'd be wary about 4. I've worked at a fintech startup before where the founders boasted about how they had moved all their net worth onto the platform. Some time later over a casual chat and drinks, it turned out this was far from the truth. Don't just take people's word for it, I may be biased about startups now, but "trust but verify" is a good motto to go by.
Just to answer some questions I'm seeing from other comments, this is built with three.js. Think of it as a 3d scene with an image rendered on a 2d plane and the camera has certain gaussian blur applied to a section of it. He's using orbit controls for the zoom in/out and for the ability to pivot the image.
Tangent but "Your margin is my opportunity" was originally a Sam Walton quote when he was building the 5 and dime stores. Bezos was deeply inspired by early Walmart and Sam.
That's interesting -- the quote is very much attributed to Bezos. Did the quote actually come from Sam Walton, or merely the sentiment? Either way, it's clear that the Waltons were an inspiration to Bezos!
Interesting perspective, disagree on one central tenant. Even though Github holds production code, it is not production. Built artifacts and the machines running those artifacts is production. When Github goes down, which it rarely does, it just means developers cant sync for a couple hours, no different than if someone works offline. The temptation to increase internal devops complexity should not be an automatic immune response when a service goes down, it comes with all sorts of hidden costs.
Also something that irks me is that all these platforms design DAGs as journeys. Journeys are fine but they're inherently value capped. A user is only supposed to go through an onboarding journey once or a memorial day sale journey once.
What I really want as a mobile app dev is loops. I want to be able to say "Run this every day, send a user a push or email at 10am. wait until 6pm. if the user hasnt opened the app yet, send another push based on a different template".
Currently we have a whole ass subproject dedicated to defining these flows. whats worse is that its hard to ab test flow and impossible for anyone non technical to set up a loop. Please build this, we'll pay you sweet sweet MRR if you do.
Our plan is to model loops by having journeys define re-entry conditions, allowing users to run through journeys multiple times on a schedule. Would love to talk, to learn more about y'all are doing.
My email is: max@dittofeed.com, or feel free to ping me on our community slack!
Some people are annoyed with the way Docker (the company) has tried to monetize the technology by revoking free repos from open-source teams. If I recall, Docker doubled back on that.
