As a professional developer, I tend to both write and review a LOT of code every day. Add to that my general interest in development outside my day job, and that number of little monospaced characters looked at in a given day goes up exponentially.
Recently, I’ve felt (for the first time) that I really have my footing under me in a career, and my constant impostor syndrome is a little quieter. This has led me to start looking into development projects outside my usual Salesforce projects for my day job. Python, React Native, C#, Unity engine, and more have caught my eye for one reason or another, and yet I have no personal record of what I’ve learned, what I’ve built (or tried to build at least), and the additional lessons learned from those experiences.
With all that in mind, I decided to actually build out this blog on my website, which until now has been an empty page with nothing to say. And a year from now, who knows, maybe this will be the only post on it.
However, my goal is to use this space as a chance to record my thoughts, experiences and lessons learned from my time spent on any number of projects, coding languages, and experiments so that I can look back and at the very least see how far I’ve come.
Each post in this devlog series should be categorized, indicating if what I’m posting about has to do with a specific project or simply a learning moment or experiment. I’m hopeful that keeping this content as specific and organized as possible will give my future self an easier time sifting through my ramblings, and anyone stumbling on this blog a way to understand what the heck they’re looking at.
I also plan to tag each post with helpful additional information, including what coding language(s) the post is dealing with, what context/framework/engine I’m working in, if applicable (Unity? Salesforce?), and any other supporting information that might be helpful.
Will I stick to this organization? Will I redesign it in a week? Will I scrap the whole thing and turn this into a freeform poetry slam blog? The world may never know.
It’s Dangerous to Go Alone!
I plan to leave the comments of these blogs open so that if someone happens to have a question, feedback, or find something here useful, they can respond. Granted, I’ll also have every spam filter I can find enabled, as every WordPress blog post I’ve ever published usually gets slammed with spam comments within 5 seconds of publishing, but here we are.
Generally, expect comments to be open and discussion to be encouraged.
The Way Forward
Will anyone else’s eyes fall on these posts? I’m 99% confident that the answer to that question is a resounding NO, but if you’ve found yourself here, welcome. I hope you can learn from the guaranteed number of mistakes I hope to record here. Maybe a win or two, if I’m lucky.
So now it’s time to buckle up, crack my knuckles, and jump back into whatever project or experiment I have cooking at any given time, and try to make magic from series of letters and numbers on a glowing screen. Wish me luck!