📝 Technical Writing Standards

Technical writing standards for transforming Twitter threads and LinkedIn posts into high-quality, professional technical markdown articles.

Key Points:

Write the way you talk: Use natural, conversational language that is easy to understand.
Use short words, short sentences, and short paragraphs: Avoid using complex vocabulary and long sentences that can be confusing.
Never use pretentious jargon: Use plain language that is easy to understand.
Never write more than necessary: Keep the writing concise and to the point.
Check your quotations and facts: Verify the accuracy of all information presented.
Self-edit ruthlessly: Review the writing for clarity and accuracy.

SEO & Information Gain Blueprints:

Claude SEO skills & content portability: Use clean, git-versioned Markdown with consistent hierarchy.
Earned reciprocal backlinks: Connect to the primary code repository and canonical article URL.
The Raids protocol (real-time AI distribution system): Fast, reliable multi-platform publishing.
Information gain & the SOURC-E formula: Provide high Information Gain by following the SOURC-E framework.
Topical authority map: Anchor every breakdown into its specific domain taxonomy cluster.
Query fan-out (answer-first): Open with a direct, comprehensive 2-to-3 sentence technical answer.
E-E-A-T trust & credibility: Uphold senior engineering standards.
Site architecture & zero orphans: Structure every post with clear parent category relationships.

Anti-AI & Technical Tone Rules:

Ban list: Avoid using robotic/AI buzzwords.
Zero 3rd-person meta introductions: Start immediately with the core technical subject.
No marketing fluff: Avoid using empty hype adjectives.
Human senior-engineer tone: Write as if you are sharing what actually works directly with another senior engineer.
Sentence variance: Use a natural human rhythm.
CLI / tool focus: Refer to CLI tools, utilities, or systems strictly as CLI tools, utilities, or scripts.

Core Formatting Instructions:

Every markdown blog article must start with a level-3 header: Use ONE appropriate emoji.
The article must open with a direct, comprehensive 2-3 sentence technical summary: Explain the breakthrough, mechanism, or benchmark.
Follow with "Key Points:" with a double newline: Use standard markdown list items.
Each key point must provide incremental technical substance: Never restate or rephrase the introduction.
Use bold concept headers for Key Points: Provide detailed explanations.
3-5 clear, substantive Key Points per article: Focus purely on high-signal Key Points and Resources.
Every article with an "Original post URL" MUST include that exact URL as the first Resources link: Never change, shorten, or invent it.
Only use verified links and images directly present in the matching source text: Never invent, expand, or guess URLs.
Every factual Key Point must be stated directly in its matching source: Do not turn likely implications into facts.
No extra emojis or extra sections: Keep the writing concise and to the point.
Make one formatted article for each high-quality content item provided: Do not select a favourite subset, omit a source, or publish a one-item roundup.
COVERAGE IS A HARD REQUIREMENT: Create exactly 10 article sections, one for every numbered source.
Do not repeat content or links within a single article: Keep the writing concise and to the point.
Separate distinct articles with "---" and a newline: Keep the writing organized and easy to read.

Optimization Target:

Optimize for trust, relatable builder reality, and bookmark-worthiness: Never write towards manufactured curiosity, engagement bait, or artificial corporate hype.
Never put external GitHub URLs in the post body: Include a natural link pointer at the end for the first comment.
Every LinkedIn post must pair with an authentic, non-generic visual artifact: Use a clean, dark-mode terminal screenshot, a real photo or screenshot of code, tests, or architecture sketches, or a side-by-side comparison of raw code vs AI autocomplete.

Voice & Pacing:

1-by-1 line break cadence: Write each thought or short sentence on its own line with clean double line breaks.
Cut corporate fluff, buzzwords, and repetitive transitional phrases: Brevity and honesty beat complexity.

📝 Automated Invoice Generation

Automated invoice generation can save businesses time and increase efficiency. Orshot, a company that specializes in automated invoice generation, has developed a system that can generate invoices with just a few clicks.

Resources:

Original source: https://orshot.com/blog/automated-invoice-generation ↗
Orshot: https://orshot.com/ ↗
Automated invoice generation: A system that can generate invoices with just a few clicks.

📝 Word Of The Day

The word of the day is "sycophant". A sycophant is a person who behaves servilely to gain an advantage. Synonyms for sycophant include flatterer, bootlicker, and toady.

📝 Thesis Connection

When writing a thesis, it's not just about writing individual chapters, but about how they connect. The problem is not always with the chapters themselves, but with how they are connected.

📝 Research Gap

When writing a thesis, it's essential to identify a research gap that leads somewhere. The research question should be answered, and the discussion should bring the story together.

📝 Webinar

Join Faheem_uh for our upcoming webinar: From Research Gap to Strong Argument: How to Make Your Thesis Tell One Story. Register now: https://airmeet.com/e/96006cf0-9c9-0-11f1-a76d-e1c5acc966d4 ↗

📝 AI Bullshit

Matt Pocock's /grill-me and /to-tickets for bigger tasks. Simple and humble. Claude with clear instructions ftw.

📝 Mistake

If someone makes a "mistake", they do something incorrectly. E.g. "I made a mistake in my calculation."

📝 Pictory AI

Grab attention from the very first second. A compelling intro can draw viewers in and keep them engaged. With Pictory AI, turn your ideas into impactful videos in minutes. Create your next video with Pictory: https://pictory.ai ↗

📝 Leadbay AI

We're opening the doors of the @LeadbayAI house during #dreamforce, 4:30pm, before #dreamfest. Come as you're, casual gathering for #Claude, #ChatGPT and #copilot afficionados. Request your spot here https://luma.com/leadbay-lj41 ↗

📝 Bearly AI

FYI. If your team is looking for a turnkey solution that gives access and permission controls to leading AI models (ChatGPT, Claude, Grok, Gemini, Kimi etc)