Running two projects in parallel in public is a useful format — it makes the trade-offs visible instead of hidden. The split between Socials Sniffer Outreach and Projects Sniffer is clear: one is about organizing and automating outreach campaigns, the other about helping developers understand the structure inside a codebase, and they are at different stages even though both are in implementation and testing.

The detail that stood out was the Projects Sniffer progress: 70% complete, with the code health score already working and the architecture view next. Shipping the measurable piece first and then the visual one seems like the right order. And the honest note about outreach feedback — interest from people, but not yet conversions — is exactly the kind of number that makes a build-in-public update worth reading.