competent

i was struck by the reaction i got for a recommendation i made.  the other party immediately understood what i was saying and readily agreed that it should be done.  whoa!  i haven't had that in a looooooooong time!

for so long now, there i'd be, raising all these things that should not be skipped and the other party's reflex reaction would be to ignore, object and/or not do them at all.  i'd go into details to explain what it is we should do and why it should be done and still i would fail to get through.  aaaaaaaaarrrrrrrggggggghhhhhhhh!!!

what's worse, the things i am raising are things that really should not be coming from me but from these people themselves who object to and ignore the action points!  hello!!!  this is supposed to be your lookout, you're not seeing it (!!!), given my previous assignments i am able to do the heads up for you and you're the ones who object?!  insane!!!

no matter how much lip service you pay about acting on the recommendations, the developments would show that certain things were not done.  the effects are there, in black and white, in actual disruptions.  if you are someone worth your salt, you would realize that these things were caused by certain inaction.

i've said so many times, if you do not understand the technical aspects of what i am saying then maybe the non-technical aspect you could comprehend, that is, it is not in my interest to delay anything.  i am onsite here!  i want to go home!  i want a successful activity otherwise we're going to schedule another attempt.  i don't want repeated attempts, more so unsuccessful ones.  they wreck my weekends, they eat up my time!

it's really nice talking to people who know what they should know for a change.  that was how it used to be.  i hope we can bring it back.

No comments:

Post a Comment