For every person joining tech, the trick is to explore. I realized that everybody felt that they needed to be able to code to join tech, and that's its beauty: technology is broad and you will always find your niche.

Whether you're a law student looking to find footing in tech, or a product marketer, there will always be something for you, as long as you know what you are looking for, and a community that will help you. You simply have to find your purpose and your passion, and also do intensive and/or extensive research.

I realized earlier on in my career, that as much as I like coding/ learning how to code, I preferred writing about code. I figured systems analysis was what I wanted, and I recently started checking out technical writing.

Writing about code or tech related subjects is understanding the various elements that contribute to it; The designs, the lay out, what each specific program is supposed to do, and who will use it. If you understand that, it is easier to put it into writing and communicate with end users of the product, or people simply interested in what might be happening if you also understand it.

Documenting and writing after finishing up on my projects, or writing code, is my favourite thing. I knew I liked the thought process that happened during the timeline of each progress, and what led to using a particular system/ software to accomplish that. I would sit with colleagues and ask them to talk to me about their work; some would and some would not, because they found it difficult to explain. I mean, they know their work, they just couldn’t explain, but I did know how, and I decided to be at the forefront with the end user, putting them through gathering user experience and giving effective feedback to my colleagues.

I love coding, I love technology; but I wanted to be the link between developers and users, rather than a developer. I wanted to write about my developing process, I wanted the best of both worlds, and so I started to work towards it - I started writing about code.