-sigh-

work's aplenty in the office. we're kinda behind time on the current "project" we have at hand, and we're gonna be later still i believe. okay my boss doesn't quite seem to agree on my using that word but for now let's just say i think that it's quite apt to be termed a project.

my colleague and i - who do most of the work getting our hands dirty - have slightly different views in our style of working from the lead programmer. i should say, we're on a different wavelength. for me, i'm just trying to find a balance between their styles, because we simply can't find one single solution that will fit both scenarios. in my opinion of course. one has cost-effectiveness in mind while the other follows Java programming practices+practicality. let's not go too deep into that. at times, both would think themselves right, while i have my own ideas. so to compromise, i'd then try to blend my thoughts with their thinking. other times, i'd have just done what i was told. no biggy. sometimes it just takes too much energy+effort debating over the right course of action that it just doesn't seem worth the time to do so.

still, i wouldn't say that there's conflict. the roots of the beliefs for the few of us of course is to get things done right and soonest possible. everyone might want the rest to agree and follow in their ideals, but they all have good intentions nonetheless. i wouldn't say all this is political. us code monkeys don't have much of that.

i'm sure this will blow over once this project is completed.

*kupo?*