Categories

Tag Cloud

Chat With Me

Sponsors

Powered by Coretechnique Systems Proudly Pinoy!
Rate this post: 1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)
Loading ... Loading ... |
  • E-mail this story to a friend!
  • Digg
  • Reddit
  • del.icio.us
  • Twitter
  • Slashdot
  • Facebook
  • MySpace
  • Google Bookmarks
  • DotNetKicks

On the High Turnover Rate of Software Developers or How to Retain your Best Software Developers and Programmers


_resign It is not exactly news that programmers love to quit their job. It is an industry-wide obsession. The annual turnover rate for the High-Tech industry in 2008 is a little bit above 20% (2 out of 10 employees quit every year). A typical programmer on a typical software company stays for about 23 months on average. For an employer, these figures are scary – especially if you employ skilled workers such as programmers and software developers. High turnover rates of skilled professionals can pose as a risk to the business or organization, due to the human capital (such as skills, training, and knowledge) lost.

Having been a newbie software developer (and I’m still fairly “new”), I did not understood why software developers in our company are quitting. Having been a fresh graduate, I was, then, still amazed by the fact that there are people out there in the real world that will pay me real world money just to write code – a hobby that I will do for free. I was puzzled. We are working in an environment that fosters creativity and innovation, a company that strictly subscribes to the “programmers’ bill of rights”, and a company that scores high in the Joel Test (11/12).  Those, plus the fact that we can surf Facebook anytime and drink all the brewed coffee in the pantry, made me believe that this is the best company to work for locally; it made me believe that anyone leaving our company is insane.

_1783-Hackers_and_Painters_Big_Ideas_from_the_Computer_Age Just a few months after starting my job (I had my internship there for 6 months), one of the bestest programmer I know (he’s actually a “software architect”, but hates being called one), my mentor when I was still an intern, filed his letter of resignation. This guy is one of the most passionate programmer I know. He gets it. Paul Graham classifies him as a hacker and he actually worked for Microsoft (in Redmond, not the local whatever-they-are-doing-there branch).

For some, asking people why they quit their job is taboo; I actually enjoy having those type of conversation. Gives me insight. So I asked the fallen hacker, “Why did you quit?”. He pointed to the picture of his new born baby (his desktop wallpaper) and said with an enthusiastic smile “He is my new priority”. He then explained to me, in a fashion that I would understand, why working overseas means “better opportunity” for his family. Being a bit unconvinced with his explanation, I asked him “Is that all? Better opportunity?” and he replied back with a playful smile, “In my new job, I will be able to code again. I will no longer be a ‘Word Programmer’”. He has always joked about being a Word Programmer – programming in Microsoft Word using narrative texts (use cases, scenarios, etc) and UML diagrams; programming by story telling. He was indeed a hacker.

Having spent a year and a half on this job, I can say that I now have a vague idea on why programmers (or I.T people, in general) quit. Even though I’m only a year-and-half year old in corporate servitude, I had been handled by four managers and had been transferred to four teams and that gave me great insights on the crucial dynamics that affects employee turnovers. In my year-and-half stay, I have seen three managers, a project manager, two architects, four senior developers and a handful of intermediate developers go. Just a few months ago, four of my teammates left. The statistics above is a little off; it is more than 20%.

Continue reading “On the High Turnover Rate of Software Developers or How to Retain your Best Software Developers and Programmers” »

Rate this post: 1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 3.00 out of 5)
Loading ... Loading ... |
  • E-mail this story to a friend!
  • Digg
  • Reddit
  • del.icio.us
  • Twitter
  • Slashdot
  • Facebook
  • MySpace
  • Google Bookmarks
  • DotNetKicks

High Salary is Killing the Software Industry

Judy Ann Santos - Philippine Superstar

Judy Ann Santos - Philippine Superstar

If there is someone that I hate more than Ms. Judy Ann Santos, that someone would have to be a person who has a job that he or she is not passionate about.

I don’t know if it’s the Philippine economy or just the Filipino culture that makes it “okay” for someone to live a life of suffering; enduring a job he or she hates for exchange of a comfortable life and a prestigious career. I’ve heard countless stories of teenagers being forced by their parents to take a course like Medicine, Law or Engineering (Courses which will attach fancy-sounding, age-old, titles to their child’s name) against their child’s will. I’ve accidentally watched countless Pinoy movies with the same theme. (Kid wants to major in Fine Arts, MOM aka Mrs. Attorney wants the kid to major in Law and be a lawyer. Sounds familiar?)

Five years ago, Nursing became a popular course for High School graduates to take in college. I know that because that was the year when I graduated from High School. During that time, some of my classmates took Nursing courses not because they want to be nurses but just because being a nurse would almost guarantee a free-work pass to the US and a chance of snatching that American dream. And you know what? I think majority of the newly graduated nurses thinks the same too.

Continue reading “High Salary is Killing the Software Industry” »

