<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Imieni Odijie</title>
    <description>The latest articles on DEV Community by Imieni Odijie (@imieni).</description>
    <link>https://dev.to/imieni</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2230275%2F629b67ab-f566-4e3a-96e4-3f8da87aaf47.jpg</url>
      <title>DEV Community: Imieni Odijie</title>
      <link>https://dev.to/imieni</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/imieni"/>
    <language>en</language>
    <item>
      <title>Beginning as a Technical Writer</title>
      <dc:creator>Imieni Odijie</dc:creator>
      <pubDate>Mon, 25 Nov 2024 16:30:31 +0000</pubDate>
      <link>https://dev.to/imieni/beginning-as-a-technical-writer-j50</link>
      <guid>https://dev.to/imieni/beginning-as-a-technical-writer-j50</guid>
      <description>&lt;p&gt;Hello!!!&lt;/p&gt;

&lt;p&gt;So here I am, starting on a clean slate, delving into another field in tech as a Technical Writer.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F02dgy13nhddp92hp2sht.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F02dgy13nhddp92hp2sht.gif" alt="Image description" width="498" height="498"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I started out as a developer, backend developer. I loved writing codes, I still do. I code in PHP and Python. &lt;/p&gt;

&lt;p&gt;A friend of mine, when he heard I was delving into technical writing asked me, "What about your coding?", and I responded, "Coding is in my blood, nothing can take it away. I'm still a backend developer through and through". &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqq9siskfek5nq16emvfn.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqq9siskfek5nq16emvfn.gif" alt="Image description" width="640" height="522"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;So, how did this journey or interest into technical writing begin?&lt;/em&gt;&lt;br&gt;
It is a common saying that programmers hate writing. Well, I guess I grew into loving to write out of necessity.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;A quick background story...&lt;/em&gt;&lt;br&gt;
I worked in a company where we had limited man-power. The company got a project that required a user manual/technical documentation for the application we were to develop. I was the developer, but no technical writer. I had no choice but to adjust to that role, howbeit grudgingly.  I had no idea I was actually technical writing. I finished the manual and it was good and easy for the users to understand. We had about two more projects that also needed users documentations and, once again, I had to fit into that role and deliver. &lt;br&gt;
I discovered I loved to program and write also. &lt;/p&gt;

&lt;p&gt;Fast forward to some months ago, a friend sent me a job vacancy for a technical writing position and my first thought was, "I'm not interested. I want to code not write". But after much advise, and looking through the job role, I decided to apply and suprisingly, I was called for interview and to cut the long story short, I got the job as a technical writer for my new company. &lt;/p&gt;

&lt;p&gt;I'm no expert yet, still learning, unlearning and relearning. &lt;/p&gt;

&lt;p&gt;So join me, as I document my technical writing experience and journey. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2pbvufnazw2bvvahbup9.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2pbvufnazw2bvvahbup9.gif" alt="Image description" width="400" height="314"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>technicalwriting</category>
      <category>beginners</category>
      <category>developer</category>
      <category>developerturnedtechnicalwriter</category>
    </item>
  </channel>
</rss>
