Cost Of Not Upgrading Developer’s Computer

Computers and Servers repairing snapshotMany times, there is situation where people in SMB and startup businesses do not upgrade their computers and perhaps their software tools too. Most of these businesses think that it is pretty ‘OK’ to run things as it is ,for years since either they are running the same things.And upgrading systems would add up to their cost.But they eventually forget the cost of loss of productivity of developers. This added cost would certainly pain for customers as well as it can harm your business severely.

Let me give you an example,If there is some code base of your product, which takes 3 minutes to build and compile and run on normal [read upgraded or having latest hardware and software], and you had a machine with your developer which is taking 7 minutes and project would gone up to 24weeks and developer had generally compiled solution even only 50 times per week then you are losing the productive time of 2 Person-Days. Assume, you had 8 working Hours per day.

Time lost in each Build/compilation = 7-3=4 minutes.

24 cal. Weeks = 24 X 50 X (Time lost in each code compilation) = 120 days.

24 cal. Weeks = 24 X 50 X (4) = 4800 Min/60 =80 Person-Hours= 10 Person Days].

So for 6 Calendar Months of work the organization is losing 10 Person days per developer.

Doesn’t that is good eye opener for managers? I think that is quite a lot valuable time and that it is wasted just because you had not upgraded your hardware or software system.

Sometimes, many of us forget that we are using computers just because those damn good and fast machines can do tasks faster than human can think of.

Share this post :


4 thoughts on “Cost Of Not Upgrading Developer’s Computer

  1. fernal73

    Developers usually are provided with the fastest computers. At least, that has been my experience. Because yes, they have to be more productive. Managers , usually, may ask for slower computers, not because they cannot code or develop , but because they need to run the developers program, on a machine that the client will probably work with. This paradigm may not hold true so much now, in the case of most server-side development but I am not so sure since the advent of Ajax heavy applications, RIA applications indicate that client machines might need to be decently quick.
    My two cents.


  2. lalitkale Post author

    Hi Linus,
    Thanks for adding your two cents on this post 🙂

    I think people who are obsessed with lot of metrics and measuring of productivity can look at those hidden things.One of which is shown in post.

  3. fernal73

    I would not be against metrics. You can’t improve what you can’t measure. But you should definitely know what to measure! Making sure that you measure the right thing is key to process improvements.

  4. Lalit

    I am also not against the metrics too.But because of so called quantitative methods used for determining everything and the very notion of ‘You can’t improve what you can’t measure’ is not the right way.How many Organizations focus on qualitative analysis efforts compared to quantitative analysis.

    I had seen managers,’C’ level executives trying to measure something like productivity or LOC per developer per person-day and drowning themselves into numbers loosing their precious[Productive??? :)] time.For me that doesn’t make any sense.

    All I can say is,I agree with you partially[we should know what to measure!] and I 100% agree with Martin.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s