Mob mentality

No Comments

The mob mentality negates the basic premise that two wrongs doesnt make a right. Being part of a mob grants both a sense of power and a degree of anonymity by blending with the crowd. The combination of both can imbue a euphoria that overrides the normal and logical reasoning, enabling a person to do things they won’t normally be expected to do.

Once a mob is fired up, it will either take a lot to subdue it. Most of the time, it will simmer down but only after leaving a lot of damage in its path. The participants of the mob usually doesn’t feel any remorse as they justify their actions as both “right” and “acceptable” since it was the actions of the mob and not their own.

The best time to stop a mob is when it is just starting up. That is easier said than done though. The best way to handle a mob is get out of its way and just hope that there is still something left in its wake.

BftP : Passing vs Working

No Comments

[Lifted from an old email I sent to my previous project mates.]

This is an email to remind about wantonly tweaking configuration settings in the Oracle Fusion Middleware stack to make the code work. Wantonly in this case means it did not go through the official change management process as the members in question wanted to quickly solve an issue that was first encountered in the UAT environment.

E2 is supposed to mirror the E3 environment to catch any problem that could happen in E3, or replicate an ongoing issue.

Our goal is not to make our deliverables pass UAT, but to provide deliverables that will not malfunction in production.

Any setting that needs to be changed needs to be evaluated properly to ensure it doesn’t affect the other applications in the environment. Each setting change is always a compromise between two conflicting scenarios (e.g. performance vs scalability, traceability vs resource management, etc.). We need to understand what we are exchanging for each setting update. The E2 settings change needs to be propagated to E3 afterwards.

For the nomenclature:

  • E2 is the User Acceptance environment, and
  • E3 is the Production environment.

Business Optimism

No Comments

You probably have heard of “when life gives you lemons, make lemonade” or “you cannot make omelette without cracking eggs” but company business optimism is taking this a bit further. They are thinking ahead and in what I would assume to be pursuit of cost cutting the powers that be has shifted to “why bother making lemonades and omelette in the first place? let us take away the lemons and eggs so you wont have that problem” mentality.

Ingenious, yes.
Devilish, yes.
Practical? It depends on whose perspective.

I like lemonade and omelette. I also like having the choice whether I will or I will not have them.

ciao!

Turn around

No Comments

SLA – the maximum amount of time that a task can be put off that the requester cannot contest except to raise the cost by involving higher-paid individuals to increase the imaginary priority shown to external users.

Sometimes misunderstood to be the time needed to require work to be completed.

AnalogClockAnimation1 2hands 1h in 6sec

Imagine This

No Comments

Imagine an environment where standards are strictly enforced.
Where security is of paramount importance.

Now imagine that at the expense of productivity or rational reasoning.
Where compliance is dictated by the contents of a clipboard checklist.

Sandro Botticelli - La Carte de l'Enfer

Welcome to Hotel California.

Older Entries