doNotMessWithITTeamInAFuckingProject();

Last night me with my team have a discussion with my project team. Currently we have a project for our insurance client building a Learning Management System. The project condition already messed up since the first day i join a meeting. Because since its a consortium project with multiple company involved, one of company had a bad experience with another company. It happened few years back when both of company were somehow break up badly because miss communication (i heard this from one of my team).

Skip..skip... And then day to day like another stereotype IT projects when client and business analyst doing requirements gathering, the specs seems unclear and keep changing day by day even when I type this rant I'm sure it will change again.

Then something happened last night when my team leader force our business analyst to re index the use case number (imho) this is no need to be done, and i know the field conditions its so tough for all team members.

So many problems occured, actually this is a boring problem like lack of dev resource, lack of project management and all other stereotype IT projects had. Its sucks why this things is happening again.

Finally my fellow business analyst type a quite long message in our group and said that he maybe quit because its too tired and he felt that the leader only know about push push pushhhhhy fcking pussy, he never go to the client site and look what we've done and what we struggle so far.

I just don't know why, i know this guy earlier was an IT geek also, but when he leading a team he act like he never done IT project before, just know about pushing people without knowing what the context and sound to me like just rage push!

Damnit, i maybe quit also, you know we IT guy never affraid to quit anytime from the messed up condition like this. Even though we were at the bottom level in a project, but we hold the most main key for development.

Hope he (my leader) read this rant. And can realize what happened and fix this broken situation. I don't know what to say again, im in steady mode to quit anytime if something chaos happen nearly in the future.

doNotMessWithITTeamInAFuckingProject();

Process forking, signal handling, socket communication and race conditions. If I smoked I would have gone through a carton today.

ITS VBA again!

I made two misstakes today.

The first one was touching vba, the second one was assuming things.

The two statements are almost the same except the braces. VBA uses IF [condition] THEN..i soo foulhardly assumed that, when you just chain conditions together with an AND its taken as one statement. While in reality it apparently ignores some conditions and not some others.

I really dont bother with VBA a lot and try to avoid it, but upon occassion the need arises. I still dont know why the brace variant does the expected behaviour while the without does not. It seemingly does not ignore thew first two conditions but the third which makes it even more confusing. But as i dont know enough about VBA to say with confidence its on Excel and not on me i squelch my rage and tend the happiness that it now works..somehow.