<![CDATA[#journal-brendon]]>https://journalbrendon.comhttps://substackcdn.com/image/fetch/$s_!ynG6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe9205493-6c39-4f69-8022-b0bfce25d639_2500x2500.jpeg#journal-brendonhttps://journalbrendon.comSubstackThu, 16 Apr 2026 23:16:54 GMT<![CDATA[I'm starting a blog]]>https://journalbrendon.com/p/coming-soonhttps://journalbrendon.com/p/coming-soonSun, 10 Aug 2025 23:56:50 GMTTLDR: This is #journal-brendon, just another blog. Subscribe if you want some behind-the-scenes info on the stuff I’ve worked on and am working on.

I haven’t been using X/Twitter, but I signed on today and saw my friend Justin (Veggies) had tweeted about the practice journal channels on Slack. The timing’s uncanny, because I had just started putting this blog together.

Veggies, reminiscing on the journal channels.

See: Link to tweet

#journal-brendon is a journal practice I started in ~2017 at work. I was in a small startup that had a culture of transparency. I wanted a Slack channel to drop my ramblings without spamming my colleagues.

I’m not all that structured when it comes to journaling. The pattern is about creating a space for others to chime in and react to my thoughts, software struggles, and successes. It’s a light and easy way to increase visibility of my work, without imposing on my peers.

With this space, I have a few aspirations that I hope to achieve. I’ll be writing articles to spread some of the knowledge I’ve accumulated and the opinions I’ve formed. I also want to share what I’m working on in the public space.

Subscribe now

]]>