[This message has been edited by JUNILU LACAR (edited June 01, 2001).]
I appeciate the issue raised by Junilu.I have also faced difficulties in understanding the "code words".Many who practice such shortcuts say that this is an "internet language".Of course sometimes it is acceptable upto certain extent but it should not get converted into an alltogether different "alien language"which is not recognizable by all.
I ve fould many short forms on this site only.BTW,IMHO,RHE,GoF,etc.So excessive use of such language should be avoided.That is what I think.Some may not be agreeing to it.But I think it will be friendlier for the novices.Anybody should not feel alien here.
Just my $.02
[This message has been edited by Dave Vick (edited June 04, 2001).]
I strongly believe we should use "textbook" English here wherever possible. We have users from all over the world, why make things hard for anyone just through laziness?
The ever popular 'please help me', or the equally unenlightening 'need help'. Those drive me even more crazy than the abbreviations. Not only is it hard for people to decide what posts they want to look up but it makes it hard for someone to be able to look up previous answers by scanning the subject line.
Granted in some cases it is hard to pick a subject when the poster may not even know where to begin but they should be able to come up with something - even a generic 'applet won't compile' is better then 'please help me'.
Again, that's just my opinion.
I know that I started using "RHE" simply because I was tired of seeing how often people referred to the book as if Simon Roberts was the only author. Plus I'm inherently lazy, and considering how often we refer to that book here, it seemed an appropriate thing to abbreviate. Same with M&R for Mughal & Rasmussen (poor Rasmussen is usually forgotten), though I see we forgot to include that one in our FAQ. Likewise the JLS should be listed.
[This message has been edited by Jim Yingst (edited June 04, 2001).]
Originally posted by Jim Yingst:
Well, we do have a short list in the FAQ... include that one in our FAQ. Likewise the JLS should be listed.
Do you think "GoF" should also be added to the list? It's used fairly often in some forums.
How about including a friendly reminder to limit the use of abbreviations to the ones listed in the FAQ and avoiding arcane and "lazy" abbreviations like plz, pls, hlp, u, r, ur, b4, -tive, +tive, since they make it harder to read messages.
XML, XSL, DOM and SAX
Process: UP, RUP, DRUP, XP, etc.
Or this message:
�I heard <�> that dRUP comes from the DSDM approach with RUP� - makes perfect sense, BTW
�You are a programmer, if any three letters make sense for you�
I think "plz,pls,hlp,ur" are at times acceptable but frequency should be less.We understand that in this internet world we try to convey as much as possible with as less words as possible.
In this scenario,the above abbreviations are reasonably fair.Because those are understood by the majority of people.But the one mentioned by Mapraputa Is tricy one.It seems like the one who posted wants to test the basic necessity of the programmer that is "Aptitude".I think itwill be difficult to moderate but can't we monitor the users who use such language frequently.They can be given a hint towards it.They are so used to it that they even do not bother.
Another reason for using such abbeviations can be that everybody wants to be in the "no. of postings race".Sometimes I find it partial.Many people read "somebody reached 2000" and gets motivated and posts messages with such abbreviations.I apologise if I am offending somebody But to be frank I don't believe in "unnecessarily hyped no. of postings" stuff.
My biggest concern with using this type of 'internet language' is it seems unfair to those whose primary language is not english. I know a little French, and if I had to try and phonetically guess the author's intent of a message written in such a manner in French I would be totally lost. It is simply harder to communicate effectively this way, which of course means that by writing messages like this the author is limiting the number of useful responses.
Since JavaRanch is such an internationally open society, I don't think we can limit this conduct. On the same token however I would hope that we could inspire everyone to use "real" words in the spirit of effective exchange of ideas. The Internet is our medium, let's use it well.
I'm a soldier in the NetScape Wars...
[This message has been edited by Joel Cochran (edited June 05, 2001).]
If someone posts a hideously hard to read message, full of b4->before, u->you, etc, etc... Then that person will not get a response, and the gene pool is cleaned (so to speak).
Aren't I rude?
p.s. Acronyms are totally acceptable.. in fact when someone once wrote out "Transmission Control Protocol / Internet Protocol" I had to think for a few seconds "what the heck is that?". Sometimes an acronym is easier.
Many people read "somebody reached 2000" and gets motivated and posts messages with such abbreviations
Why??? As far as I know, none of the 1000+ poster use abbreviations in the way complained about in this thread. It seems a poor shortcut to get a post done faster, if that's what you are implying.
Needless abbreviations simply do not work. Along with bad spelling, unclear structure, untested code examples, URL links which don't go to the right place, and leaving out important information, they just make it much harder for readers to understand the message. If only a few people can understand a message, even fewer will even think about answering it, and probably none at all will bother replying.
If you really want an answer to a question, or if you want someone to be able to use an answer you give them, the upshot is simple. It is your responsibility to make your message as clear, straightforward, accurate and understandable as possible. This means think, check, and edit until it is the best you can do.
Saving half a second by typing 'u' instead of 'you' helps none of these things.
If I happened to be a potential employer reading through the replies to my job posting and saw them filled with all of these abbreviations, I would just ignore these replies outright. The writers might be wonderful coders, but I think in even an informal recruiting environment such as the Ranch that *some* formality of business communication would be appropriate.
I wouldn't apply for a job in which the recruiter wrote the job posting full of cute abbreviations, and I certainly wouldn't expect that a recruiter would reply to me if I wrote to them in that fashion.
Language is our primary medium, the internet is only secondary and English is the 'Language' used at this site. Any derivation from standard form in any language leads eventually to a slippery slope effect where it can be and is argued that a small change is inconsequential yet the next argument after that one small change has been accepted will be yet again another small inconsequential alteration. Slang is a bad thing in most cases with any language. Slang tends to 'deconstruct' a language one small subtle piece at a time. This should be of concern to anyone with understanding. With all the talk of 'professionalism' on this board I would expect it should be a common denominator to refrain from any practices that endanger our primary medium of communication. And that's my five dollars worth.
Originally posted by Rochelle Hoffman:
The one place on the Ranch where overuse of abbreviations (pls, hlp, u, ...) is common, and seems to be such a bad idea is in the Jobs Offered forum.
If I happened to be a potential employer reading through the replies to my job posting and saw them filled with all of these abbreviations <..snip...>
I have to admit that in my opinion people who use 'too' many non acceptable abbreviations tend to give me the view that they are lazy and unprofessional.
(Ex: u r rite I am !going to spend the $ 2day.) What the hell is that?!? "You are right, I am not going to spend the cash today.)
Who wants to have hire a programmer who then sends a bunch of emails to a client written in "3l33t15m" . (Elitism).
SOURCE CODE should be SURROUNDED by "code" tags.
Click here for an example
Okay I've vented and I feel better now.
hag1 (have a good one),