Wow! It's already March!
In what seems like the blink of an eye, we've gone through:
- two project extensions in Los Angeles
- significant progress on another application for said project's client
- a theme park
- faux Christmas carols in Colorado's Breckenridge
- a personal project transition to GitHub
- 200,000 miles on United, and 50,000 on American
- significant fitness-related changes
- ...and more
I'm learning more than ever these days in very specific, technical categories. This is in no small part because I have the unbelievable privilege of working with some of the best software developers and consultants on the planet at ThoughtWorks. My coworkers are often willing to help, but their example alone is enough to really help push me toward continual improvement. I'm frequently finding myself in situations where the code I've written two months ago is flat out embarrassing — which is most certainly a wonderful thing. These learnings don't quite seem to fit with the majority of the 77 posts that have preceded this one, however. A trap I've fallen into is a half-written post that never ends up published because it doesn't fit the flow this blog has carved out.
A great idea that was proposed by Sumeet Moghe at the end of TWU XVIII is advice I'm finally ready to announce I'm following: split into two blogs.
So, What's The Difference?
All of the above adds up to why I've started a second blog, or created a dev branch, if you will. My intent is to have a code-centric corner of the world where I can write about improvements I'm making and hopefully get feedback on where to go next and how to make things better. As a secondary benefit, I hope to simply have a log that documents the progress of a young developer, if for no other reason than I wish there was something similar I could read while in school.
Fun Fact Cronotrons may one day be the official unit of time estimation.