Submissions from github.com/getlago

		Why Stripe's 'Open' Isn't Open–The Developer's Dilemma (github.com/getlago)
		1 point by AnhTho_FR 6 days ago \| past \| discuss
		Misconceptions about using open-source products (github.com/getlago)
		2 points by thibo_skabgia 10 days ago \| past \| discuss
		The Limits of Stripe's Openness: What Developers Need to Know (github.com/getlago)
		2 points by jdenquin 10 days ago \| past \| discuss
		Can Stripe products stand on their own? (github.com/getlago)
		2 points by jdenquin 14 days ago \| past
		Avoid vendor lock‐in in the payments space (github.com/getlago)
		2 points by AnhTho_FR 15 days ago \| past
		How open should Stripe be? (github.com/getlago)
		1 point by brivu 16 days ago \| past
		Stripe – Is Sky the Limit? (github.com/getlago)
		3 points by thibo_skabgia 24 days ago \| past
		How open can Stripe be? (github.com/getlago)
		4 points by AnhTho_FR 25 days ago \| past
		Why Stripe Won (github.com/getlago)
		2 points by timbourcier 25 days ago \| past
		Against the 'QA‐Free' Philosophy (github.com/getlago)
		8 points by AnhTho_FR 37 days ago \| past
		Stripe Data vs. Open‐Source Alternatives: A MRR Example (github.com/getlago)
		167 points by AnhTho_FR 76 days ago \| past \| 69 comments
		Anatomy of a B2B Payment (github.com/getlago)
		1 point by AnhTho_FR 78 days ago \| past
		What to do if a user racks up an AI bill and doesn't pay (github.com/getlago)
		1 point by jdenquin 4 months ago \| past \| 1 comment
		Cost Precedes Performance for Devtools (github.com/getlago)
		1 point by thibo_skabgia 4 months ago \| past
		Pricing AI products is an engineering nightmare (github.com/getlago)
		1 point by AnhTho_FR 4 months ago \| past
		Performance isn't a strategy, community is (github.com/getlago)
		1 point by gneray 5 months ago \| past
		Pricing AI is a unit based problem (github.com/getlago)
		1 point by thibo_skabgia 6 months ago \| past
		Pricing AI products is hard (github.com/getlago)
		2 points by AnhTho_FR 6 months ago \| past
		Pricing AI Is Hard (github.com/getlago)
		1 point by jdenquin 6 months ago \| past
		Charging Customers Is Hard (github.com/getlago)
		3 points by AnhTho_FR 6 months ago \| past
		Performance inching isn't a strategy, even for AI models (github.com/getlago)
		2 points by jdenquin 7 months ago \| past
		Using ClickHouse to scale an events engine (github.com/getlago)
		237 points by wyndham 7 months ago \| past \| 97 comments
		Performance Isn't That Important (github.com/getlago)
		2 points by AnhTho_FR 7 months ago \| past
		Using ClickHouse to scale an events engine (github.com/getlago)
		3 points by AnhTho_FR 8 months ago \| past
		ClickHouse saved our events engine problem (github.com/getlago)
		6 points by mathewpregasen 10 months ago \| past \| 2 comments
		Do not rely on Stripe Data products (github.com/getlago)
		3 points by AnhTho_FR 11 months ago \| past
		Why charging customers still isn't a cakewalk (github.com/getlago)
		1 point by AnhTho_FR 11 months ago \| past
		Most common charging sub-problems (github.com/getlago)
		2 points by AnhTho_FR 11 months ago \| past
		Payment isn't billing, which isn't metering, which isn't invoicing (github.com/getlago)
		4 points by donnaoana 11 months ago \| past
		Skipping Beta Is a Mistake (github.com/getlago)
		2 points by thibo_skabgia on Nov 2, 2023 \| past
		More