First off, special thanks to Dan Cruz. I've been struggling for a while about the blogger templates. For those who'd seen my blog a long time ago, you'd see the series of changes that took place.
Anyway, I happen to be online in YM and Dan sent me a message. It's actually been a while since I last heard from here as well as from his blog. The topic about blog layouts came about and I mentioned the difficulty I've faced.
I've done so much experimenting that I think I almost lost it. So, I simply reverted back to one of the default blogger templates -- already forgot what that one was.
Dan mentioned that he faced the same thing before -- the reason he did not update his blog for the longest time between 2007 to 2008. Turns out he's been busy studying CSS and XML. :) He suggested that I do the same, but with a little help from the site here.
Ooh boy. How great was that site! They said you will WOW when you explore the site. Well in my case, just saw the first page and already I said WOW. :) I downloaded one of the templates there. Hence, the look that you are seeing right now -- the super-customizable Professional Template.
This won't be the final look of this blog. Afterall, there's always room for improvement. But using the templates from the site is certainly a good place to start.
Well, I'm done here. It's 4AM here and I haven't slept yet. Well, technically I slept at around 3PM yesterday up until around 7:30 PM, which in restorspect, might explain why I'm still awake at this time. :)
Anyway... I think I'm rambling in my post already. Thanks for reading! :)
Showing posts with label project. Show all posts
Showing posts with label project. Show all posts
Wednesday, March 11, 2009
Monday, June 16, 2008
Project aftermath...
Finally, after months of anticipation, the project had come to pass... and we all survived!
This is perhaps the biggest project I am involved in my entire career. I wish I could say that everything was smooth sailing, but that would be a lie.
So our team were there on site at 10:30 AM last Saturday, but people were already behind schedule; we could not start unless the first team has finished their task. All preliminary tasks on our side have been done, so all that was left was to wait for the other team to finish their task. So we waited patiently... And waited... And waited some more.
Around 3:30PM, that's when we had our first issue. Easily resolved, no sweat.
About 30 minutes later, then came the seemingly never-ending parade of issues... We had a list pasted on a wall were all the problems / issues encountered are listed. For the next 2 minutes, 10 issues are listed and there were no signs of it letting up. Thankfully it did stop, but there were already too much on the list and we were stuck with these problems for the next hours.
Bottomline, we finally called it a day around 2:30 AM. Workarounds were in place, although there are a couple more unresolved issues. We had to come back the following day. (Or technically, later that day since it's past midnight.)
We returned to work around the 11 AM, refreshed but not as eager as we were the previous day. Thankfully, all of the outstanding issues have been resolved around 3:00PM. Finally! We went home very elated that the project is finished.
While sitting in front of the TV, I realized a couple of things; first, I'm watching "Sunday" shows which means it's already Sunday; and, second, we have to go back to work the following day (to provide support in case problems do occur during normal production hours). I feel shortchanged. If you look at it, we would be working for twelve days straight (the 10 normal working days in two weeks plus the two weekends). Aint exactly your ideal scenario!
So today we returned, still not very enthusiastic. Problems did occur but thankfully these were resolved easily. We would be staying put for the rest of the week to ensure that any and all incidents are dealt with.
Aside from that, I had to update all the documents that are affected by the changes. Aside from the two documents I created for this project, my boss assigned me to update five other documents affected. I know for a fact that nobody is assigned to update one other document, so I plan to do that as well.
All in all, just another fine week. :)
This is perhaps the biggest project I am involved in my entire career. I wish I could say that everything was smooth sailing, but that would be a lie.
So our team were there on site at 10:30 AM last Saturday, but people were already behind schedule; we could not start unless the first team has finished their task. All preliminary tasks on our side have been done, so all that was left was to wait for the other team to finish their task. So we waited patiently... And waited... And waited some more.
Around 3:30PM, that's when we had our first issue. Easily resolved, no sweat.
About 30 minutes later, then came the seemingly never-ending parade of issues... We had a list pasted on a wall were all the problems / issues encountered are listed. For the next 2 minutes, 10 issues are listed and there were no signs of it letting up. Thankfully it did stop, but there were already too much on the list and we were stuck with these problems for the next hours.
Bottomline, we finally called it a day around 2:30 AM. Workarounds were in place, although there are a couple more unresolved issues. We had to come back the following day. (Or technically, later that day since it's past midnight.)
We returned to work around the 11 AM, refreshed but not as eager as we were the previous day. Thankfully, all of the outstanding issues have been resolved around 3:00PM. Finally! We went home very elated that the project is finished.
While sitting in front of the TV, I realized a couple of things; first, I'm watching "Sunday" shows which means it's already Sunday; and, second, we have to go back to work the following day (to provide support in case problems do occur during normal production hours). I feel shortchanged. If you look at it, we would be working for twelve days straight (the 10 normal working days in two weeks plus the two weekends). Aint exactly your ideal scenario!
So today we returned, still not very enthusiastic. Problems did occur but thankfully these were resolved easily. We would be staying put for the rest of the week to ensure that any and all incidents are dealt with.
Aside from that, I had to update all the documents that are affected by the changes. Aside from the two documents I created for this project, my boss assigned me to update five other documents affected. I know for a fact that nobody is assigned to update one other document, so I plan to do that as well.
All in all, just another fine week. :)
Thursday, March 20, 2008
Busy Thursday
I've never been busy like this since I was the duty network engineer for the entire December '07. I've been away my desk for most of the time, much even less time to do the usual blogging and Internet surfing... Oh well, it's one of those days... Or rather, one of those weeks...
Well, it's not like I had a good time during Holy Week last time I was in the Philippines. Holiday or not, as long as it is a day between a Monday and Friday, we go. Here at least, we don't have to go this Good Friday. :)
Particularly busy was this Maundy Thursday. With this being the last day before the upcoming event this Monday -- the campus will be holding a laptop configuration event thingy for all the students; lucky kids! -- everyone was scrambling to get all things ready.
Sadly, though, someone has messed up the configs of some switches (someone deleted the damn VLANs) causing all the test laptops connected to it to be disconnected. Well, at least that was easily resolved once the "damage" was seen from the switch-side. I had to go to the switch, though, which was holed up in a a very small, cramped, and somewhat smelly room.
I wanted to find out what the hell happened that the switches got messed up! Oh well... Too tired to track down the who, the how, or the why of it all.
Earlier...
So let's see... I had to carry a switch from my place to the event site which was about five buildings away. I had to get the keys from the other support center which was another two buildings away. The switch is not that heavy -- just a small 48-port switch... I think it was a Cat3750... Well, doesn't matter.
When we're done with the event, I'll play around with the switch for a little while... Better to experiment and do tests on spare switches than the ones in production.
There were also these three switches in computer laboratory which cannot be accessed remotely via CiscoWorks servers, telnet, or SSH... Well, okay SSH will not work for two of those which are the old Cisco Catalyst 3500XL switches. Still, it's getting in the way of me getting rid of my three-month-old task of upgrading the IOS images of all the hundreds of devices in the network -- did I mention they have hundreds of devices? Hehe...
Hmm, I actually learned a great deal about that... Maybe I'll post it on my other blog.
Well, it's not like I had a good time during Holy Week last time I was in the Philippines. Holiday or not, as long as it is a day between a Monday and Friday, we go. Here at least, we don't have to go this Good Friday. :)
Particularly busy was this Maundy Thursday. With this being the last day before the upcoming event this Monday -- the campus will be holding a laptop configuration event thingy for all the students; lucky kids! -- everyone was scrambling to get all things ready.
Sadly, though, someone has messed up the configs of some switches (someone deleted the damn VLANs) causing all the test laptops connected to it to be disconnected. Well, at least that was easily resolved once the "damage" was seen from the switch-side. I had to go to the switch, though, which was holed up in a a very small, cramped, and somewhat smelly room.
I wanted to find out what the hell happened that the switches got messed up! Oh well... Too tired to track down the who, the how, or the why of it all.
Earlier...
So let's see... I had to carry a switch from my place to the event site which was about five buildings away. I had to get the keys from the other support center which was another two buildings away. The switch is not that heavy -- just a small 48-port switch... I think it was a Cat3750... Well, doesn't matter.
When we're done with the event, I'll play around with the switch for a little while... Better to experiment and do tests on spare switches than the ones in production.
There were also these three switches in computer laboratory which cannot be accessed remotely via CiscoWorks servers, telnet, or SSH... Well, okay SSH will not work for two of those which are the old Cisco Catalyst 3500XL switches. Still, it's getting in the way of me getting rid of my three-month-old task of upgrading the IOS images of all the hundreds of devices in the network -- did I mention they have hundreds of devices? Hehe...
Hmm, I actually learned a great deal about that... Maybe I'll post it on my other blog.
Tuesday, March 04, 2008
My new project blog
I just launched a project blog that I've been wanting to put up for a long time now. You can find it here:
Networking Stacked Knowledge
This will serve as a quick reference for me, as well as a sharing blog for everything IT networking.
Please feel free to send me comments, suggestions, requests, questions or whatever regarding this blog.
Thanks!
Networking Stacked Knowledge
This will serve as a quick reference for me, as well as a sharing blog for everything IT networking.
Please feel free to send me comments, suggestions, requests, questions or whatever regarding this blog.
Thanks!
Subscribe to:
Posts (Atom)