Rate this post: 1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 3.00 out of 5)
Loading ... Loading ... |
  • E-mail this story to a friend!
  • Digg
  • Reddit
  • del.icio.us
  • Twitter
  • Slashdot
  • Facebook
  • MySpace
  • Google Bookmarks
  • DotNetKicks

Work is now officially “WORK”

I can still clearly remember the words of our Tech Lead as if it was just said yesterday…

“Madali lang to sayo. Parang laro laro lang.”

He would always give me that answer while putting on a big, warm smile. Every time that I see him coding or preparing a design document, I would always approach him and ask him out of curiosity, “Ano ginagawa mo Sir? Mahirap ba yan?” and he would always give me that answer. And I have always wondered what he meant by “parang laro laro lang“. Sadly, I was never able to ask him about the actual meaning of it (he is now in Singapore) but as an Intern, I assumed that he meant that “If you’re having fun, it’s easy!“.

So much for work being "fun".

So much for work being fun?

Continue reading “Work is now officially “WORK”” »

Rate this post: 1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ... |
  • E-mail this story to a friend!
  • Digg
  • Reddit
  • del.icio.us
  • Twitter
  • Slashdot
  • Facebook
  • MySpace
  • Google Bookmarks
  • DotNetKicks

ASP.NET 1.X to ASP.NET 2.0 Migration Postback Problem

ASP.NET Migration Problem

ASP.NET Migration Problem

If you’ve read my previous blog post, I talked about some of the problems encountered while migrating some of our web applications from .NET 1.1 to .NET 2.0. Well, those products are now handed off to the Test Department for their routine torture.

Just a couple of days after the hand-off (Hand-off to Test or HOTT), the tester who is testing the product filed two (2) Tracks (Incident/Bug/Problem). Since I am the only developer working on the product, all of the tracks will automatically be assigned to me. The said tracks that were filed have the same “type” of problem.

When browsing for a file (Backup File / File Upload), the value of the Textbox would change back to its default value when the page re-loads.

Continue reading “ASP.NET 1.X to ASP.NET 2.0 Migration Postback Problem” »

Rate this post: 1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)
Loading ... Loading ... |
  • E-mail this story to a friend!
  • Digg
  • Reddit
  • del.icio.us
  • Twitter
  • Slashdot
  • Facebook
  • MySpace
  • Google Bookmarks
  • DotNetKicks

Migration: Why Developers Hate Microsoft or Why Developers Hate Vista or My First Encounter how Microsoft can Break your Software

Do you know how much Programmer's Blood it cost to put this tiny sticker in a Software Box?

Do you know how much Programmer's Blood it cost to put this tiny sticker in a Software Box?

In my previous blog post, I’ve mentioned that I’m working on a project to migrate an entire product line to Vista. What I meant by that is that I am responsible for making sure that our current product will run properly on Windows Vista. To guarantee that it is indeed Running Properly it should behave *exactly* like it behaves in Windows XP.  In simple terms, my entire job security is riding on making our products compatible with Microsoft’s failed attempt at a MAC-ish Operating System and with Microsoft’s successful attempt (a first in their history) to make their operating system NOT backward compatible with older applications. So much for Raymond Chen’s camp undying obsession with backward compatibility.

This products that I’m talking about are a set of Web Applications written in ASP.NET version 1.1. This web applications are as old as Windows XP. :lol: I checked its File Modification History in our TFS repository and the last time that anyone have touched its code base is in 2005 — and that’s just for a minor code modification to fix a bug. I believe this apps were written way way back in 2004 — when I was in Third Year High School! :)

To make this products compatible with Vista, there are a couple of steps that had to be done. I’ll enumerate each steps and what it takes to accomplish them.

Continue reading “Migration: Why Developers Hate Microsoft or Why Developers Hate Vista or My First Encounter how Microsoft can Break your Software” »

Rate this post: 1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ... |
  • E-mail this story to a friend!
  • Digg
  • Reddit
  • del.icio.us
  • Twitter
  • Slashdot
  • Facebook
  • MySpace
  • Google Bookmarks
  • DotNetKicks

Localization: A Programmer’s Dirty Job

When I was in College, I was amazed that the suits (”Business People”) are so willing to pay me good money just to spew out pieces of code that would eventually end up in a crappy system somewhere. Well, that was the time when I thought that working as programmer is just about programming. Or, that was the time when I believe that majority of a programmer’s time would be spent writing code… building stuffs.

Nowadays, when people ask me about my typical day at work, I always tell them that I’m working on a Localization Project. Most often than not, the common reply is “What’s that? Does it involve programming?” Yes, it involves “programming”, if you consider replacing a bunch of strings to their localized equivalent as “programming”.

As Mike Rowe will put it…

Localization… It’s a dirty job!

Why is it a dirty job, you ask? Consider the English phrase “Preview and Spell Check”. Now let’s see how it will translate to different languages:

French: Prévision et contrôle de charme
German: Vorbetrachtung und Rechtschreibüberprüfung
Russian: ??????????????? ???????? ? ???????? ????????????

Continue reading “Localization: A Programmer’s Dirty Job” »