Lorem ipsum dolor
A placeholder text used by designers all over the world when they’re utterly clueless about what to do next, I’m not far behind. This is supposed to be an introduction post for Regular Dev, but I’m still figuring it all out.
Regular Dev is a newsletter I started to paint the actual journey and struggles of a real-life software engineer; if it helps, I am a Nigerian Software Engineer, and the tech space in my part of the world is deserving of a Netflix series, rightly because everyone is an industry thought leader but mostly on Twitter.
Why this, why now?
I am not a thought leader, you need a lot of actual original thoughts to be called that but I am a “real-life” software engineer and I can say for free that it is a lot different from what you see in mainstream media and there is a huge disconnect between expectations and reality for those coming in or already in tech. This newsletter will try to be that bridge.
What kind of community am I looking to build?
I’d hate to have any form of Gateway filter. Gatekeeping is bad unless it’s on an API. Now you may or may not have understood the references above, so let me explain:
1. My Audience
A backend engineer gets the above reference and I’d bet would even smile a little but not everyone does backend. The issues I would begin to talk about are not specific to any aspect of software engineering, it may be a little biased but they really are issues familiar to everyone in tech, and what’s more, it’s not specific to continent or country. Whether you’re a Designer or a DevSecOps person, you’re my audience, especially if you like honesty and have an open mind. I’ll do my best to be a perfect load balancer (can’t promise I’d obey the laws of Round Robin though) - “reference again - sorry!”
2. What should you expect?
Expect me to light a few wildfires and make absolutely no attempt to quench any - street word for that is Violence! - A ‘streeter’ word is Vawulence!
I’d also strictly stick with real-life examples in everything I talk about, I’d probably use a lot of pseudonyms though, but everything will be from experience, and if my experience is not enough I’d borrow from books, and mentors. What I aim to describe is the real-life journey of the career of a software engineer, from L1 all the way to L9 (as I experience it myself).
I like feedback a lot too and I’d ask for them a lot, for instance:
an out-of-context poll, feel free to vote but then you’d have to promise me you’d see a therapist if you pick option one.
3. What you should know
I write with a lot of cheeky references, I might go overboard sometimes and talk about anime, but why you don’t love anime deserves another blog.
I will use pictures sometimes to illustrate what I mean, and maybe GIFs too. Think - Head First Tech!
Finally
Well, that’s it! Expect me soon. If you’d like to be on my mailing list, there’s a subscribe link at the bottom of the page. You can also share this post so it can reach even more people. Gracias!
PS: I wrote something I’d like you to read, I published it on Medium last week, here’s the link.
That out of context poll😂👌🏾
Beautiful!