Finally! I’ve bitten the bullet and made a respectable (in my opinion) web presence for myself aside from my post-college, name-based websites in the past. Not only do I have a website to gladly hand off to potential clients, but I plan to build an issues archive for myself in the form of the site’s blog. Now, I am notoriously terrible at documentation and/or journal entries of any sorts. I rarely make lists; I don’t like diaries; and I like to move on to the next problem as fast as possible. Though, I’m starting to notice the times in which I encounter a problem that I’m quite sure I’ve tackled in the past. A little deja vu in a workday. Suddenly my “make the best of your time and push forward” side has a conflict of interests. Turns out it could be more efficient to mark down a learned lesson than to hope it looks familiar later down the road. Plus, like Oppenheimer said, the best way to learn is to teach it!
Or…at least tell about it in a blog. Perfect!
As much as I love to say, “I have NO idea how this code works but DON’T TOUCH IT!”, I think it’s best to start understanding each step with a little added effort in writing it all down. My younger developer self is cringing at my maturity and putting money on 10 or fewer posts.
Just another reason to keep at it :)