It is like when a hostile aircraft enters the unauthorized zone and starts creating a lot of chaos with its unmindful actions , it becomes imminent to...
1. First give it a friendly message to stop bothering the vicinity of our concern and return to it's abode.
2. If it doesn't listen to us and continues it's provocative actions disturbing the peace in the vicinity of our concern, then chasing it down to answer via appropriate retaliatory measures like gun fire on the fly, etc would be the next line of action to be taken to control the situation.
3. Despite the multiple appropriate measures taken to inform it of it's deliberate hostility, if it doesn't stop creating the ruckus then finally activating a laser guided missile with object-to-object inter lock activated would be the final controlling measure to completely take it down so as to re-establish the peace.
( Once the object-to-object inter-lock gets activated on a laser guided missile, irrespective of the territories being traversed the missile will not leave it's target no matter what until it makes a successful collision to completely bombard with and annihilate it's target in it's entirety )
Now that my vicinity of concern is software engineering and a few folks associated with it, let me take a practical simple scenario that I have had a chance to work along with all the various personnel who were resolving the ticket with the inputs from all the allied teams of the SDLC gamut.
It was a ticket from a customer complaining about the efficiency of their production systems going down significantly ( Unix/Linux/HP-UX) after installing a specific one-off patch aimed at fixing one of the S2 issues specific to their environments.
Long story short would be,
the installer bundling the specific fix or the one-off patch ( the .bin file ) wasn't successfully performing the clean up process of all the interim temp files generated during the installation and configuration of the fix because the lock on some of those temp files wasn't getting released by a few rogue processes created during the installation process. Adding to that every specific DM process ( 'Dependency Mapping' was one of the most sought after maquee feature of the then product being built ) getting spawnned from the Introscope Agent via the EM server's aggregated metrics' the same of which gets displayed in the form of a "visual map" that provides the workstation admin a complete clear picture of the entire end-to-end webservice transaction tracing once it gets invoked by an end user.....
So this rogue processes would go on increasing multifold as and when that specific feature is accessed by every authorized user and thus they keep on burdening the entire system with no GC equivalent to clean them off from time to time. So it indeed is a serious concern for the customer because all his key resources like CPU / RAM / DiskSpace are being eaten away by those innumerable
ad-hoc rogue processes with no one having an idea of who are creating them and why....
It was then that 2 veterans who are highly revered engineering personnel of the group that I was working with, one named
Mr. Stewart Thain ( the Introscope EM expert ) and the other Mr. Roger Saunders ( the Introscope agent expert ) , pitched in to zero in on the actual root cause of the issue and then suggested the appropriate measures to be taken to force kill all those specific processes with a certain naming pattern before the clean up script gets executed by the installer to leave no trace of any unwanted rogue files and processes burdening the customer environment which was a complex Introscope clustered set up...
And thus there was another one-off patch to fix the issue with the earlier one-off patch by including the corresponding changes to the IAP_XML files creating the respective platform's installer files along with the allied few changes to the build system scripts executing those iap_xml files to post the final software bundles on to a huge builds' storage server named Truss.ca.com that is configured with the Apache Tomcat HTTP server that allows the builds to be download by all the authorized internal users / external customers ...
The PdM / product management personnel
( who don't all of a sudden pop up from the skies.. They essentially have donned various core engineering roles earlier and after having had a good exposure to the various facets of the SDLC gamut, have placed themselves in the role of a Product Manager who essentially play a pivotal role in tying all the individual strings being held by the PrgM, Dev, Qa, Sustenance, Ops and all the other allied teams to align the universal goal of
"building the right software to the right customer with a right feature set with-in the right time in a right way...."
by their defined executions.... )
have no clue as to why only this customer has complained such an issue when it was just the same generic feature set for all the platforms being supported as per the 3PQ matrix....
The Dev had no idea about how such a use case can arise when almost all the brought up use cases by the global engineering team have been considered and are included in the iterative feature development process....
The CQ Qa / Sustenance Qa has no idea about how can such an issue be there when they have executed all the test cases that were handed over to them by the core Qa after the Alpha and Beta checks were all good....
So every one in the org were like
" Ohh...
hamay tho nahi pata...!
ham kaisay bhoolay...!
hamay kaisa pataa chalegaa....!
ham kaisa pataa karay....!
"
and all that typical exclamatory remarks with a rather frowned expression based on the SDLC discipline they belong to....
It is here the experience of a veteran combined with the exploratory outlook of the field personnel implementing the software at the customer site, that comes to our rescue with their exceptional RCA capabilities and efforts put in to zero-in on the root issue...
Similarly in real life scenarios too,
there would be a rather peculiar situation where in a few rogue personnel keep fabricating strange issues when we already have enough to deal with, that keeps harming our peace of mind and all other precious resources like Health, Time, Efforts.....etc....
And it is when the approach of
" Going above the usual plane of existence by thinking beyond the obvious realms..."
that one needs to look for so as to zero in on the root cause of the problem in order to
nullify it completely and it can happen only with the grace of a sathguru and God's blessings.....
Let me explain one such scenario.....
Mr. V, some typical normal chap, was busy with his regular work by putting in all his diligent efforts within the purview of the authority and opportunities he was allowed to consider and it was like any other typical global software team...,
A few associated folks let this guy do his work as usual...
Another few wanted him to work like a donkey but they neither want him to get any name nor they want to provide atleast some amount of minimal 'food' to satiate the obvious hunger.....
They just want him to keep dragging the load....
Another few have become jealous and deliberately caused many hard ships to stop this guy from becoming successful with his diligent and smart efforts....
Another few with their arrogance have cunningly plotted various types of hard ships to stop this guy from gaining good name at the top management....
Another few couldn't digest the fact that this guy would certainly become one of the pivotal personnel of the org and thus have become extremely jealous and have resorted to put an end to his efforts and existence intelligently and anonymously...
In a wild goose chase of finding solace amidst these many different types of weird executions going on around him,
this chap simply kept observing everyone so keenly so that he can form the entire block chain of the hostile folks with their respective executions as their individual block's signature and when its the right time to answer them in a right way, he can just start his counter executions accordingly as appropriate....
However a few extremely cunning and over intelligent folks have barged in to the territories that they're aren't supposed to enter and started infusing their venom of narrow mindedness to many of his friends, relatives, family members, neighbours etc so that they can achieve their spoilsport matrix to stop him from being successful in his endeavors....
While dealing with this highly intricate and complex situational crisis, this chap can neither hurt his own folks whose executions were infiltrated by the hazardous narrow mindedness of all those hostile folks who want to stop him from achieving his goals by all possible means....
nor can he stop himself from becoming vehemently ferocious against all those who are either knowingly or unknowingly
have become a reason for his sorrow and pain by allowing the hostile folks to hurt him via them.....
So the most efficient way to solve this problem / fix this pestering issue would be to completely stop the rogue folks from spreading their ire and narrow-mindedness by appropriately identifying the core root ( or 'roots' if the conglomerate is akin to a Banyan tree with multiple groundings,
which it sounds to be.... ),
i.e., the core culprit or culprits need to be given a strong blow ( both cosmic and executional ) that can ground their arrogance at once forever when the time is ripe....
Just like MaheshBabu's powerful punch in the movie 'AthaDu' when they undermine Parthu's power and listen to Naidu's words to continue bashing the former despite witnessing enough blows from his steel nerved fist....
Copied below are the lyrics of the 'AthaDu' movie's title song that would aptly describe this 35 year old witty Manager's vehemently wiser executions....
" అదరక బదులే చెప్పేటి తెగువకు తోడతడే తరతరాల నిశీధి దాటే చిరు వేకువ జాడతడే
తరతరాల నిశీధి దాటే చిరు వేకువ జాడతడే..అతడే..అతడే..అతడే
ఎవరని ఎదురే నిలిస్తే తెలిసే బదులతడే
పెను తుఫాను తలొంచి చూసే తొలి నిప్పు కణం అతడే..
పెను తుఫాను తలొంచి చూసే తొలి నిప్పు కణం అతడే...
Life has made it stronger It made him work a bit harder
he got to think and act a little wiser This world has made him a fighter
కాలం నను తరిమిందో శూలంలా ఎదిరిస్తా సమయం సరదా పడితే సమరంలో గెలిచేస్తా
నే ఫెళ ఫెళ ఉరుమై ఉరుముతూ..జిగి ధగ ధగ మెరుపై వెలుగుతూ..
పెను నిప్పై నివురును చీల్చుతూ.జడివానై నే కలబడతా..
పెను తుఫాను తలొంచి చూసే..తొలి నిప్పు కణం అతడే !!
చుట్టూ చీకటి ఉన్నా వెలిగే కిరణం అతడు
తెగపడే అల ఎదురైతే తలపడే తీరం అతడు
పెను తుఫాను తలొంచి చూసే..తొలి నిప్పు కణం అతడే !!
తన ఎదలో పగ మేల్కొలుపుతూ..వొడి దుడుకుల వల ఛేధించుతూ..
ప్రతినిత్యం కధనం జరుపుతూ..చెలరేగే ఓ శరమతడూ..
Life started to be faster made him had a little think smoother
he's living on the edge to be smarter this world has made him a fighter "
No comments:
Post a Comment