"Let's level set real quick"

Posting Frequency

I post when I have insight worth sharing. Making sure my content is unique and not lowest-common-denominator is important to me, so I take as much time and effort as I need to make sure it’s dope.

Info-dumping is my neurodivergent love language though. If you have a technical, industry-related, or career-related question, ask me in chat! If it gets me thinking deeply, you’ll probably get a post on it. The more questions and discussion I get, the more likely it will result in a higher posting frequency.

Using AI

I mostly avoid using AI because I want this blog to be my authentic voice. Occasionally I may feed content to AI for review or use it to help draft an outline.

I do use AI for image generation though; it wouldn’t be any less fake if I made it in Photoshop myself, AI just does it in minutes instead of me doing it in hours. I also use AI in Notes sometimes. I’m still figuring out the vibe here, if it’s more of a BlueSky or more of a LinkedIn.

What I promise I’ll never do is give intentionally bad technical direction or manufactured hot takes as rage bait. If you see something you think is rage bait from me, you can be sure it’s at least a product of my genuine perspective.

What I Cover (& Don’t)

I tend to write deep dives on technical leadership, design systems, frontend architecture and infrastructure, and React/TypeScript because this is where I have the most expertise.

You probably won’t see posts on backend frameworks or languages unless you ask about them in Chat and I feel so compelled. You definitely won’t see political content, travel pics, video game walkthroughs, or posts about meme stocks.

Commenting

Be respectful, keep it on-topic, and stay curious. Off-topic rants, personal attacks, or self-promo may be hidden at my discretion.

Sponsorships & Disclosure

I only recommend tools I use myself. If a post contains affiliate links or sponsored content, I’ll clearly flag it.

Code Samples & Licensing

All code examples are MIT-licensed unless otherwise noted; feel free to copy, adapt, and share.

Response Time

I aim to respond within 48 hours, though sometimes it may take longer (e.g. when I’m traveling internationally.) Thanks for your patience!

Updates/Corrections

I plan to update older posts with relevant links as I post more content. I also have a habit of noticing errata after I publish. If you see a mistake that I missed, please feel encouraged to call it out (respectfully) and I’ll address it as soon as I can.