Writing about Writing Part 5
Okay, don't worry. No rant this time. This is a celebration! I finally have a writing setup that works for me, on every level. And as I suspected for a while, Markdown was the answer. So was Typora.
You can see my entire journey here:
- Writing about Writing
- Writing about Writing Part 2
- Writing about Writing Part 3
- Writing about Writing Part 4
Just when I thought it was over, I found one more step I hadn't considered, the ultimate test for my setup.
I've started to use it at my job for technical writing.
A New IT Adventure
So, a new work opportunity showed up out of nowhere. One of our consulting teams needed a lead ERP analyst as soon as possible. A welcome new challenge.
This new role requires me to write my own technical documentation, specs and proposals.
Because AI is everywhere now, we don't have templates for technical documentation anymore. For me, this sounds like an exciting writing opportunity.
And it begs the question: Why use Word when you can use Typora?
Full focus on the content. No formatting hassle, no clutter. Beautiful typography.
My theme? The default Typora GitHub theme with one single change. Alegreya font family. Chef's kiss.
The final result? Proposal documents and specs that look sublime.
End of the Search
Five episodes and four and a half years later, the search is over. I don't think about my tools anymore, and that's the whole point. Markdown and Typora get out of the way, and I just write.
Novel chapter late at night? A technical spec at work? Well, it's the same flow: open, write, export if needed, done.
So if you're still searching for the perfect writing setup, try plain text and/or Markdown. It might be all you ever needed.
Now, if you'll excuse me, I have words to write. See ya!