so today, I finished one of six course of HP's so called software development methodology which is SLIM. The whole training course reeks of waterfall methodology. Always talking about processes and tools and how those tools helped them to save time and budget. In my opinion and observation, those metrics that they used are so shallow and there are a lot of possibilities on how they could arrive to the conclusion.
Which makes me wonder did they never read those books written by those famous and successful software developers? for example, The Mythical Man Month which explains extensively on why we should not add more people to an already late project.
They mentioned I the training course that when they implemented SLIM, the numbers of defects went significantly down. But as I observed from the slides, that was in the last phase which could easily mean that logically most of the other requirements have already been met successfully so why would they need to change the source code further? And regarding the so called work life balance can be easily achieved if the whole organization implements agile and lean methodology at the first place. Agile and lean protects the developers from unnecessary problems and allows them to focus more on developing the product.
On a side story, a senior colleague warned me that I'm under serious scrutiny as the manager often saw that I'm on facebook 'all' the time. Did they never heard of focus and time management techniques such as the pomodoro technique? I guess that comes naturally when you stay too long in a traditional waterfall management.
Conclusion: waterfall is evil and should be ceased from practice. Adopt the Agile Methodology today!
Thursday, July 22, 2010
My take on HPME and SLIM
Sunday, July 18, 2010
Hey dumbass!
Bloody hell! Stop posting comments in chinese and stop trying to promote your stupid porn site will ya? Better if you just stop visiting my blog. Sorry to say, you and your chinese porn site sucks! Now just go to hell!
Friday, July 16, 2010
Well, whatever.
This new company that I serve is seriously messed up. Too many things that I'm not satisfied with to list here. I mean come on! It's been nearly a month since I worked here but I still don't have access to too many stuff that I should already have access to. The active id for example. Why the heck do I need to request access for it twice? And about the claim for my employment buy out process, why the heck does it says that I haven't keyed in my bank account details yet when I already keyed it in 2 days ago? Why do those people in india have to key in my bank account to another system? This is so inefficient and stupid.
You tell your employees that you value them but these things that you're doing really contradicts to what you just said. I really don't get why a lots of people wants to work here.
This place is so overrated.
Sunday, July 4, 2010
The grass aren't always greener on the other side..
I got cheated by the HR too. They mentioned that the Annual Leave is 15 days. But they never mention that there is about a week of forced leave during the end of the year for business closing because of Christmas. I don't celebrate Christmas and I do not need 1 week of holiday for it. Talk about being honest.
They promised me that the job will be as interesting and as challenging and the work environment would be as exciting as what I had in my previous company. But just after a week of being here, I don't feel excited at all, I found out that the job doesn't really need my deep technical skills and I heard from one of the colleagues that there will be no real programming task as the framework that they are using are already catering for that via the use of templates and what we are going to do are just plumbing. I really wonder why do they really need people with my knowledge around. Now this is just boring.
They told me that the organization have their own version of development lifecycle which is a mixture of Waterfall and Agile methodologies. I seriously went 'WTF?'. Those two cant even mix together as both are of different ideologies and different focus. Fine, they are derived and incorporated from Agile but seriously, you can't just say that you are using Agile. Adopting from Agile doesn't make it an Agile! and just by a glance I can tell that they are going against all four points of The Agile Manifesto. So, tell me, how can you say that you can call it Agile when you are going against the manifesto itself? Now, this is getting annoying.
Well, now, all I could say is I wished I never did all of this. I miss all the things that I enjoyed previously. I miss working with people that are smarter than me.
Well, lesson learned: no matter how big and prestigious is the organization, all of it are just talk unless they can really prove it. I guess the much more fatter pay doesn't really guarantee happiness at work. Well, I'm going to give it a chance and challenge myself whether I can change the mindset of at least my designated team. It's hard to work with people that doesn't share the same passion on software development.