>>>>> "BM" == Brandon McCaig <bamcc...@gmail.com> writes:
BM> [1] I personally find it very petty when Uri mentions his work as a BM> Perl "recruitment agent" (for lack of a better description right now) BM> and implies that he'll never consider you as a potential candidate BM> with regards to that because of your opinion on a subjective topic. BM> That's not even a relevant qualification, IMHO; I bet there are a few BM> thousands, if not millions, of people doing that job that don't even BM> know the first thing about software development. Go consult BM> http://thedailywtf.com/ for some fun stories about people being hired BM> in senior programming roles without even knowing the very basics of BM> programming. :-X and you're not being petty bringing that up? :) my point there is that i do judge perl and other skills professionally. not a hobby, not on this list, etc. i get paid for my opinions about the quality of candidates. i review their code, talk the them about it, listen to what they say, how they take the critique, etc. it all factors in. my views on coding style and rules are mine but developed over 38 years of coding. i beat linus on that and i have done things he hasn't done so that isn't a useful comparison (a silly one IMO). so getting back to this. if i suggest something or offer an idea here, you can take it or leave it. you can discuss it in a logical way or attack me directly or my posting style. i choose to say that one way is more how i want to see and i support in candidates i recommend. the other is not something that i want my clients to see in their developers. that is my job, separating the professionals from the kiddies. and if you act like a kiddie and get all hurt because i disagree with your ideas, that is your issue and i won't be helping you out as much. you need to separate ideas from the person. i do that all the time. if you can't see that, i can't help there either. i will attack your ideas if i think they deserve it. i will not attack the person unless they attack me or other people. and getting back to the subject at hand, single letter var names. you and rob seem to keep forgetting i didn't say never use single letter names. i said the vast majority of vars don't want them so focus on those. and try to keep away from single char names. get it? try to keep away from the is the idea. you want to convey information to the reader of the code. single letter names convey no information unless they are cultural standards like $i. and those are not used as often as you all seem to think. as i said think about the thousands of names you need to pick and use - how many are $i and related? a tiny fraction. so why even support their use except for the few allowable cases? the logic railed against this is weak and emotional and not in the interest of good coding. that is my goal, better coding for all. single letter names IN GENERAL are a bad coding idea. i yelled again for emphasis. no one seems to get that point. and i am off this thread. all replies will be redirected to /dev/null. let's move on. uri -- Uri Guttman -- uri AT perlhunter DOT com --- http://www.perlhunter.com -- ------------ Perl Developer Recruiting and Placement Services ------------- ----- Perl Code Review, Architecture, Development, Training, Support ------- -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
