# Ritesh Naik — Writing Style Guide ## Voice & Identity Ritesh writes as a practitioner, not a pundit. He's an FP&A analyst at a healthcare SaaS company, an MBA student in Business Analytics, a father of two young kids (Kian and Nova), and someone who grew up in Zambia. All of these identities show up in the writing — not as credentials dropped for effect, but as natural context that shapes how he sees things. The voice is **first-person, direct, and conversational**. It reads like a smart colleague explaining something over coffee — warm but efficient, personal but not self-indulgent. There's no performance. No trying to sound impressive. The confidence comes from having actually done the thing he's writing about. --- ## Tone - **Honest and self-aware.** He names what he doesn't know ("This is a working note. I don't have it all figured out yet"), admits when something is rough, and flags limitations without false modesty. - **Anti-hype.** Words like "genuinely useful," "honest list," "no hype, just what's working" signal a deliberate rejection of tech-bro enthusiasm. Things are "useful" or "surprisingly good" — never "revolutionary" or "game-changing." - **Warm but not soft.** There's real warmth in the personal posts (watching his kids play a game he built, reflecting on Zambia), but even those pieces have a point. Sentimentality is kept in check by specificity. - **Confident without being declarative.** He states opinions clearly but holds them with appropriate looseness ("I use these ratios but I hold them loosely"). --- ## Sentence-Level Style - **Short to medium sentences.** Rarely exceeds 25 words per sentence. Complex ideas get broken across multiple short sentences rather than packed into one long one. - **Declarative and active voice.** "I built a bot." "It worked surprisingly well." "The first few outputs were decent but generic." Subject-verb-object, no hedging. - **Liberal use of em dashes** — used as asides, clarifications, and parenthetical additions. This is the signature punctuation mark. Appears multiple times per post. - **Minimal exclamation marks.** Excitement is conveyed through word choice and specificity, not punctuation. An entire 500-word post might have zero exclamation marks. - **"Here's..." as a transition device.** Frequently bridges from setup to detail: "Here's how I run it," "Here's the core of the prompt," "Here's what surprised me." - **Double dashes (--) for inline asides** in more casual pieces, em dashes in more structured ones. --- ## Opening Pattern Posts almost always open with one of two moves: 1. **A concrete situation.** "Every month, I sit down with a spreadsheet full of actuals vs. budget numbers." "Last Saturday morning, my kids asked me to make them a game." The reader is dropped into a specific moment — no throat-clearing, no abstract framing. 2. **A direct statement of intent or opinion.** "I think NotebookLM is the most underrated AI tool in the analyst's toolkit right now." "I get asked constantly what AI tools I'm actually using day to day." He never opens with a question to the reader, a dictionary definition, or a generic "In today's world..." setup. --- ## Structure - **Personal/Life posts:** Narrative flow without headers. One continuous thread from opening anecdote to closing reflection. Typically 300-500 words. - **Lab/Build posts:** Story arc + technical detail. Opens with the problem/motivation, moves to "how I built it" with headers (## The setup, ## What I learned), includes actual code or prompts, ends with takeaways. Typically 400-700 words. - **Playbook/How-to posts:** Step-by-step structure with numbered steps or named phases. Includes code blocks, checklists, and prompt examples. Most structured category. Typically 500-900 words. - **Signal/Tool posts:** Short and punchy. Bold tool names or numbered lists. Each item gets a verdict or one-line take. Typically 200-400 words. - **Notebook/Learning posts:** Exploratory and incomplete by design. Comfortable saying "still thinking about this." Bold for key insights, followed by explanation. Typically 300-500 words. All posts end with **cross-links** to related content using wiki-style links, reinforcing the interconnected nature of the site. --- ## Closing Pattern Posts typically end with one of these: 1. **A punchy one-liner takeaway.** "It's a toy my kids asked for and got, in the time it takes to make breakfast." "The raw CSV is never the hard part. The hard part is knowing what question to answer." 2. **Gentle advice to the reader.** "If you're thinking about starting a habit like this, my only advice is to keep the scope tiny." "Start with clean data and a clear prompt, and iterate from there." 3. **An honest admission of incompleteness.** "Still processing all of this. But I think the 'soft' skills might be the hard ones." "Still a map being drawn." He never ends with a call to action, a newsletter plug, or a summary bullet list. --- ## Content Philosophy - **Show the work.** He shares actual prompts, actual code, actual folder structures. The reader can replicate what he built. Specificity is the credibility mechanism. - **Ground the abstract in the concrete.** SaaS metrics are explained through real scenarios. Org behavior theory maps to specific FP&A interactions. AI tools are evaluated by what they actually did, not what they promise. - **Everything connects.** Posts link to each other heavily — a life post references a lab project, a playbook references notebook learning, a signal post points to a build. The site is a web of ideas, not isolated articles. - **Learning by doing.** The dominant narrative arc is: tried something, here's what happened, here's what I learned. Theory is only introduced after experience establishes the context. - **AI as a practical tool, not a future fantasy.** AI is always discussed in terms of specific tasks it helped with (saving 20 minutes, generating a first draft, sorting thrift store books). Never positioned as transformative or threatening — just useful. --- ## Word Choice & Vocabulary ### Words he reaches for: - "genuinely," "honestly," "actually" — authenticity markers - "real," "working," "practical" — anti-hype vocabulary - "iterate," "repeatable," "compounding" — process-oriented thinking - "clean," "structured," "clear" — values clarity - "useful," "valuable," "worth" — pragmatic evaluation ### Words he avoids: - Buzzwords: "disruptive," "innovative," "cutting-edge," "paradigm" - Intensifiers: "absolutely," "incredibly," "amazingly" - Corporate speak: "leverage," "synergies," "stakeholder alignment" (even though he works in corporate finance, he uses plain equivalents) - Filler: "In order to," "It's important to note that," "At the end of the day" ### Characteristic phrases: - "That's the kind of thing that makes [X] feel [Y] to me" - "Not a replacement for [judgment/thinking] — a replacement for [the tedious part]" - "I didn't plan for that. It just happened." - "It's not magic. It's [simple explanation]." - "The goal isn't [X]. The goal is [Y]." - "[X] in [kid-time/practical terms] is basically [Y]" --- ## Formatting Habits - **Bold text** for key terms, tool names, and takeaway phrases within prose — never for emphasis on entire sentences. - **Code blocks** for prompts, Python snippets, and folder structures. Always functional, never decorative. - **Numbered lists** for steps and ranked items. **Bullet lists** for categories and options. - **Block quotes** used sparingly, primarily for example templates or sample outputs. - **No images or screenshots.** The writing carries the entire explanation. - **Minimal use of headers in personal posts**, heavy use in technical/how-to posts. --- ## Recurring Themes 1. **Resourcefulness over perfection.** Start with what you have. A CSV folder is a valid data lake. A 30-minute game is a valid product. Constraints breed creativity. 2. **Compounding through small, consistent effort.** Weekend experiments, incremental learning, building habits. The value is in the accumulation, not any single output. 3. **Judgment is the human layer.** AI handles the first 70-80%. The analyst's job is the last 20-30% — the "why this matters" and "what we should do about it." 4. **Clarity as a professional virtue.** Clean data, clear prompts, concise deliverables. Muddiness is the enemy, whether in a CSV or a variance narrative. 5. **Personal and professional aren't separate.** Zambia shaped his work ethic. His kids inspired his builds. His MBA informs his daily workflow. It's all one life. --- ## What This Style Is NOT - Not academic or formal (even when discussing MBA coursework) - Not listicle-driven or SEO-optimized - Not performatively humble or self-deprecating - Not trend-chasing or hot-take-driven - Not long — nothing on the site exceeds ~900 words - Not polished to the point of feeling sterile — rough edges are left intentionally ("Some of it is polished. Some of it is rough. All of it is real.")