happy birthday to one of our elite technical writers @Ok_Timmy🎉🎉🎉

Want a paragraph rewrite? Drop it 👇

many auto workshops will soon experience massively reduced cashflow, and they don’t even know yet… so here is the gist, the world is moving fast. some years back, you’d remember your Dad driving a clean manual transmission car. now, things have changed. for many years now, automatic transmission cars have taken the market. the trend is getting better again: the arrival of durable electric cars, especially with house Chinese car companies are pushing thousands of it to the market. here is the issue: many car auto professionals are not upskilling on how to fix things that can go wrong in an EV car. and this is how they will miss out on many deals that could have boosted their cash flows. btw, this is not only about auto professionals. as a software engineer and product builder, how are you adapting to new industrial terrains? evolve or bust! ps: spot the artworks behind me.

Clarity is a growth strategy 🤝 Bad writing vs. Good writing

When docs work, no one notices. When they fail, no one forgets.

Web3 needs more agencies that understand dev audiences, depth & distribution. These ones get it 👇 1. Coinbound @coinbound 2. Blockchain Alpha @blockchainalph 3. Omni Agency @omni_agency 4. Crowdcreate @crowdcreate_us 5. reblonde @ReBlondePR

the last time I sent a newsletter was 3 years ago. sent something to the homies today. read here: open.substack.com/pub/johnfa…

there’s absolutely no reason to put your private keys plainly or in an environment variables file in big 2026. and I won’t only massage the problem, here’s the solution: - use the cast wallet feature in Foundry. even Hardhat has something similar. with the cast wallet feature in your Foundry bash terminal, you can invisibly paste your pk, lock it, and call it whenever you have to deploy. if you’ve lost money due to pk leaks before, you’d cherish this. and good news is, you don’t have to lose money before you follow good DevSecOps. read more here: getfoundry.sh/guides/deployi… would you want me to write an extensive article on it?

for most SaaS teams and crypto protocols, there is a wide gap between pre-seed and Series B. ideally in terms of structure for content output. in most cases, they want to keep the teams small so they don’t over hire and increase burnrate unduly. which is understandable. nonetheless, running a startup is brutal game ; you have to come correct. this is why the idea of partnering with a competent agency might sound attractive. why? - only plug and play as often as you need content - already trained personnels - pre-existing content planning and review systems - you only focus on building your protocol at Blockchain Alpha, we’ve had to partner with a good number of companies in this category. and it’s always a great win for them. if you’re a leader early-stage crypto or SaaS team and you want to talk more, reach out.

Wanna know how to make docs work? Start here.

Most technical docs lose readers before they even start. Not because the tech is hard. But because the entry point is broken. Let’s talk about that 👇 Docs That Work #1

Docs aren’t just information. They’re onboarding. And onboarding is storytelling. You’re guiding someone from confusion to confidence.