I know this post is a bit late… ok, really late. 2014 proved to be a very full and active year, marked by the arrival of our new daughter mid summer.
My daughter passed out with mama after a busy day at the farmer’s market. It’s as if the Chinese fortune cookie knew.
Checking out the river walk in San Antonio.
Happy Halloween from an inquisitive little bee.
I never fully appreciated how much one’s schedule will change when a child is thrown into the mix, but I wouldn’t trade it for anything.
Ok, down to the business at hand.
This past April, I attended the UofI Web Conference. This was the first conference I’ve attended that was directly applicable to my current job… and it was excellent! What follows is a quick brain dump of my notes from the conference.
One of my biggest take-aways from 2013 was that I don’t stop to re-evaluate my situation often enough. So, my biggest goal is to check in on my progress in July rather than wait until December. With that said, here are my goals for the first half of 2014: Continue reading
The time has come to look back on another year. 2013 was exciting for me as I started my new job as a web developer at a local web consulting company Pixo, and boy was I ready for it. There were a lot of exciting new things to learn, but one thing I know I didn’t do was to stop and re-evaluate my goals I set at the start of the year. That said, there is no time like the new year to look back for a little self-review…
I never really got New Year’s resolutions, it always seemed kind of arbitrary to me. However, I am appreciating more the periodic reviewing/setting of goals for one’s self. Time to learn from the past. How about it 2013? Continue reading
While setting goals is important, following up on them to evaluate progress is equally important. I don’t want to get lost in over analyzing, but I did want to see where I succeeded and where I failed. Continue reading
“Although practicality beats purity.”
– from the Zen of Python
What started off as a step toward alleviating excessive journaling of temporary data structures in our system, ended up exposing a handful of cases where they were actually used for persistent data. When we made the switch within our data base environments to turn off journaling on this set, some of these data structures disappeared unexpectedly. Once we realized what had happened, the only course of action was to search the code base for these data structures, restore their data, and rename them so they would be permanent memory again. Continue reading