Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:Audiophile market (Score 4, Funny) 418 418

Unbelievable. From TFR:

So do Ethernet cables have their own sound? This is no longer a question but a statement. The cable between switches is less important than the ones connected to the end points (NAS and/or streaming device), but a decent type like the AudioQuest Carbon is certainly worth the price in high end systems.

+ - Linus Torvalds No Longer Ranked in the Top 100 Linux Kernel developers->

darthcamaro writes: The Linux Foundation's Who Writes Linux report is now out and after 22 yrs leading Linux, Linux creator Linus Torvalds this year has fallen out of the list of top 100 developers in terms of code contributions.

Torvalds currently ranks 101st on the latest "Who Writes Linux" report for number of patches generated from the Linux 3.3 to the Linux 3.10 kernel releases. Topping the list is Linux kernel developer H Hartley Sweeten with 2.3 percent of changes. Sweeten is followed by kernel developer Mark Brown, who contributed 1.5 percent of changes.


Link to Original Source
Programming

+ - CompSci researchers: What Developers Call "Agile" Often Isn't->

Esther Schindler writes: "When sociological researchers studied the cultural effects of Agile methodologies on workforces, they made two unanticipated discoveries: One, companies adopting Agile actually struggle more to cope with the side-effects. Two, development teams that succeed in producing better products and pleasing customers aren’t exactly using Agile after all. In “Agile” Often Isn’t, Scott Fulton delves deep into the findings. For example:

Entitled “Agile Undercover,” the first report from Hoda and her colleagues demonstrated conclusively that Agile development teams were failing to communicate with their customers — not just occasionally, but mainly. And in order to ameliorate the impact of these failures, teams and their companies were making active, intentional efforts to keep customers in the dark about their development practices, including their schedules of deliverables.

There's more. A bunch more."
Link to Original Source

Simplicity does not precede complexity, but follows it.

Working...