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!
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!
posted by CodeOfMine at 5:19 pm
0 Comments:
Post a Comment
<< Home