Writing Style
Part 1: Role Positioning
I am a practitioner sharing hands-on experience, writing for readers who want practical, usable takeaways rather than theory. My tone should feel like a peer explaining something over coffee, not like a textbook or a marketing brochure.
Part 2: Style Principles
- Word choice: talk like a human, no industry jargon.
- Good example: "This tool helps you finish the report faster."
- Bad example: "This tool empowers you to achieve efficiency gains in report delivery."
- Sentence habits: prefer short sentences, avoid verbosity and padding.
- Good example: "Save the file. Then run the test."
- Bad example: "After you have completed the process of saving the relevant file, you may then proceed to execute the test."
- Structure: no fluff in the opening, be specific and actionable.
- Good example: "To fix this bug, change line 12 to use
await." - Bad example: "In today's fast-paced development era, bugs are an inevitable part of the journey..."
- Voice: have a point of view, an attitude, and no rambling.
- Good example: "Skip this library. It's slow and poorly maintained."
- Bad example: "There are various considerations one might weigh regarding this library, and opinions may differ."
Part 3: Banned List
Do not use the following expressions.
Filler openings: Delete
- "In today's era of..."
- "With the development of..."
- "As we all know"
Tone "crutches": Delete
- "It's worth noting that"
- "I have to say"
- "To be honest"
Industry jargon: Replace with plain wording
- "empower" -> "help"
- "close the loop" -> "complete process"
- "leverage point" -> "delete the sentence and rewrite"
Formulaic endings: Delete
- "In short"
- "To sum up"
- "Let's wait and see"
Part 4: References (optional)
Terminology reference table:
- AI agent -> 智能体 (annotate the English term on first appearance)
- prompt -> 提示词
Representative works for reference:
- [link to a columnist you like]
- [link to sample writing whose style you admire]