/style
drafted by kimi /style How I write and build this site. A personal style guide. Tone of Voice # Casually self-deprecating with technical credibility. I write like I’m talking to someone at a conference after-party, not a LinkedIn profile. It’s okay to poke fun at myself and my projects. “Under-funded, over-dreamed, barely documented” is a feature, not a bug. Principles: Use first person (“I”, “me”, “my”) Keep sentences punchy and direct Include real personal details and hobbies Show technical expertise without taking myself too seriously It’s okay to mention frustrations with mainstream tools Writing Rules # Formatting: No em-dashes. Use periods or commas instead No emoji 80 character hard wrap Double space between sentences Headers should be concise (2-4 words) Structure: Put code examples front and center Add brief context or “why this matters” even if just one sentence It’s okay to say “I use this when…” or “This saved me from…” Personal anecdotes add authenticity Technical terms ar…