- All three can be considered artists in one form or the other.
- All three tried to be very very secretive about their person lives.
- The public did and does everything it can to dig more information on exactly what all the three want to hide.
- And I am a fan boy of all three ( or I should say fan boy of their projections to the outside world)
Wednesday, August 19, 2009
Micheal Jackson , Steve Jobs , _why
What is common between Micheal Jackson, Steve Jobs and _why?
Tuesday, August 18, 2009
Quantitave over qualitative analysis
I will try to blog more often,not because I have something useful to say but because it will hopefully improve my writing skills.
So today's topic is - Quantitave over qualitative analysis a.k.a how bad an idea it is for a company (especially a software company) to say that they are "process" driven - almost hinting that anybody on the project is just a dispensable "resource" who can be easily replaced with another "resource".
I would like to put my disclaimers first.I have worked only on internal account projects(internal account = no real money = suckery) for the same deparment.So my views are more or less based on that experience.
Quantitave over qualitative analysis : I have seen a lot of importance given to generating numbers in my projects - how many hours worked, how many hours worked over time, how many defects opened per release, Function points etc, etc, etc.However in the real world around me I have never seen those numbers really make much difference to the overall quality of code (which is the only true main deliverable to the client). Secondly there are so many nitty gritties involved that it is not even easy measuring these numbers accurately without spending a whole lot of time and effort on it
What surely has made a difference in my projects is people.In almost all my projects, there have been a select few technical people(mostly one or two in a team of about ten) who pretty much determined the overall quality of the code delivered.For me it seems pretty clear that if you take the time and effort in hiring and keeping your best talent happy everything else will automatically take care of itself.
If the people are good you don't need a quality department telling them that they got to use a SCM system, defect tracking system , track their defects etc - The whole process becomes "common sense"
PS: Now you are wondering ,I could just have said, in a big software company there are some stupid fucking processes they follow and sometimes(especially difficult times) they treat people like trash and everybody also knows that it is not easy running a big software company and inefficiencies will creep in with scale- BUT hey I am just trying to improve my English here!
PS1:I just upgraded to IE8 and I must say it almost feels as good as Firefox - Something is either happening to me or Microsoft, I think Bing and Google are equally good, Firefox and IE are equally good - wow!
So today's topic is - Quantitave over qualitative analysis a.k.a how bad an idea it is for a company (especially a software company) to say that they are "process" driven - almost hinting that anybody on the project is just a dispensable "resource" who can be easily replaced with another "resource".
I would like to put my disclaimers first.I have worked only on internal account projects(internal account = no real money = suckery) for the same deparment.So my views are more or less based on that experience.
Quantitave over qualitative analysis : I have seen a lot of importance given to generating numbers in my projects - how many hours worked, how many hours worked over time, how many defects opened per release, Function points etc, etc, etc.However in the real world around me I have never seen those numbers really make much difference to the overall quality of code (which is the only true main deliverable to the client). Secondly there are so many nitty gritties involved that it is not even easy measuring these numbers accurately without spending a whole lot of time and effort on it
What surely has made a difference in my projects is people.In almost all my projects, there have been a select few technical people(mostly one or two in a team of about ten) who pretty much determined the overall quality of the code delivered.For me it seems pretty clear that if you take the time and effort in hiring and keeping your best talent happy everything else will automatically take care of itself.
If the people are good you don't need a quality department telling them that they got to use a SCM system, defect tracking system , track their defects etc - The whole process becomes "common sense"
PS: Now you are wondering ,I could just have said, in a big software company there are some stupid fucking processes they follow and sometimes(especially difficult times) they treat people like trash and everybody also knows that it is not easy running a big software company and inefficiencies will creep in with scale- BUT hey I am just trying to improve my English here!
PS1:I just upgraded to IE8 and I must say it almost feels as good as Firefox - Something is either happening to me or Microsoft, I think Bing and Google are equally good, Firefox and IE are equally good - wow!
Subscribe to:
Posts (Atom)