GururBrahma GururVishnuhu....
GururDevo Maheshwarah....
Guruh saakSaath Parabrahma.....
Tasmai SreeGuravay namaha.....🙏😊
This Shloka is the one that we have been reciting since our childhood school days.....
Now that in our earlier post we read and understood the importance of GurupourNima, let's talk in detail about the role of a Guru and relate it to today's modern world's roles to understand the essence of 'gurutwam' in it's entirety......
Let me step in to the shoes of
Software Product Management and explain the same so that it essentially establishes the fact that a Guru's role intertwines everything under the Sun and serves as a fulcrum for an overall peaceful and prosperous society and thus a healthier and happier Nation as a whole........ 😊
As many of us know, any given firm's SDLC comprises of
Dev, QA, B&R/Ops, Project/Program Management, Product Management, as the 5 key engineering elements that work in tandem to execute the technical business of building an enterprise level software product.......
Dev ( Core & Sustenance development team ) is all focused on getting the Code Fixes / Bug Fixes checked in to the SCM tool and get their basic UT reports validated via the smoke CI builds......
QA ( Functional [ Inclusive of white box and black box testing teams ], Automation Qa & CQ Qa ) is all focussed on logging as many bugs as possible to make the software as much error free as possible. A good number of showstoppers ( S1 Bugs ) is all they are happy about.......
B&R/Ops/Field/SupportLine
( all that engineering personnel that doesn't belong to exactly either DEV or QA, who work on the other various supporting engineering infrastructural needs ) is focused about churning out successfull builds by capturing the latest and the greatest code fixes via their CI systems and/or providing the required specifically configured environments for various in-house engineering needs......
Project / Program Management
is worried about " Kitnay loag hai.....Kitna % kaam complete hua aur baaki kab complete hoga.....? "
so that all the colorful excel sheets with various timelines can be updated and shared across.....
And here comes the
Product Management, that serves as a fulcrum that intertwines all the aforementioned entities in a continuous optimistic executional manner so that each of those functions essentially travel on the right track.......
to build something that the existing / prospective customers really require to address their growing current business needs......,
to build it in a right way, so as to save on the resources' time....,
to build it in a bright way so as to have a gain on the competitors.....
to build it for making an impact in the market so as to stay ahead of the same.....
and finally
to build it for addressing the larger world on how a near utopian product offering would look like so that others could emulate or get inspired with the same.......
As a part of this continuous executional saga, a typical Product Manager would place himself/herself in a pivotal role that essentially would make it's successful mark in all of the aforementioned entities by ensuring that all of them are aligned and fine tuned to a cohesive organised global development model that makes the united larger global engineering team highly successful in executing the various phases of their SDLC .....
And given the fact that a Product Manager typically holds a good amount of knowledge in all of these 5 SD entities, he/she would be serving as one of the guiding beacons to head the product and it's marketing strategies inline to the real world's practically applicable scenario to ensure that the product always remains successful in placing itself as the most promising and competent solution for every given customer looking out to address their business concerns........
Lets take a simple example of a scenario where in an e-commerce solution is provided as a cloud offering to various customers and the various perspectives of the same that are dealt by a typical Product Manager heading that particular cloud SKU while working on a marquee feature that is
" Having a provision for selective customers to access the offered cloud application on a set of predefined ports only......."
( Their in-field automation systems require such a feature to avoid a clash with other executions running on dynamically selected ports that are different from the ones chosen for their business application.....)
Hence here we need to isolate another key parameter called "port" in addition to the business logic that is held with the cloud provider......
Initially, this might look like a simple ask to have it fetched as a predefined parameter from a customized UI that triggers the application deployment as per the customer needs.......
However there are another 2 key factors that are to be considered while including this customer ask in to the production / Dev code changes.....
The app deployment need not be always via the standard UI execution with dynamic parameter input.....
Because
1. It can be subjected to a completely "Silent App Deployment" with a WebLogic provided innate command line system called as WLST...
2. It can be subjected to a "Passive
App Deployment" where in a given WebApp
( jar / war / ear ) can be placed in an exploded archive format in a WebLogic specified directory structure which would be captured in to an Up & Running application upon a simple server restart........
Now if the customer ask is percolated only to the UI App Deployment process, we would be missing out on these other key aspects.....Isn't it...?
So it needs to be dealt from a 360 degree perspective that can be done only when we are aware of all the available deployment options......
Now if we can come out of the software world for a while and get in to the spiritual world....,
An established sathguru is like this versatile Product Manager who evaluates every Shaastra Vachanam from a 360 degree perspective to ensure that the "Paramaatma tattwam" gets distilled in to the ShisyaLokam so very well that it leaves no stone unturned......
I specifically took the above example of 3 different ways of web-application deployment because this concept is much closer to explain the " Paratattwam " in the form of the well known Trinity,
Brahma Vishnu, & Maheshwara...
donning the roles of
SruSHTikarta, Sthithikartha, & Pralayakartha, respectively..... 😊
1. "BrahmaDeva SrushTikartha / BrahmaTattwam" is like the " Passive App Deployment" process.......
Until yesterday the file system had nothing in a given directory structure......
And all of a sudden someone pastes a 'folder' and in no time that folder becomes an Up&Running live application upon a server restart....!!
( Ofcourse a lot of R&D went in to create that 'folder' to get it converted in to a web application.....)
Similarly, until some day there was no person in so and so house and all of a sudden there is a human being born on a fine day who would gradually take a Name, an identity and so on going forward.......
All the complex Karmik R&D that went in to create a new living being on the planet earth and convert it in to a 'simple human being' is what the BrahmaTattwam / SrushTikartha deals with......!
2. Vishnu Tattwam / Sthitikartha :
The all visible generic UI app deployment process that deals with every parameter required represents Vishnu Tatthwam.....
where in everything is clear, visible, fathomable, and above all it's always an interactive deployement model.....
As Shree ChaaganTi sadguruji explains, though there are 1000 names recited in the "Shree Vishnu Sahaaranaama Stotram..."
the first two
"Vishwam Vishnuhu...."
would say that all the visible Universe is nothing but Vishnu....!
( Vishweati vyaaptaha iti Vishnuhu......i.e., the one who is ever pervading is Vishnu.....)
Hence the rest of the names would only mean the various explanations / perspectives / for Vishnu...!
3. Maheswara tattwam / PrayalaKartha :
The " Silent App deployment / undeployment model " represents Maheshwara Tattwam......
Because no one knows when did the lightening fast App Deployment /undeployment occurred at the click of a button on the configured scripts named
" WSLT-DeployApp.sh "
&
" WSLT-UnDeployApp.sh ".
Until a few minutes ago there was an Up&Running live application accessible from the WebLogic Admin console and after just one click on a script, in no time it got erased completely.....
Similarly no one knows when did the lightening fast "Layakaaraka Prakriya " was executed by Maheshwara via a cosmic script
" CallYamaDharmaRaja.sh "
to complete one's journey on the planet......
Until a few minutes ago a person alive walking / eating / and doing all other chores exists in a given place.....
And all of a sudden once
" CallYamadharmaRaja.Sh " script is invoked, that person gets perished away from this planet completely and in no time there wouldn't be any remains of him in his usual place......
Just like the silent App Undeployment leaves no residue on the file system....
Just like an efficient Product Manager who details all these scenarios to the wider engineering teams while working on the Marquee Feature Implementation,
an established sathguru similarly distills the "Paramaatma Tattwam" so profusely in to all his Sishyaganam......😊
And thus a Guru is venerated as a.. "TrimoortiSwaroopam" of BrahmaVishnuMaheswara......😊
And thus Shree Taallapaaka Annamaachaarya rightly extolls the Trimoortyaatmaka ShreeVenkaTeshwara Viabhawam saying
" తనరగ గపిలుడై దత్తాత్రేయుడై |
ఘనమైన మహిమ శ్రీ వేంకటరాయడై |
ఒనరగ సంసార యోగము గృపసేయు |
అనిమిషగతుల నభ్యాసయోగి | "
No comments:
Post a Comment