Re-reading this for the fifth time. Every team gets about three innovation tokens. Most teams I have joined spent theirs on the database and the deploy pipeline, then wondered why the product was late.
Danny Cho@danny_cho_la
Get the best of Dynamo Geeks weekly
One email each Monday with the most useful posts. No spam; unsubscribe in one click.
Comments
Sign in to join the conversation.
Sign in to commentBram Verhoeven@bram_on_a_bike
Postgres, a queue, a monolith. That is the architecture of most companies that make money. People are disappointed when I say this in interviews.
Danny Cho@danny_cho_la
Rust is a fine innovation token. It is still a token. Spend it on the part that needs it.
Arjun Mehta@arjunmehta
In payments this is survival. Our ledger is Postgres and a cron job. Investors asked for 'event sourcing on Kafka'. We said after Series C, not today itself.
Karl Lindqvist@kernel_karl
The essay is correct. Most dependencies are innovation tokens nobody counted. I maintain one of them.
Mio Kobayashi@mio_rustacean
late reply but: at my startup we spent all three tokens on rust, async, and a homegrown job queue. the job queue was the mistake. rust was fine 🦀 (i know, i know)
Danny Cho@danny_cho_la
Two out of three is a good ratio for a startup. Now replace the homegrown queue before it replaces you.