A fisherman doesn’t ask permission from the ocean. He reads the currents, adjusts his approach, and gets to work. Writing isn’t different—except we’ve convinced ourselves it is.
Look, I’ve debugged Kubernetes clusters at 2 AM and sold phones to skeptical Alaskans. I’ve written technical documentation that prevents million-dollar outages and articles that get shared thousands of times. The common thread? Every system has a logic to it—you just have to stop fighting it and start seeing it.
But here’s the thing about most writing advice: it’s designed to keep you consuming advice, not producing words. Let’s cut through the noise.
The Permission Problem
The writing industry has built a beautiful prison. MFA programs. Publishing gatekeepers. “Proper” procedures. Flash fiction challenges that start mid-conversation because that’s this week’s arbitrary constraint.

Meanwhile, the best writers I know—the ones actually reaching people—figured out something simpler: you don’t need permission to write well. You need practice and honesty.
That technician who writes crystal-clear documentation that saves his company time and money? He’s a better writer than most MFA graduates. Why? Because he writes for humans who need to understand things, not professors who grade theoretical frameworks.
“The amateur sits and waits for inspiration, the rest of us just get up and go to work.” – Stephen King
The Clarity Conspiracy
Here’s what they don’t tell you in writing workshops: clarity is rebellion. Every unnecessarily complex sentence, every jargon-heavy paragraph, every “as you know” preamble—that’s not sophistication. That’s static.
I learned this selling cell phones in Alaska. You had thirty seconds to explain why someone should spend their hard-earned money on a device they’d carry for two years. No fluff survived that environment. Either your explanation worked, or you went hungry.
The same principle applies whether you’re writing code comments, marketing copy, or the next great American novel. Your reader’s time is finite. Their attention is contested. Respect both.

This doesn’t mean dumbing down your ideas. It means translating complexity into clarity. Einstein allegedly said if you can’t explain it simply, you don’t understand it well enough. Whether or not he actually said it, the principle holds.
The Tools Don’t Write the Code
Writers love to obsess over tools. Scrivener vs. Notion vs. Google Docs. Markdown vs. rich text. Dark mode vs. light mode. Meanwhile, the best article they’ll write this year is probably sitting unwritten in their head.
I’ve written on everything from yellow legal pads to enterprise collaboration platforms. Here’s the secret: the tool that gets words on the page is the right tool. Everything else is sophisticated procrastination.
Same with grammar rules and style guides. Yes, learn them. They’re the syntax of clear communication. But don’t let perfect grammar become the enemy of effective communication. I’d rather read a grammatically imperfect piece that changes how I think than a technically perfect essay that says nothing new.
The Feedback Filter
Not all feedback is created equal. Your mother thinks everything you write is brilliant. Your writing group has opinions about everything. Neither perspective will make you a better writer by itself.
The feedback that matters comes from people who’ve solved similar problems. If you’re writing technical documentation, get feedback from users who actually follow the instructions. If you’re writing fiction, find readers in your genre who buy books with their own money.

Here’s the filter I use: Does this feedback help me communicate more effectively with my intended audience, or does it make me sound more like the person giving the feedback? The first is useful. The second is cosplay.
Also, beware the feedback that comes with no skin in the game. Anyone can criticize. Not everyone can build something better. Weight advice accordingly.
The Real Curriculum
Want to become a better writer? Here’s the curriculum nobody’s selling:
Read outside your genre. Technical writers should read fiction. Fiction writers should read user manuals. Bloggers should read research papers. The best insights come from pattern recognition across domains.
Write for people who don’t have to read you. Newsletter subscribers can unsubscribe. Blog readers can click away. Social media followers can scroll past. This constraint forces clarity and value.
Edit ruthlessly, publish regularly. Every published piece teaches you something no workshop can. Every edit makes you more honest about what’s actually on the page versus what you intended to say.
Solve real problems. Write the instruction manual that doesn’t exist. Answer the question people keep asking. Fill the gap you wished someone else would fill. Purpose beats poetry every time.
“I write to find out what I think.” – Joan Didion
Same Rules for Everyone
Here’s what I learned debugging systems at 2 AM: code either works or it doesn’t. The server doesn’t care about your credentials, your process, or your intentions. It cares about results.
Writing works the same way. Did you communicate effectively? Did you respect your reader’s time? Did you say something worth saying? These are the only metrics that matter in the long run.
The writing industry wants you to believe there’s some secret knowledge, some special qualification, some proper channel you need to go through. There isn’t. There’s just the work: putting useful words in the right order, one sentence at a time.
So here’s my question for you: What are you not writing because you’re waiting for permission? What idea is sitting in your head because you don’t feel qualified yet? What would happen if you started treating writing like the practical skill it is instead of the mystical art everyone pretends it needs to be?
The signal was always there. You just have to stop listening to the noise long enough to hear it.