We've integrated posthog (cloud hosted) and have been using it for a few months now. It's got a rough edge or two but it's tight, integrated nicely with the codebase, and an order of magnitude cheaper than amplitude. I'd like a nicer sentry integration
Time spent with the team ebbs and flows depending on complexity of projects, where in the roadmap you are, seniority of the dev team, and more.
The agile manifesto was too abstract in it's original state, and folks who needed a rigid framework created capital A agile in order to adapt it to their cog in the machine role.
For my team of 6 in a ~20-25 person (remote) startup, we have a 30 minute dev meeting in the morning, and a 15 minute full team meeting where the agenda rotates daily around departments. I quite like it honestly, remote can be lonely and isolating otherwise.
Generally I think it's important to structure team responsibility around who ultimately needs to make the decision (although they need to consult others and get team buy-in). And hire people you trust to make the decisions. Then the meetings become about problem solving and getting through the work, rather than performance art and politics.
Here's our main problem with Stripe for what it's worth -
Stripe Subscriptions and Subscription Schedules are massively complicated and don't support our use case. Subscriptions support complex scenarios like proration and metered billing, but miss the mark on simple use cases.
All I want to do is ship products when people are charged, but I also want to move the next charge (or next several charges around) based on end user requests. This is accomplished in Stripe using their "trial" functionality - which is a hack because the Subscription isn't in "trial", the customer just wanted to move the next invoice. Putting the Subscription in "trial" screws up Stripe out of the box analytics because they don't get counted as active Subscriptions.
I'm not surprised you were driven to build your own Subscription platform, I wasn't around for the decision for us, but knowing what I know now, I probably would have built as well or looked at Chargebee or similar.
Is effectively what you're wanting to do "snooze" a subscription? Given that you can schedule subscriptions to start at a later date, maybe a better (albeit still hacky) way to handle that scenario might involve canceling the active subscription and scheduling a new one to start at a later date? That way you can ship on any subscription renewal, but still track "snoozed" subscriptions within stripe itself?
Interestingly, we actually have the opposite problem—our subscription model (effectively a payment plan) is so specialized that no-one, stripe included, supports our requirements out of the box.
EDIT: I re-read your comment and saw that you mentioned wanting to track active subscriptions easily, so I'm not sure my suggestion really solves your problem. Maybe you could classify any scheduled subscriptions as active/paused, if you're not using them anywhere else in your billing system?
Yeah you're right, it's another hacky way to solve it. Also yes, invoice at either a later date, earlier date, or immediately.
Another hacky way my CX team has been solving moving the next invoice date around is to pause their subscriptions then unpause/bill now (Stripe supports bill now but not reschedule next out of the box) - they'll set calendar invites for themselves to unpause when the customer requested then blow through them in the morning in the Stripe UI. At least we've upgraded from that scenario to the current "trial hack" scenario. We can pull analytics and treat "trial" as active, it's just annoying that their dashboard analytics are hard baked to treat trial as inactive.
I really think what Stripe did was launch Subscription then get a bunch of customer requests, created Subscription Schedules which was supposed to be the layer of advanced functionality you opt in to if you really need it, but created a product that's too complicated and misses the mark.
Oh another fun note I'll leave you with - we never want proration (the price of the product is always the price, since we're shipping physical products). But the proration radio is always on. So a team member using the Stripe UI forgets to turn it off every few days or so and we charge the customer the wrong amount (and have to sidestep proration line items when shipping)
Ugh, I really hope the lesson Disney learns isn't more sequels, less original IP.
I thought it was middle of the pack for Pixar, not their worst, far from their best though.
Even worse than the quality of the movie was how they advertised it. The preview seemed so recycled - the story seemed unoriginal the characters so similar to what we've already seen before with Inside Out and Soul. We just went on a whim because its nice to have the excuse to go to the theater
Doesn't seem like it performs result set nesting on joins? For example with the one to many of owner -> pet, I'd like the results to look something like `{ person: Person, pets: Pet[] }[]`. Knex doesn't do this either (afaict) - wrote a few "deep" queries with some convoluted lodash to group things up but mostly gave up and just live with raw resultsets.
I guess I still prefer that to a full on ORM, but that's really the one missing feature I want from these SQL query builder libraries
Oh sure, knex had a github issue with a similar recommendation. Interesting approach, and I suppose json -> ts is a smooth transformation, thanks for the tip
It's funny that the author introduces React as a framework that's notable because it brought a few paradigms mainstream, then immediately re-introduces the equivalent of virtual dom diffing without a tip of the hat.
Excited to see what they come up with here though, love Jetbrains products and Kotlin is a solid JVM language
What's frustrating is that Meta was so close to "getting it" - games where you get to be in the creative driver's seat are underrepresented right now. The Metaverse should be the place you can experience that childlike wonder you mentioned - decorate your place, visit your friends, set up your own escape room, show off the 3d art you made with tiltbrush. 3d myspace. During the pandemic I bought a quest, learned blender & unity, and built a little retro arcade with skeeball and a few other games. It was so much fun.
I'm disappointed that Apple is focused so much on office productivity AR, I'd rather be transported somewhere else in space and time with VR - not marginally more productive at work. But still crossing fingers that this is the start of something.
The metaverse problem is that there are a million different metaverse. Creating a stable spatial OS that other experiences can exist inside of creates a broader-spanning ur-system that might possibly grow. Where-as most metaverses aspire to be a beginning & end. Creating open ended technical ecosystems is a challenge.
