just wondering, hangning up and listening...ank
If you must have a pong, Heiko Selber's honourable mention beats Piotr Dabrowski's hands down, in my opinion -- yours is pretty classy Piotr but I prefer the full field, myself (same reason I detest tablet-ized interfaces).
But I don't think the logo should go crazy on sideways references; hence I cannot vote for any of the other "presented" options. My top 6 are, therefore, #1, #7 and #9 from the accepted list, and Pocholo Peralta's, Erik Berglund's and Pete Mendoza's honourable mention entries.
* #1 refers to these polls, a strong feature of slashdot from so long ago that it might as well be the beginning.
* #7 has classic lines and is self-referential to its topic
* #9 is almost Matrix-y and ASCII-art-ish without being a 100% send-up of either
* I preferred Pocholo Peralta's logo over Sean Murphy's #31 because I view animated graphics, generally, as abominable. This works in the 15th anniversary theme tastefully and effectively.
* Erik Berglund's logo embodies slashdot's quirky take on everything -- give it a twist!
* I like Pete Mendoza's contribution for the same reason I prefer #7 to the ones to vote for. I'm disappointed that nobody used the default Slashdot logo font in the same way, actually.
I think I'd have to vote for #1, as much as anything because I can suffix my vote with
you insensitive clod...ank
In 27 years of professional software development I have watched numerous co-workers succumb to various RSIs, require ergonomic keyboards just to be able to bear the pain of working. The one difference I notice between me and these unfortunate folks is this: I avoid using the mouse.
I use keyboard shortcuts, I prefer a text editor that allows me to do everything including navigating from a standard QWERTY keyboard (in my case, the One True Editor, vim but there are other options -- I've also used BRIEF, OS-9's stylograph and IBM's Personal Editor in my time). Hot-keys, short-cut keys, accelerators, anything that keeps my hands on home row have been my safeguard.
It's also fair to say that I have been playing piano since I was 5 but I still think that "stay away from the mouse" is the best advice anyone will give you.
Because when you learn it you may gain a whole new way of looking at the languages you already know.
Sorry... just to be clear "This kind of comment" was referring to the question, "Why is Wikipedia so ugly?", not to parent. I agree with parent 100% and more.
This kind of comment comes from the same kind of morons who brought us the re-tooling, for instance, of GMail. It was great (to use) the way it was. Now I hear nothing (NOTHING!) but complaints about it (or blank stares which when probed yield statements of powerlessness). If the underlying code was ugly, the first update cycle should have been to upgrade the code in a way that none of the users would notice.
Note to Jimmy Wales: resist the UX-groupthink mob who would tell you to make Wikipedia more tablet friendly. If it's ugly, it's ugly the way the old White Pages were ugly. Ugly and informative. The way a real newspaper used to be ugly (especially the front sections up to where the editorials, letters and Op-Ed pieces lay): ugly, information rich and informative.
Note to the groupthink mob: if you must make something tablet-friendly, make sure it's still screen friendly during the design before you foist it on those of us who haven't caved-in to constant computing through tablet ownership.
<quickly hitting submit before going off and doing something real>...ank
Agile is just a structure. Like anything else, it's only going to be as good as the people you put in place to execute it. A properly constituted agile team will put documentation (of designs, code, deployment, whatever) up as stories/tasks that need to be accomplished right alongside working features. Documentation is an end-product just as surely as working code and unit tests are.
If the team doesn't identify those tasks and sign up for them, you hired the wrong people. Reform your recruiting process before you blame a process that delivers a working solution at the end of every sprint. And if your so-called Agile doesn't pretty much do that, then you really are being scammed.
(I've been a developer for 26 years; some form of Agile has covered the most productive and enjoyable parts of my careeer)
You are in the hall of the mountain king.