aidanlister
Joined 13 years ago
Joined 13 years ago
I’ve been looking for an alternative to CARTO, their sales reps are awful and their pricing is wildly expensive and opaque.
Businesses have natural expansion and contraction cycles. New products are built and iterated on with a hope of finding product market fit, but most of these endeavours fail.
I am paid to make the hard decisions. Sometimes that hard decision is to scale down the workforce. Yes, it sucks, but a large majority of those impacted end up financially ahead (rehired quickly and one, two or three months ahead because of the redundancy payout).
Penalising a CEO for making hard decisions is a great recipe for stagnant companies. What would have happened to Kodak or Blockbuster if they had a CEO with enough grit to cut the workforce and pivot the businesses before they collapsed?
3% on payment processing, subscription management and collection.
7% on AWS.
10% on product support, account management and retention.
If you’re fast growing this is about right. If you’re starting to slow down then you can afford to spend more time optimising these, eg 2, 4 and 9, giving you a GM of 85% which is elite for a B2B SaaS.
- You make Microsoft Excel. Someone uses Excel to leak a million people’s PII.
- You build shovels. Someone murdered someone with your shovel.
- You build an analytics product, explicitly ban collecting PII in your EULA, someone does it anyway.
It’s fun to be outraged and hating on GA is very in vogue at the moment, but this specific incident is just someone (yes, someone, not a nefarious company) using a popular tool incorrectly.
A bunch of very smart bankers have spent an enormous amount of time doing due diligence on the company you work for and they think that the risk is low and repay-ability is high … but the contrarian always knows better. To them this is a sign that the end is nigh, and they rejoice in the feeling of their beautiful superiority.
The billing part was easy to build (though of course we under-estimated the effort by 10x), but the reporting is the really tricky part. Revenue recognition, plus simple things like correctly tracking upgrades/downgrades vs expansion/contraction when someone changes plan mid-month.
Is this something that Lago does now or intends to include? I could not see it in the docs.
The ergonomics of doing this in pre-commit make no sense.
Spin up a PR in GitHub and get Cursor and/or Claude to do a code review — it’s amazing.
It’ll often spot bugs (not only obvious ones), it’ll utilise your agent.md to spot mismatched coding style, missing documentation, it’ll check sentry to see if this part of the code touches a hotspot or a LOC that’s been throwing off errors … it’s an amazing first pass.
Once all the issues are resolved you can mark the PR as ready for review and get a human to look big picture.
It’s unquestionably a huge time saver for reviewers.
And having the AI and human review take place with the same UX (comments attached to lines of code, being able to chat to the AI to explain decisions, having the AI resolve the comment when satisfied) just makes sense and is an obvious time saver for the submitter.