Skip to content

Latest commit

 

History

History
28 lines (15 loc) · 1.81 KB

68-technically-considered-writing.md

File metadata and controls

28 lines (15 loc) · 1.81 KB

Technically Considered Writing

#writing, #watercooler, #beginners, #career

Photo by Kelly Sikkema on Unsplash

Write to document what you're doing now, finding relief from its gripping subject. Set a publishing date as motivation. And where there isn't inspiration, tinker with the process of writing. Undoubtedly the muse will return later.

What you'll write will become fuzzy. Re-read your past writing to remember where you were and laugh with the people you shared it with. Writing transmits a once-lived perspective and style.

Writing on a matter is a loop that spirals in your mind. But not after publishing it. When moving to the next, which will inevitably occur, the previous writing is a compressed artifact for a future reader of your earlier thinking.

Were you clear? Did you write?


Dev reader, you came for write engineering: Here's how:

Writing as a System

Higher-res version here. Subscribe below!

Social Post

Have you #written today? Find pure #exuberance through my words from eight write-ups. Then, get #technical with a #writing #flowchart. But the question remains, where you clear?

dev.to

#writing, #watercooler, #beginners, #career, #fun