Fifteen people. Fifteen minutes. Roughly ninety seconds of information.
The format's failure is structural, not cultural. You're asked what you did yesterday at the exact moment you're least able to answer before coffee, from memory, in front of an audience. So everyone reports the ticket they had open, because that's the retrievable answer. The actual texture of the day, the part where you'd learn something about how the sprint is really going, is gone.
The thing that's worked better for us: declaring intent in the morning instead of reporting history. "Here's what I'm picking up today" takes ten seconds, is answerable without memory, and produces something you can compare against reality at 6pm. Plan versus done, written down, no meeting.
Where it falls apart is that plan-versus-done is only useful if nobody's judged on the gap, the moment it becomes a scorecard, everyone starts declaring safe plans.
We’re live today! I’d love your honest feedback, especially on the onboarding, activity timeline, and drafted work updates. Every comment helps us improve Meridian.
Three months ago you quit your job to build this. It's MIT-licensed and free for individual developers, a lot to give away on day one. Congrats on shipping it.
@lucasjpols Thank you! Leaving my job to build Meridian was a big leap, so the support means a lot. Making it MIT-licensed and free for individual developers felt like the right way to ensure developers can trust it, audit it, and benefit from it without barriers.
You quit your job three months ago to build this, and it's MIT-licensed and free for individual developers. That's a lot to give away on day one. Congrats.
@ben_kahan Thank you! Leaving my job to build Meridian was a big leap, and making it MIT-licensed and free for individual developers felt essential to earning developers’ trust and making it accessible from day one.
Such a smart and needed tool for career growth. Congrats on bringing this to life!
@thisiskp_ Thank you for the support! As one of Meridian’s makers, it means a lot to hear this from someone who helps founders bring products to life. We’d value your perspective on what could make Meridian even more useful for career growth.
Congrats on the launch, guys! 🎊
@gordana_laskovic Thank you for celebrating with us! 🎊
Congrats on the launch!
@mcarmonas Thank you! Really appreciate the support.
hi @Meridian @adityaharish2002
Quick question on repo access -- Meridiona/meridian is MIT-licensed and public, but Meridiona/screenpipe-fork is private, and it's not optional: it's the in-process capture stack (screen + a11y + OCR), the sole data source since the Bucket-2 cutover.
Without read access to it, nobody can actually build the tray app from source -- even the daemon-only build fails, since Cargo resolves the whole workspace lockfile at once.
Is that intentional (proprietary capture code, PII-sensitive, still pre-release, etc.), or just an access oversight? If it's meant to stay private, might be worth a line in CLAUDE.md or the README saying so, since right now "clone and build" quietly dead-ends there with no explanation.
If it's an oversight, can I get added? I'm on GitHub as arush361
@sharma_arush
This is intentional, and we plan to add it to the monorepo. Thank you for bringing it to our attention. Its intentional and we plan to add itt o he mono repo but thats for brinding it to our notice