We've been thinking about what a blog means for a consultancy like ours. The typical approach is standalone articles - polished pieces about React patterns or TypeScript tips. But that felt disconnected from what we actually do.
What we're building now is more of a journal. Daily notes on what we're working on, why we're making certain decisions, and what we're learning. Less polished, more real.
The idea is simple: developers on the team write about their day. Not tutorials, just honest documentation of the work. Sometimes it'll be technical - a gnarly bug we fixed or an architecture decision we debated. Other times it'll be more reflective.
We think this is more valuable than yet another "10 React tips" post. It shows how we actually think and work.