What is Digg?64 Comments
- rodrigo74, on 10/12/2007, -3/+43No, this is not blogspam. This is an interesting article that was originally published in a blog. What should the guy do? Have it published at NYT so he can put that link here instead?
- DeskFlyer, on 10/12/2007, -2/+42If I looked like Angelina Jolie, I'd be too busy fondling myself to care.
- rm999, on 10/12/2007, -5/+34I think there needs to be a rule on Digg - when someone says something stupid as the first comment (and this appears to happen about 75% of the time), only one person is allowed to respond. I am tired of this pattern in the comments:
stupid comment, -276
.....obvious reply #1, 362
.....obvious reply #2, 287
.....obvious reply #3, 151
.....insightful comment #1, 15 - SavageBlackCat, on 10/12/2007, -4/+271. speak english
2. learn how to write
3. dress like a professional, not a frat bum
4. bathing should be done with soap
5. it's permissible for a developer to show up before noon - Gizza, on 10/12/2007, -2/+21WTF? Did it take you 8 minutes to write that comment and this is just some bizarre coincidence. Or did you actually just directly copy the comment above?
- Niten, on 10/12/2007, -4/+15Well the article was informative and was not nested between layers of ads, so I don't see any reason to go around shouting "blogspam". Really, did you find the article any less insightful due to the fact that it happened to be served using WordPress?
It looks like somebody has written something worthy of the front page of Digg on *GASP* a _blog_, of all things. I mean, who would have thought? - mwadhera, on 10/12/2007, -3/+12who taught you to spoke ruby?
def pluralize(number, word); return word + 's' unless number.eql? 1; return word; end
99.downto 1 do |i|
2.times do; puts i.to_s + ' ' + pluralize(i, 'bottle') + ' of beer on the wall'; end
puts 'You take one down and pass it around,'
puts (i-1).to_s + ' ' + pluralize(i, 'bottle') + " of beer on the wall"
puts ""
end - roosterjm2k2, on 10/12/2007, -1/+10I'm with you on all but the "Dress Like a Professional"
Dressing in a monkey suit makes you no better a developer. It makes you uncomfortable. Sadly, the higher ups in most big companies don't get this. Thats why I like working for the place I do... 8 people. Plenty of work. Relaxed atmosphere. Work in jeans and tshirts and vans. You know why? Because the clothes don't make the man (or the developer), and for the most part, the clients never see us anyways. We're dressing up to impress ourselves (Well, not me, but figuratively)
I almost feel pity for developers that have to dress up all the time. - underthelinux, on 10/12/2007, -0/+7... but quite uncommon.
- wassim2k, on 10/12/2007, -0/+7Common sense is free.
- NICU, on 10/12/2007, -2/+9Wow I definitely agree with every point on that list. When a new hire comes in and doesn't ask questions I get nervous. When I started out I was asking questions about everything. Not asking for help only makes the people around you nervous, they're not impressed when they go through all your check-ins after you leave.
If you're new and your company doesn't routinely do code reviews - ask for them, ask for design help, and always get some criticism. If someone tells you that everything's perfect the first time then they either don't care about your work or never checked it. - waxoff, on 10/12/2007, -2/+8I've been burned by the "improve things straight away" bug. Who knew using CVS (before SubVersion existed) and using build scripts would be controversial?
- Spr0k3t, on 10/12/2007, -1/+7Well stated savageblackcat. Unfortunately, you will find a few outsiders in the system wherever you go.
- roosterjm2k2, on 10/12/2007, -0/+6The environment has to be right for asking questions too though.
And sometimes, too many questions can be just as damning as too little. Even non-technical (procedural) questions, can kinda make me think twice about someone.
When I was growing up, I heard the saying "The only stupid question is the one you don't ask." Well...No, I've heard alot of stupid questions.
And the seniors have to be willing to answer (At least the good ones) the questions too. If the seniors have the elitist "im too busy" attitude, then it will never work. Part of the responsibility of a senior is to help mold the juniors. - ucg1, on 10/12/2007, -1/+7If you're wearing a tie, you're overdressed for a developer.
I tend to dress somewhere between casual and business casual, but usually more on the "casual" end of that. Some people in my office where shorts, flip-flops and a crappy t-shirt. They look pretty crappy, but they get the job done and are respected for their abilities not their appearances.
I'd hate to have to work in an environment that forced me to overdress. - ucg1, on 10/12/2007, -0/+5@DivisibleByZero
You're pretty stupid for wearing that shirt at all... - DivisibleByZero, on 10/12/2007, -0/+5My company's pretty lax about the dress code. I'm wearing shorts and a t-shirt right now. Every once in a while I come in wearing a suit to keep them on their toes; make it look like I've got a job interview somewhere else.
The only time I've been criticized for my clothes was when I wore my "Speak English or Die" shirt, and customers from Portugal were in the office.... Usually they send an email the day before, but that time they sent it at 9AM the day of. Oops. - SavageBlackCat, on 10/12/2007, -0/+4CV = curriculum vitae
http://web.mit.edu/career/www/guide/cv.pdf - Jellybob, on 10/12/2007, -1/+5So true - one of the first things I tried to do when I started my first job as a programmer was to get everyone using Subversion, but I made the mistake of not taking the time to find out what the workflow was like, and it crashed and burned. A year on, and we're still not using any sort of version control.
- IHatePants, on 10/12/2007, -0/+3I'd be too busy fondling you too.
- havensbreeze, on 10/12/2007, -1/+4well, I thinks these point do not only apply to Junior programmers.... Even a senior programmer should questioning its own attitudes from time to time...
- insovietrussia, on 10/12/2007, -1/+4Yeah, you're fired.
- rodrigo74, on 10/12/2007, -1/+3Then the best is to understand what's the problem exactly (instead of calling it "a problem"), try to figure out a decent workaround, and say something like "there's this specific problem with this library, but we could try this and that, while we don't get a fix from them".
- SavageBlackCat, on 10/12/2007, -1/+3No, it means be upfront. All developers are more than familiar with syntax lag.
- OnipSemaj, on 10/12/2007, -0/+2I am developer myself. I know Java, SQL, Perl, etc. I think I know them well and am actually quite successful. But in order to become successful, you need to spend alot of time. The problem is there are some many new technologies out there, that its hard to find a developer who knows EXACTLY what your looking for. So many dumb-ass companies want their candidates to know everything specifically on their list. They are missing the point.
This guy makes a good point. If your are a programmer/developer/software engineer, it means you should have the ability to learn and implement any programming language. Period. If not, you need to start selling insurance or something. - rodrigo74, on 10/12/2007, -0/+2CV means Canned Vodka, you know, the bribe we always send to a company when we want to work there.
- bpapa, on 10/12/2007, -0/+2Guy kinda crosses his wires with the "Oh yeah, sure I know all about that technology that you just asked me if I know, even though I've never actually used it" thing because I think most programmers only do that on interviews. Once you're in there like swimwear there is no real reason to lie about that kind of stuff. At least from my couple of years of professional experience, I see more empty, pressured promises from management to upper management than programmers lying about knowing a certain kind of technology.
- Jellybob, on 10/12/2007, -0/+2In that case you stay honest, saying something like "I used it a few years ago, but I don't remember all the details." - they'll appreciate it a lot more then claiming to know the language, only to find out you can remember nothing but how to write an if statement.
The key thing most companies are looking for when interviewing a new hire is an ability to learn, since even if you're the worlds best [language x] developer, likely there will be some quirks in their applications that you just won't know about until you hit them. - KoZo, on 10/12/2007, -1/+2Oh man, what he says is true. But sometimes you know the language, you have tried it, but after say 1-2 years of not using it, of course you'll forget about it but still you know it, does that mean I have to say, "i dont know about that language?"
- motters, on 10/12/2007, -0/+1I don't agree with the "don't rock the boat" advice. Programming inefficiency is programming inefficiency, and often someone joining a company can have a more objective perspective on the situation, unclouded by corporate politics or historical legacy.
- rodrigo74, on 10/12/2007, -0/+1"The internet says that to earn the respect of your peers you should have these qualities"
Do you talk with the Internet by email, or phone? You could at least link to the original article. - underthelinux, on 10/12/2007, -1/+2'If you use excuses like "the users are stupid", "the 3rd party library is buggy" or any of the other classic programmer alibis it will only reflect poorly on yourself.'
So then, how do you avoid this? What if it is genuinely the fault of 3rd party or data source ? You can't really plan for each and every situation that could occur as a result of (poor data, bad libs, etc.). - over1, on 05/31/2008, -0/+0Thanks
http://rmooosh.net/video
http://rmooosh.net/games
http://rmooosh.net/link
http://rmooosh.net/vb - rubyminer, on 10/12/2007, -5/+5Found this on the Ruby ML :
@c=(@b='#{n>0?n: :No} bottle#{:s if n!=1} of beer')+' on the wall'
eval %{puts"#@c, #@bnTake one down, pass it around,",(n-=1;"#@c.nn");}*n=99
145 bytes of Ruby... pretty crazy. - mhmdkhamis, on 10/11/2007, -0/+0http://links.paramegsoft.com/
http://fr.paramegsoft.com/ - chaoskaizer, on 10/12/2007, -0/+0"Don't expect your CV to give you instant respect"
very good read. - drbrutus, on 10/12/2007, -0/+0Its a good article, but at times politics and priority comes into picture and spoils the whole thing. "Dont try to influence people by words, prove it yourself" .
- hguhf, on 12/28/2007, -0/+0http://www.aljayyash.net
http://forum.aljayyash.net
http://www.al-games.net
http://english.al-games.net
http://www.al-dreams.com
http://www.al-health.com - salehali, on 07/01/2008, -0/+0http://www.y4yy.com/
http://games.y4yy.com/
http://games.up-00.com/
http://tv.y4yy.com/
http://www.up-00.com/
http://www.up-00.net/
http://www.yallaup.com/
http://dir.y4yy.com/
http://9or.y4yy.com - drbrutus, on 10/12/2007, -1/+0check this article
http://drbrutus.blogspot.com/2007/03/software-job-perspective-work-to-get.html - inactive, on 10/12/2007, -3/+1What's a CV?
Oh, is it the British version of a resume? - inactive, on 10/12/2007, -3/+1Lemme guess, this is a result of a 'group digg' by the blogger's friends huh
- wvdavis, on 10/12/2007, -3/+1This list can be applied to every career path out there, not just programmers.
- OrangeTide, on 10/12/2007, -5/+3why not in befunge?
http://en.wikipedia.org/wiki/Befunge - Jellybob, on 10/12/2007, -4/+0Get yourself a copy of The Ruby Way (I can't remember who it's by at the moment), it describes how to write your code in a way that takes advantage of Ruby's features to create programs that read like poetry.
-
Show 51 - 59 of 59 discussions
Digg is coming to a city (and computer) near you! Check out all the details on our 
© Digg Inc. 2009
— Content created and posted by Digg users is