writes: I have worked for about a decade as a software engineer. I am almost never hired to build new software from scratch, so my work satisfaction tends to be proportionate to quality of the legacy code I have to work with. Some legacy code has been good. Most of it is bad. I know a few questions to ask during an interview to determine the code quality: Are recent technologies used? Are there code review processes? Is TDD practiced? Even so, I still encounter terrible quality code. Does Slashdot have any advice for other questions to ask? Any other ways to find out code quality beforehand?
writes: The Most Evil Technology Company
* I, for one, welcome our new corporate overlords
writes: I'd like to run a server in my home, but am not too thrilled at burning a couple of hundred watts. At the same time, if I don't leave it one, it won't be much use. Energy Star seems to concentrate on entire systems rather than on specific components. Are there other standards for high efficiency components? And what about software? I would not be able to put my server into hibernate or it won't function as a server. Are there creative ways to reduce power usage under low or zero load while still maintaining responsiveness? I'd love to hear what loyal Slashdot readers have done to slash the power consumption of their home servers.
writes: Recently, AT&T censor Pearl Jam for some anti-Bush comments during a performance.
The band fired back saying, "This, of course, troubles us as artists but also as citizens concerned with the issue of censorship and the increasingly consolidated control of the media. What happened to us this weekend was a wake-up call, and it's about something much bigger than the censorship of a rock band."
Other public interest groups have used this censorship as an argument for net-neutrality.
Ars Technica has more.
What do slashdotters think?Link to Original Source