Change change change

Well, first change ever. When I first started this, I thought of using it solely for the purpose of information sharing and dissemination (uhh... bombastic word, but not sure if my spelling is correct =p) but I realise that would make this blog too focused, and I'm too lazy to start another personal blog ;) so I think I shall use this place to crap as well.

Nothing much to crap about though. Even if work seems to be more, tension and stress is increasing but I somehow feel better, more at ease. It appears like I'm beginning to learn to accept things as they are and that the situation is here to stay so might as well get comfortable and excel at it. =)

Well, recently we got some fresh blood in the house, hehe.. a colleague suggested they start of by making coffee for us >:) so evil. Nah, I think we'll try to be the stern but nice kind of people. Suppose to mentor them and I hope I will be able to help them find their own self and grow but not too confident though. It's infinitely easier to share knowledge and help people who are already at ease with themselves, their goals and objectives in live and their self confidence. I myself haven't really found my identity yet and I know am responsible for guiding new people along their path. I darn sure am going to make sure I don't screw up other people's life. =|

Guess that's enough crap for now. Signing off, The Evil Saint ... or maybe The Saintly Devil, like I said, haven't found my identity yet =p

Dry dry week plus

Wow, have just started the blog and already AWOL almost a month. Have been busy sharp-shooting bugz a-plenty, unfortunately failed miserably. Why are software so buggy? Sigh, but then again, if software can be developed without any bugs, I'll definitely be out of a job. ;-)

My previous project has been finished two weeks ago however the software still full of bugs and the client has been complaining incessantly - not that I blame him since I would have done the same thing being in his shoes. After such a long debugging period with no end in sight, my boss decided to take over the debugging once and for all. Definitely NOT a good impression seeing as how I was still on probation. =p

Subsequently, I've been working on a new project, but progress has been slow going. The past week and a half have been doing some tasks which are a part of the standard software development process. Just too bad I absolutely abhor them. Well, at least I use to, now I've upgraded to merely 'dislike' status. Soooo..... what's this task that's so un-liked? Well.... the bane of programmers worldwide, paper-work.

With this being the beginning stages of the new project, obviously the kind of paper-work I'm referring to is designing the process, class diagrams et cetera. I've never really been interested in all that stuff and always leave it last but now need to learn. I wonder, for software development, would the traditional waterfall process still work in todays world of flexibility and quick change?

I've been looking at various Agile methods over the last two years and am rather intrigued by Scrum, XP and so forth but haven't really had much chance to do much other than read up on the theory and success stories. How applicable would it be to my current job? How can I start using it to try it out without needing to involve the whole team and management? After reading up on these light-weight processes, I'm still a gazillion kilometres away from any form of practical understanding.

Oh well, back to my designing work now. As it is, I actually skipped that phase of the process and started my coding already thereby causing me to be late by three days as compare to the agreed upon Gantt chart.

Bye for now, a bien tot!