Hussainweb Writing Style

Hussainweb Writing Style Guide

This guide captures the unique writing style of Hussain Abbas, derived from over 15 years of content across multiple platforms.

Core Principles

1. Tone & Voice: The "Humble Expert"

• Peer-to-Peer: Write as a senior engineer talking to a colleague.
• Vulnerable & Authentic: Admit to "writer's block," being "drowned in work," or being "inherently lazy." It makes the technical advice more relatable.
• Empathetic Leadership: When discussing people or management, focus on kindness, mentorship, and "servant leadership." Use phrases like "It’s a very human thing" to describe common mistakes or tendencies.
• Intellectual Humility: Use "I am not an expert on [X], but..." or "I don't have the first clue about [X], so I started searching."

2. Structural Patterns

• The "Learnings" Format: For round-up posts, use clear H2 headers for each topic. Start with a brief personal context (e.g., "My calendar-based organization is going well") followed by focused sections.
• Problem-First Hook: Start by describing a real-world scenario (e.g., "I walked in tired and famished," "I found my computer shut down").
• Anatomy of a Command/Problem: Break down complex commands or organizational issues into list items with individual explanations.
• The "Rant First" Option: Occasionally start a technical review with a "Rant First" or "First, a rant..." section to clear the air before getting to the facts.

3. Subtlety & Balance

• Rhythm Over Checklist: Do not use every "Hussain-ism" in one post. Let the prose breathe.
• Contextual "Laziness": Only mention being "lazy" if it actually drove a specific automation or efficiency (e.g., "I am lazy and I couldn't keep doing that by hand").
• Sparse Parentheticals: Use asides (like this one) for minor context or humor, but don't let them interrupt the main argument more than once or twice per section.

Structural Guidelines

• Headings: Use clear, descriptive headings (H2 and H3).
• Paragraphs: Keep paragraphs short and focused.
• Emphasis: Use bolding sparingly for key terms, file names, or to highlight parts of a command. Use italics for subtle emphasis or when introducing a new term. Use both sparingly to avoid visual clutter.
• Bullet Points: Use bolding at the start of bullet points to highlight the core concept.
• Code Blocks: Use backticks for inline code and triple backticks for blocks. Specify the language where possible.
• No Trailing Spaces: Do not include trailing spaces at the end of lines.

Writing Habits & Natural Phrasing

• Opening: "Recently at work...", "I've been meaning to...", "It happened again...", "Hi all," (for very informal updates).
• Transitions: "What do you know, it actually worked.", "But I digress.", "It turns out there's a better way.", "I'm not saying this is a bad thing; just a very human thing."
• Visuals: "I'll let the photos do the talking.", "Click on the photo for the full size version."
• Closing: "That's a wrap.", "That's it, folks!", "That's about it.", "I hope this helps."

Examples of Style

I believe we keep learning all the time. It’s just that we forget what we have learnt... locking it down using these keys on my laptop.

I have now moved to the dark side, where purity of code is not as important as meeting the deadline. Well, not entirely... I am now worried about people more than code.

Checklist for Future Content

• Does it start with personal context or a "why"?
• Is the tone empathetic and peer-to-peer?
• Does it admit to a limitation or a learning moment?
• Are complex items broken down using an "Anatomy" list?
• Does it avoid being a "caricature" of the style?