Arun Batchu

Greenhorn
+ Follow
since Feb 13, 2007
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Arun Batchu

Mike,
Here is another good one that you can help guide me in this labyrinth of "orientation based computing". Object Oriented, Aspect Oriented, Architecture Oriented and the latest asteroid that crashed my world is: Recovery Oriented Computing.

Is there such a thing ... or is it my mind applying a soothing-balm on itself as a solution for the latest crash fiasco in my client's production environment.

When I think about it: the "...I see dead people walking.." metaphor comes to mind : I see crashed applications rising up and running again... like that alien in the Terminator movie series. Ghostly!

Please don't tell me I am hallucinating... Recovery Oriented Computing.. I will wait for your answer, while I go ask Mr. Google, uh, God. Why didn't I think about it in the first place? That would have been a cool term to coin.

Arun
Mike,
Usually it is such a trouble to get *just* the functional requirements taken care of, that the very mention of worrying about the "-ilities" that a good Architect would bring up and which are absolutely necessary and become important after the birth of a baby (what do you mean the button is on the next page?), are either deliberately ignored or pooh-poohed. People run out of steam, energy and most importantly budget and/or time just getting through the functional requirement gauntlet that they are made to run through.
Unlike a baby, whom we nurture for years before pushing her out into the wide, wild world, and that too under a watchful eye, we tend to demand our fledgeling systems to be functional, resilient, performant, scalable, secure, ACID, alkali... all that ... with virtually NO nurturing time, money or even thought.

The only way I see a way out is to "figure that quality factors in" upfront into project scope, budget etc. rather than demanding a separate "QA" and "performance testing" budget. I would really love to get some heuristics about how to get those taken care of by matter-of-factness, like scheduling a performance/scalability test or usability tests at every milestone rather than at the final release or "staging" area.

I am tired of being a hero. I need to get a life - the remainder anyway.

Your thoughts?
-Arun.