It took a mildly bad case of cold and accompanying strange headache for me to figure this one out. Considering the not so optimum incubating environment the analysis and corresponding conclusions might not stand a good test. But they sound alright to me right now.
So lets ask this question. What is common between a Doctor and a Developer?
Answer : They both end up clearing someone else's bloody mess and buggy code.
And now let me go ahead and explain that. The smart ones may skip the following part. Developers in 90 % of the case end up supporting an existing application or worse an application "designed and developed" by themselves. Doctors similarly 99% of the time end up fixing natures bloody mess. The remaining 1% is attributed to the seldom heard cases of "doctor left a glove in the patients belly during operation" or "mis-diagnosed heart patient gets his kidney removed"and suchlike.
Again lets talk of percentage. 90% of the time a developer tries to fix an exception by restarting a server or the application. Similarly a doctor prescribes a bunch of antibiotics and other generic drugs irrespective of the symptoms. The last bit on the Doctors is based on the common belief that medicine is still an experimental science. And it works in both the cases. The restarting of the server/application cleans up all the logs and caches and the application starts running smoothly. Similarly in case of the Doctor one of the generic drug hits its target and the patient is cured.
Moving forward further 9% of the time, the developer finds a documented exception , a known symptom in case of the doctor and uses the prescribed solution to fix it.
The remaining 1% are the undetected and untraceable bugs in an application for which the underlying coding language isn't developed enough. And for the doctors these are the HIV's and Hepatitis B-C's and suchlike incurable diseases.
Now both doctors and developers might take exception at this post blaming me of gross assumption. But I have nothing but immense respect for both the professions, I being a developer myself. They both do a really tough job of fixing stuff and they inadvertently get blamed for someone else's faulty design.
So lets ask this question. What is common between a Doctor and a Developer?
Answer : They both end up clearing someone else's bloody mess and buggy code.
And now let me go ahead and explain that. The smart ones may skip the following part. Developers in 90 % of the case end up supporting an existing application or worse an application "designed and developed" by themselves. Doctors similarly 99% of the time end up fixing natures bloody mess. The remaining 1% is attributed to the seldom heard cases of "doctor left a glove in the patients belly during operation" or "mis-diagnosed heart patient gets his kidney removed"and suchlike.
Again lets talk of percentage. 90% of the time a developer tries to fix an exception by restarting a server or the application. Similarly a doctor prescribes a bunch of antibiotics and other generic drugs irrespective of the symptoms. The last bit on the Doctors is based on the common belief that medicine is still an experimental science. And it works in both the cases. The restarting of the server/application cleans up all the logs and caches and the application starts running smoothly. Similarly in case of the Doctor one of the generic drug hits its target and the patient is cured.
Moving forward further 9% of the time, the developer finds a documented exception , a known symptom in case of the doctor and uses the prescribed solution to fix it.
The remaining 1% are the undetected and untraceable bugs in an application for which the underlying coding language isn't developed enough. And for the doctors these are the HIV's and Hepatitis B-C's and suchlike incurable diseases.
Now both doctors and developers might take exception at this post blaming me of gross assumption. But I have nothing but immense respect for both the professions, I being a developer myself. They both do a really tough job of fixing stuff and they inadvertently get blamed for someone else's faulty design.
No comments:
Post a Comment