i want to be a gosu designer. but currently, i'm a developer. and as such, i concern myself with syntax, api, best practices and optimization. is it perhaps of my personal experience that i expect at least the same courtesy from other technical persons in the field? i guess it goes without saying that people who call themselves developers and do nothing of the items stated above are trouble. in all honesty they should switch to another profession and steer clear from me (preferably, they should be absent within a meter's radius from me.. physically and virtually).

i guess my ranting about them proves that i have been exposed (unwillingly of course) to these so called techies. and it is for my better health i suppose that i vent about them here.

1. abu and his henchwoman with their cryptic english ( i wonder if they created an art of unintelligible, loosely constructed english? not of course that i'm saying that my english is perfect, but at least it's functional...) and worse, their incapacity to implement a simple mechanism to wrap information in xml (and they were given the wsdl too!!!!) in a programming language they testify to have been using for years. idiots. it took me less time to write a script in asp, a language i didn't know and they supposedly mastered. honestly, i did in 4 lousy hours (and i didn't even file it as overtime) what they had been trying to implement for the past 3 days. they must have missed something in their english... oh what was that abu? can you hold? i have to decipher that one. i'll get back to you later.

2. jon, who procrastinated a whole month before testing what i had rushed to deliver to him: a working shopping cart system complete with integration and layout. and who changed his eAccess password without informing me. you wouldn't believe this guy. i asked him several times over if he happened to change the password because if he did, i have to tweak the config file of the app and upload it again. he said no. but then why was the system which i had tested and worked flawlessly having errors now? the error message was a telltale sign that the error persists during sign in. that's a no brainer. it's either the sign in name or the password. since the sign in name is within my control, by the process of elimination it must be the password. but he didn't change it... or didn't he? i tried logging in to his eAccess account and bingo, username and password do not match. i reset the password and tried testing the app again. and it worked, flawlessly as expected. so much for not changing the password. why i oughta...

3. telesforo, my latest pain. who incredibly made it to tertiary education without knowing how to read. honestly, the point of documentation and in-line coding/comments are fairly obvious. they are to be read. yes, that's R E A D tele. very good! templates, although they are to be the bare minimum of anything, in this case the integration script, should still be used accordingly. don't expect to copy and paste it in your code and expect a fully functional app afterwards.

my point is, being a developer requires certain codes of conduct as well. read the comments. understand the code. do whatever it is that you can do on your own before finally asking for assistance. if you are on a deadline, don't pull me in to the mess. don't let me code for you. you are a technical person, you can do that on your own. technical assistance is fine. but being asked insipid questions whose answers are just beyond the // is not just annoying. it's insulting to both your hard work and profession.