I have a background in tech. Because of that, technical content writing comes naturally to me.

I wouldn’t say technical writing is as satisfying or fun to write and read as other types of content. Still, it’s not about what your intellect wants, but about what your intellect needs.

Before starting to write content professionally I wrote a large paper on something technical.

When I did it, I thought that the only use for that paper was in the odd case of someone wanting to do what I did, to have a guide.

I thought that it was important for me to document my two weeks working 12-14 hours to make an obsolete technology come back from the dead.

It was hard and the road was full of bumps, but I achieved my objective.

Now, this wasn’t hard as deploying a website as a first-timer or configuring either the .htaccess of a website or some DNS records without knowing what one is doing.

No, this was harder, by many orders of magnitude. The specifics of each moving part of that project were of the most forgettable kind possible of strings of data, so much, so that during day two or three into the project I started carrying a diary.

An almost forgotten technology like the one I was tinkering with was so different from what I was accustomed to for the last decade, and I had forgotten so much of what I knew about it, that I was doing progress at a slug’s pace.

Personal forgetfulness coupled with the change in the way of doing things forced me to relearn a lot of the things that I previously thought I wasn’t going to need again. It didn’t annoy me because this was just a fun project.

I think the diary was a coping mechanism, to add some livability to my life because it was a day after another of problems.

For a moment, it was hell. I kept on writing the important things in the diary, with a lot of passages that didn’t make it to the technical paper, because they were just thoughts on the page that had little to do with the technical part.

After like four-five days feeling hopeless and always having the project subdued by a problem things started to even out.

Previously, it wasn’t that the problems lasted one or more days. The problem was that fixing an obstacle either brought new ones or broke something that was fixed previously. After a battery of refactorings, re-dressings, patching, and implementing kludges I could say everything at the local level was a-go.

Yet, the notepad text went on. I couldn’t have possibly reached the point of taming the bugs storm without it. And it had served me beautifully when the second week of trouble started to bring the system down.

I wouldn’t say that because of my background in tech I have a winning, scientific method of writing technical content that can be considered journal-grade.

What I as my value as a technical writer is simply an engineer’s general outlook on life and specifically an engineer’s approach at gamifying problem-solving.

(Reading time: 3 - 5 minutes)

 

“Blockchain for Dummies” by Tiana Laurence is a standard For Dummies book that touches the subject of cryptocurrencies and blockchains with a generalist approach.

It’s five parts, 29 chapters.
 
  • Part 1 Getting Started with Blockchain
  • Part 2 Developing your Knowledge
  • Part 3 Powerful Blockchain Platforms
  • Part 4 Industry Impacts
  • Part 5 The Part of Tens

 

Connect on Social Media

 

 |  |

Please publish modules in offcanvas position.