It feels great when things are completed.
It feels even better when things that are not supposed to be done? by others, are completed, not by the person, but by you.
Sometimes, voicing out is one thing. Doing it is another.
Some people voice out, and then, that’s it. NATO. No Action, Talk Only.
Some people voice out, and get shot by others. Big mouth.
Some people voice out, and the voice fell on deaf ears.
Some people voice out, and just have to do what they have voiced out themselves.
People tell me they are busy with this, with that, with a lot of things. So, am I the one who’s most free? Why am I taking up other CCAs, when I have my own things to clear? Why am I picking up from where people left off? Why am I trying to clear piles of shit?
The reason is simple.
Some things are just so inter-linked with other things. If 1 thing fails, the whole show stops. After working on something for so long, don’t tell me, people cannot see things coming.
I see things coming.
I can choose to just stay in my domain, rotting in one corner, knowing nothing outside my domain. But I feel that is so wrong. Specialization is only possible for something that is stable, like a production line. Not a project. No.
Things are inter-linked. For example: sensor problem. It can be a hardware problem. Is it power? Is it cable? Is it settings? Is it software? Is it something else?
Let’s solve the problem the specialization way.
1) Power I/C checks. Power no problem. Hands problem to Cabling I/C
2) Cabling I/C checks. Cable connectivity OK. Hands problem to Hardware I/C
3) Hardware I/C checks. Hardware seems to be OK. Hands problem to Software I/C
4) Software I/C checks. There’s no problem with software.
5) So what’s wrong?
1 problem. So many people? LOL…
Oh well.