aggregated thinking

In my previous employment, I didn't have any problems with submitting reports, practically because we used a time management/monitoring tool and the reports sort of generated by themselves. So when submitting daily reports isn't the norm here at the unit, quarterly reports become quite tricky. I've resorted to referring to Google Calendar as most of the stuff we do are usually scheduled. I've also thought of logging everything on a text file and have pelican publish this to my website. Meantime, my reading list for the day as I decide on a workflow that will allow multiple teams to work on the university website: http://www.sitepoint.com/one-click-app-deployment-server-side-git-hooks/ http://stackoverflow.com/questions/425692/what-is-your-preferred-php-deployment-strategy https://www.digitalocean.com/community/tutorials/how-to-automate-php-app-deployment-process-using-capistrano-on-ubuntu-13

In a month's time, I would be transferring offices again. I started from a very technical department, under the administration cluster. A year and about 3 months later, I was given the privilege to transfer to one of the most influential and authoritative departments in the academic cluster. It was still a split engagement, with me going back and forth these two offices. And for almost 2 years, I improved processes, handled, battled, and took care of hundreds of scenarios, cases, and situations that seem to always come with the university seasons. I became cognizant of academic procedures and with this knowledge came the understanding of many realities that I vowed to try to fix, given the chance, and if I can. I will miss being up to my neck deep in operations and in SLMIS. But I think I will miss more being in the company of great people who, inspite of erecting a facade of sternness in all their dealings, turned out to be really cool and happy persons. I will always have the...

By 2016, five higher education institutes (HEIs) here in the Philippines will be integrating Technopreneurship as an offered elective for their Engineering programs. I am quite thankful that the higher education authorities have included my alma mater. More than being the center of trade in Northern Mindanao, the strategic location of our city makes it the best option for I.T. companies to build or expand in. While the article specifically mentions entrepeneurship training for future engineers and that inclusion will be done in the Engineering curricula of 5 HEIs, I feel that this is severely limiting the beneficiaries (e.g. the graduates, and ultimately, the HEIs) of this inclusion. The scope of Technopreneurship demands its inclusion not only in Engineering programs, but in Business Management (Business Administration, Financial Management, etc) and Computer Science (Information Management, Software Engineering, etc) as well. On the other hand, I think these may just be pr...

I didn't think there was going to be any hope for my early 2011 MacBook Pro, which had GPU-related problems after only about a year of use. The only obvious option I had was to buy a replacement laptop. But Apple seems to have been receiving a lot of reports that they've launched a repair progam that will fix the graphics problem for free. If you bought a 15-inch or 17-inch MacBook Pro between early 2011 and end of 2013, as well as the first two generations of the Retina models, you're in luck. The program became available to the US and Canada last February 20, and would be available to other countries by February 27. These are the affected models: MacBook Pro (15-inch Early 2011) MacBook Pro (15-inch, Late 2011) MacBook Pro (Retina, 15-inch, Mid 2012) MacBook Pro (17-inch Early 2011) MacBook Pro (17-inch Late 2011) MacBook Pro (Retina, 15 inch, Early 2013) Not sure if your model is included in the list of affected products? Use this Check your Coverage tool ...

Someone's been busy with the phone in the backseat.  

I just made the first step towards moving my whole blog to GitHub and going all static! Content is generated by Pelican , a static site generator, written in Python. Why GitHub, you ask? While I can always push the static content to any of my existing web hosts, there's a touch of geekness in writing using my favorite editor and publishing by git commits and pushes; thus GitHub. Also, it's this year that I'm planning to pick up Python programming again, for devops reasons. I don't actually remember the last time I was this excited to post an update!

First time out for 2015.  

Earlier today we scheduled the racking of our old C-Class HP BladeSystem. It used to be wrapped in its own enclosure with wheels to boot, but it didn't make sense to have it stand outside the cabinets. So we gave heads up and asked some guys to stay behind after office hours. Thanks to Mona, Eric, Jing, Tim, and Mark(?) for the assist! Next up, the classic IBM BladeCenter!

The day's just begun and I'm already up to my neck with work. But I'm not complaining. At least it's server stuff and not some other crap!