opportunity · Discussion
The discussion highlighted the need for incorporating before/after metrics to demonstrate impact, as suggested by Mary. Tunde and Brandon both inquired about the event log's database choice and indexing strategy, indicating a shared interest in technical details. Next steps include creating a Loom video to explain architecture decisions and considering revisions based on feedback for future improvements.
Log in to join the discussion.
Question: did you use Postgres or MySQL for the event log? Curious about the indexing strategy.
We used Postgres + JSONB for a similar event stream. Happy to share the schema.
Count me in if you spin up a workspace for the follow-up.
We used Postgres + JSONB for a similar event stream. Happy to share the schema.
Question: did you use Postgres or MySQL for the event log? Curious about the indexing strategy.
Fair pushback. I would still ship the simpler version first.
Thanks — I will add a Loom this week and link it on the passport.
Agreed — the outcomes section is what sold me.
Yes, timezone overlap was the first filter on our last hire.
I can intro you to two builders who solved the multi-tenant piece differently.
Thanks — I will add a Loom this week and link it on the passport.
Count me in if you spin up a workspace for the follow-up.
Agreed — the outcomes section is what sold me.
Strong write-up. Would love a short Loom walking through the architecture decisions.
What would you rewrite if you had another week? Always useful for juniors reading along.
Agreed — the outcomes section is what sold me.
I can intro you to two builders who solved the multi-tenant piece differently.
I can intro you to two builders who solved the multi-tenant piece differently.
Count me in if you spin up a workspace for the follow-up.
The Lagos/Accra context in this build is refreshing — not another generic todo app.
That metric idea is sharp. Conversion before/after would strengthen the story.