969 words • 4 minute read.
So I decided to start a blog. But why?
You mean other than the usual reasons of fame, fortune and endless glory.
Ok, so maybe not fame, fortune or glory… but I do have a reason.
While finishing my dissertation, I realised that I really enjoyed the writing process. There was something about just getting the words out of my head and down onto paper (you know, metaphorically speaking) that felt therapeutic.
So, after I had got myself into the tech industry, and finally finished my dissertation (after 6 years of part-time university learning Software Engineering), what next?
Well… I’ve decided to start a blog 😂, but why I hear you cry…
There are a few reasons; I feel like I have been an iOS developer long enough now to kind of know what I am talking about…sometimes at least anyway, and starting a blog covers a few different angles.
It helps out anyone who is scouring the internet looking to either just read for the fun of it or solve a problem and doesn’t want to just ask Chat GPT. I still enjoy reading blog posts on Medium, Dev.to and various other sites, both for curiosity and when I am looking for different ways to solve (normally a development) problems. So I do think there is still a space for writing that isn’t written by AI (for now at least anyway). Writing about problems I have faced at work or in personal projects, I think, is a good creative outlet, and it means I get to share my problem-solving process and outcome with the rest of the dev community
It also (in a selfish way), helps me to further my quest for iOS and software engineering knowledge. I get to explore topics I want to learn more about, and then share my knowledge with anyone else who wants to read about it. Who doesn’t love a good TLDR about a framework or API they haven’t used and just don’t have the time (or just generally can’t be arsed at that present moment) to dive into the docs to find out more.
Let’s face it, as developers, we write for a living (words at least anyway, var, let, someVariable etc…) but soft skills are underrated. Being able to write good documentation that is short, concise, and not too verbose, explaining how something works and why it has been done this way without writing 3 paragraphs is a good skill to have. These skills are also important for PRs, updating tickets with evidence, tech round table presentations. The list goes on.
As well as making sure I know what I am talking about, blogging can also help others including future employers to know what I am talking about (just for the record I’m not in the job market, but you never know what the future holds). It also helps to show that I take an interest in what I do, for me development is more than just a job, it’s a BIG hobby, and something I spend a lot of time doing and learning about.
Finally, you never know what the future holds. By training new muscles and learning new skills, it all compounds and helps me to become a better developer, writer, and person all around.
So, here’s the TL;DR on why I’m diving into blogging:
Thanks for stopping by, I hope you enjoyed it 🙂.