Writing Like Fernando: A Style Reference

The first rule of good writing is to know what you're trying to say. The second rule is to say it clearly. Everything else is ornamentation.

— Fernando Borretti (paraphrased from his approach)

This document distills the writing patterns of Fernando Borretti into a practical reference guide. Fernando writes with surgical precision, organizing complex technical and personal topics into digestible, actionable frameworks. His style combines intellectual rigor with practical wisdom.

Structural Patterns

Hierarchical Organization

Fernando structures everything hierarchically. His writing resembles well-architected software: clear modules, defined interfaces, minimal coupling between sections.

Pattern: Main topic → Major categories → Subcategories → Specific tactics/examples

Notice how his ADHD article divides into "Strategies" (high-level) and "Tactics" (implementation). Each strategy gets its own subsection with a clear title and italicized summary statement.

Key structural elements:

  • Every section has a descriptive title
  • Subsections begin with italicized thesis statements
  • Clear logical progression from abstract to concrete
  • Cross-references between related sections

Strategic vs. Tactical Thinking

Fernando consistently separates high-level principles from implementation details. This creates a natural learning progression: understand the why, then learn the how.

Example structure:

  • Strategies: "Chemistry First", "Memory", "Energy"
  • Tactics: "Task Selection", "Visual Field Management", "Inbox Zero"

The strategic section establishes mental models and frameworks. The tactical section provides specific, actionable techniques.

Numbered Frameworks

Fernando loves numbered lists and enumerated principles. This isn't arbitrary—it makes complex information scannable and memorable.

Three types of procrastination: ADHD, Anxious, Decision Paralysis.

Three things a todo list provides: Memory, Order, Hierarchy.

Notice the magic number three appears frequently. It's cognitively manageable while still allowing for nuanced categorization.

Comprehensive Table of Contents

Every substantial piece includes a detailed table of contents. This serves multiple purposes:

  • Readers can jump to relevant sections
  • The structure becomes immediately apparent
  • It forces the author to organize thoughts hierarchically
  • It provides a roadmap for long-form content

Voice and Tone

Authoritative but Practical

Fernando writes with quiet authority. He doesn't oversell or use excessive adjectives. Instead, he presents information with confidence backed by experience.

Instead of: "This amazing technique will revolutionize your productivity!"

Fernando writes: "This is especially useful for habit formation: my biggest blocker with forming habits was just remembered that I'd committed to doing something."

Notice the personal experience ("my biggest blocker") combined with clear explanation. No hyperbole, just honest assessment of what works.

Technical Precision

Fernando uses precise technical language without being pedantic. He defines terms clearly and uses consistent vocabulary throughout a piece.

Examples of precise language:

  • "A todo list is a neuroprosthesis that augments long-term memory for tasks"
  • "The todolist is an action-oriented long term memory prosthesis"
  • "Replace interrupts with polling"

He borrows terminology from computer science, neuroscience, and systems theory to create precise mental models.

Honest Assessment

Fernando doesn't oversell solutions. He's honest about limitations, tradeoffs, and when things don't work. This builds trust and provides realistic expectations.

"I don't have a perfect solution, but I try to manage it by applying a sense of proportionality..."

"This is so trite. 'Put your phone on Do Not Disturb and silence notifications'. And yet it works."

He acknowledges when advice sounds obvious or when his solutions are imperfect. This honesty makes the effective techniques more credible.

Content Patterns

Problem-Solution Architecture

Fernando consistently follows a problem-solution structure. He clearly defines the problem, explains why conventional approaches fail, then presents his solution with examples.

Standard pattern:

  1. State the problem clearly
  2. Explain why it matters
  3. Describe failed approaches (optional)
  4. Present the solution
  5. Provide concrete examples
  6. Acknowledge limitations

Concrete Examples

Every abstract principle gets illustrated with specific, personal examples. Fernando shares his actual Todoist setup, his morning routine, his specific struggles.

"For example: I like emojis in my todo list. The chores have a 🧼 emoji, the comms tasks have an ✉️ emoji."

The examples are never generic. They're drawn from his actual experience, making the advice feel tested and practical rather than theoretical.

Pros and Cons Analysis

Fernando frequently uses explicit pros and cons lists. This balanced approach helps readers make informed decisions rather than blindly following advice.

Pros:
• Simple to understand
• Simple to implement
• Can improve performance

Cons:
• Does not address concurrency
• Does not generalize to resource safety

This format makes tradeoffs explicit and helps readers understand when a particular approach is or isn't appropriate for their situation.

Systems Thinking

Fernando views problems systemically. Rather than isolated tips, he presents interconnected frameworks where different elements support each other.

"Personal growth is a dialogue between internal changes and external changes... It's more a back and forth, where internal changes unlock external changes which unlock further internal changes."

He shows how medication enables todo list usage, which enables habit formation, which reduces cognitive load. Each element reinforces the others.

Language Mechanics

Sentence Structure and Rhythm

Key patterns:

  • Varied sentence length: Short, punchy statements followed by longer explanatory sentences
  • Parallel structure: "You can write... You can write... You can write..."
  • Italicized thesis statements: Each section begins with an italicized summary
  • Parenthetical asides: (like this one) to add nuance without disrupting flow
  • Colon usage: Sets up lists and explanations clearly
"The first-line treatment for ADHD is stimulants. Everything else in this post works best as a complement to, rather than as an alternative to, stimulant medication."

Notice the rhythm: short declarative statement, followed by longer qualifying statement. This creates emphasis and makes key points memorable.

Vocabulary Choices

Fernando's language preferences:

  • Technical precision over casual language
  • Active voice predominantly
  • Minimal adjectives and adverbs
  • Concrete nouns over abstract concepts
  • Borrowed terminology from relevant domains (CS, psychology, etc.)

Examples in Practice

Opening a Section (Fernando Style)

Template:

[Italicized thesis statement that summarizes the key insight]

[Opening paragraph that contextualizes the problem]

[Transition to specific explanation or example]

A todo list is a neuroprosthesis that augments long-term memory for tasks.

I use Todoist on my desktop and my phone. The pro plan is worth it. I don't really think of it as an app, rather, it's a cognitive prosthesis.

The todo list provides three things: Memory, Order, Hierarchy.

Explaining a Complex Concept

Fernando's approach:
1. Define the concept clearly
2. Provide a concrete analogy or metaphor
3. Give specific examples
4. Explain why it matters
5. Address common misunderstandings

Example: His explanation of "energy as voltage" rather than "energy as battery" provides a more accurate mental model for how cognitive capacity works throughout the day.

Fernando-Style Writing Checklist

Structure

  • □ Comprehensive table of contents with numbered hierarchy
  • □ Clear distinction between strategic and tactical content
  • □ Each section has a descriptive title and italicized thesis
  • □ Logical progression from abstract to concrete
  • □ Cross-references between related sections

Content

  • □ Every abstract principle has concrete examples
  • □ Problems are clearly defined before solutions are presented
  • □ Pros and cons are explicitly listed for major approaches
  • □ Personal experience is used to illustrate points
  • □ Limitations and tradeoffs are honestly acknowledged
  • □ Systems thinking connects different elements

Language

  • □ Technical precision without unnecessary jargon
  • □ Varied sentence length for rhythm and emphasis
  • □ Active voice predominantly
  • □ Minimal adjectives and adverbs
  • □ Clear, concrete language over abstract concepts
  • □ Consistent terminology throughout

Tone

  • □ Authoritative but not arrogant
  • □ Honest about limitations and failures
  • □ Practical rather than theoretical
  • □ No overselling or hyperbole
  • □ Personal experience shared appropriately