Frutos, our PM, (named so because he is "PURO UTOS") asked me if we can talk outside. I was hesitant because I he pissed me off awhile ago because he insisted on pushing himself on the limited space in between me and jophet... joel... jomar!
He talked about my officemate's inability to document the requirements for the system she currently handling. I told him that maybe she's having a hard time from being a full time developer to a system analyst. He asked me why?
I told him about the common misconception that the two position are alike. We analyst should focus on system and user workflow in order to come up with a better design for the system. While programmer interprets that design for it to actually work. If someone has been a full time developer for a while, it's hard to jumpstart that person's mind and focus it on system usability and function when it's concentrated on thinking about logic and syntax. I've been there... You know what's the hardest transistion? Being a systems analyst all your life, using pseudo codes to document the functionality to a full time Project Manager that creates correspondence. I almost send something like this to the client:
Dear Sir,
If there is time we will pursue the meeting else we will discuss it.
I have to rebuild my entire vocabulary just to be able to create letters again. Join MAN-BLOG, to be able to converse in english.
I told him that. It's not easy for her also, so I guess the most logical thing to do, is for a non technical person to read the document and tell her that he doesn't understand what she is trying to tell.
But the "NON-TECHNICAL" person suddenly translates into moi... whatta motherfucker that guy is.
Office drama really sucks big hairy balls.
