After his amateur rocket flight in the desert (to 121,000 feet!), you asked rocket enthusiast Derek Deville about the project. Derek's responded to a selection of the best of those questions; read on below for his replies.

The San Francisco Chronicle features an interview with Google's patent counsel, Tim Porter, who argues that "... what many people can agree on is the current system is broken and there are a large number of software patents out there fueling litigation that resulted from a 10- or 15-year period when the issuance of software patents was too lax. Things that seemed obvious made it through the office until 2007, when the Supreme Court finally said that the patent examiners could use common sense. Patents were written in a way that was vague and overly broad. (Companies are) trying to claim something that's really an idea (which isn't patentable). There are only so many ways to describe a piston, but software patents are written by lawyers in a language that software engineers don't even understand. They're being used to hinder innovation or skim revenue off the top of a successful product." Porter is speaking in particular about the snarls that have faced (and still face) Android, based on Microsoft patents; he blames some of the mess on a patent regime where "you don't know what patents cover until courts declare that in litigation. What that means is people have to make decisions about whether to fight or whether to reach agreements."

You asked William Shatner questions, and Shatner replied. It's not the first time he's answered questions for Slashdot (that was in 2002), but Shatner's given a bit more insight this time into what makes an 80-year-old actor-author-sportsman-father-filmmaker tick as fast as ever. Did he mention that he's got a one-man show about to open? And a new album? Note: Typically Shatner, he's also chosen to ignore (or transcend) the usual Slashdot interview structure, and written his answers in his own style, which is why the format looks a little different from most of our interviews. Thanks, Bill. (Read on for his answers.)

A couple weeks ago, you asked questions of Stanford professor Jonathan Koomey about what has been dubbed Koomey's Law — the idea that the energy efficiency of computing doubles every 1.5 years. Read on for Professor Koomey's answers to the questions you raised.

Long-time readers will know that we try not to clutter the front page of Slashdot with much stuff about the site itself; this is a rare exception, but we hope you'll like the reason: we want your opinions. You should see above a link to take a survey about Slashdot, and (just to be heavy handed) here's the direct link. The questions there are simple, but we're going to read the answers carefully. The reminder bar up there will remain active for some time, but this story will scroll down the page like all Slashdot stories. Comments are welcome below; surveys have their limitations, after all, but please don't comment without also giving the survey a visit — if it makes sense, feel free to cut-and-paste any answers from there as comments, too. The engineers who build this site (and the editors, too!) are counting on your honest opinions and hoping for some great ideas; ideas outnumber the hours we have to do things, so we hope you'll make a case for the ways that Slashdot should change (and the ways it shouldn't!).

Michael J. Ross writes "Most computer and web programming books are written entirely by a single author, while the remaining are written by more authors, typically with each one tackling several chapters. The latter approach can suffer from redundant material undetected by editors, and inconsistency in the writing style from one chapter to the next. Yet it offers the significant advantage that the subject matter of each chapter can be presented by an authority on that topic — who can focus on making that explication the best possible, without the burden of completing an entire book. That was one of my first thoughts (and hopes) when hefting the 1112 pages and 4.1 pounds of the Definitive Guide to Drupal 7." Read on for the rest of Michael's review.

brothke writes "When it comes to a physical crime scene and the resulting forensics, investigators can ascertain that a crime took place and gather the necessary evidence. When it comes to digital crime, the evidence is often at the byte level, deep in the magnetics of digital media, initially invisible from the human eye. That is just one of the challenges of digital forensics, where it is easy to destroy crucial evidence, and often difficult to preserve correctly." Read on for the rest of Ben's review.

Last week, you asked Kevin Mitnick questions about his past, his thoughts on ethics and disclosure, and his computer set-up. He's graciously responded; read on for his answers. (No dice on the computer set-up, though.) Thanks, Kevin.

frisket writes "The JIRA issue-tracking system has been around for seven years and has proved popular in commercial as well as open-source environments owing to its licensing arrangements (free of charge to certain classes of organizations, and source code available to developers). The release of v.4 in 2009 (now at 4.4) brought some major changes to the UI and searching, a new plugin architecture, and the ability to share project dashboards outside the system. Patrick Li's JIRA 4 Essentials is a comprehensive guide to the interface and facilities that both presents the material straightforwardly and avoids the trap of just being a guide to the menus. Although it is aimed mainly at the administrator, it will also be useful for the desktop user wanting a standalone system." Read on for the rest of Peter's review.

Kevin Kelly ("Senior Maverick for Wired Magazine," among many other things) is back with answers to a selection of the questions posed to him by Slashdot readers. Read on below for his take on travel, the Long Now Foundation (including the 10,000-year clock — clocks! — that is among the foundation's projects), the future of fusion, and what to do about inevitable widespread suckage.

brothke writes "During the 1990's when Kevin Mitnick was on the run, a cadre of people were employed to find him and track him down. Anyone who could have an angle on Mitnick was sought after by the media to provide a sound bite on the world's most dangerous computer hacker. Just one example is John Markoff, who became a star journalist for his work at The New York Times, and a follow-up book and series of articles based on Mitnick. In Ghost in the Wires: My Adventures as the Worlds Most Wanted Hacker, the first personal account of what really happened; Mitnick says most of the stories around him were the result of the myth of Kevin Mitnick, and nothing more. In the book, he attempts to dispel these myths and set the record straight." Read below for the rest of Ben's review.

With CmdrTaco moving on to his temporary retirement home, the Slashdot editors who will continue to poke and prod at reader submissions (the heart and soul of this site: without readers, there'd be nothing to talk about as well as no one to talk about it) would like to offer an extended 'Thank You' to Rob, and offer some thoughts on the years so far, as well as what comes next. (Of late, though, we're lucky to have the growing contributions of Clinton Ebadi, aka Unknown Lamer, who got an oddball start on the Slashdot page a long time back.) Read on for a few words from Samzenpus, timothy, and Soulskill.

MassDosage writes "Getting Started with Audacity 1.3 by Bethany Hiitola covers the basics of using the Audacity software package for recording and editing audio. This book is written in a tutorial style and stays true to its title by covering Audacity from a newcomer's perspective with lots of diagrams and detailed explanations of how to install and setup Audacity and use its most essential features. This is all very much aimed at people who are new to audio software and are looking for a simple way to get started and be guided through creating and editing an audio recording. On the whole it achieves this but is occasionally let down by overly simplistic content and shoddy editing." Read below for the rest of Mass Dosage's review.

Kevin Kelly has for decades been involved in some of the most interesting projects I know about, and in his roles as founding editor (and now editor at large) of Wired Magazine and editor of The Whole Earth Catalog has helped spread the word about many others. Kelly is probably as close to a Rennaisance man as it's possible to be in the 21st century, having more-than-passing interest and knowledge in a range of topics from genetic sequencing and other ways that we can use measurement in pursuit of improved health to how technology is used and reused in real life. Among other projects, he's also the founder of CoolTools, which I consider to be (unsurprisingly) the closest current equivalent to the old Whole Earth Catalogs. (Disclaimer: I've had a few reviews published there, too.) (He's also one of the founders of The WELL, now part of Salon.) Kelly is also Secretary of the Board of Directors of the Long Now Foundation, the group which for years has been designing a clock to ring on 10,000 years in the future. Below, ask questions of Kelly, bearing in mind please the Slashdot interview guidelines: ask as many questions as you want, but please keep them to one per comment. He'll get back soon with his answers.

In an interview with Forbes, Activision CEO Bobby Kotick spoke about the rise and fall of the Guitar Hero franchise, saying "it became unsuccessful because it didn't have any nourishment and care." He then revealed that after effectively canceling the franchise last year, the company is looking for ways to resurrect it. "We said you know what, we need to regain our audience interest, and we really need to deliver inspired innovation. So we're going to take the products out of the market, and we're not going to tell anybody what we're doing for awhile, but we're going to stop selling Guitar Hero altogether. And then we're going to go back to the studios and we're going to use new studios and reinvent Guitar Hero. And so that's what we're doing with it now." Kotick also addressed Activision's lack of foresight regarding DJ Hero: "...in hindsight, if you step back – and it really would have been a simple thing to do – we should have said, 'Well, how many people really want to unleash their inner DJ?'"

brothke writes "Surveillance or Security?: The Risks Posed by New Wiretapping Technologies is a hard book to categorize. It is not about security, but it deals extensively with it. It is not a law book, but legal topics are pervasive throughout. It is not a telecommunications book, but extensively details telco issues. Ultimately, the book is a most important overview of security and privacy and the nature of surveillance in current times." Read below for the rest of Ben's review.

MassDosage writes "Software Build Systems by Peter Smith is a well written, albeit rather lengthy book that covers the intricacies of systems used to build software. It tries to do this in a technology-neutral manner where possible but covers existing tools like Ant, Make and Scons as a means of illustrating the various concepts covered instead of just focusing on theory. The real world examples illustrate building Java, C/C++, C# and Python software and cover scaling up from small builds with tens of source files up to massive builds with tens of thousands. All of the technologies used are introduced in some depth which newcomers should find useful but experienced build developers may want to skim over." Read below for the rest of MassDosage's review.

Last week, you asked questions (many rather pointed!) of Amir Taaki, co-founder of Bitcoin Consultancy, which develops Bitcoin related services, exchanges and Bitcoin itself. (They also own Britcoin.co.uk.) Says Taaki: "When creating video games I spent much time imagining tools to make artists lives easier, and how we could keep funding developers to write free software. One contribution of mine to the community was a site where developers could get funded for developing features and I'd love nothing more than to pay people to write free software." With regard to Bitcoin, similarly, "We need fulltime developers thinking about the problems and solutions needed to keep this system running. We aim to get all the creative thinkers from the community and provide a mechanism for enabling their work." Below find his answers to the questions readers raised.

CoryFoy writes "As someone who has been closely involved in both the 'agile software' movement as well as the 'Software Craftsmanship' movement, I have been following the work of Robert Martin for some time. So I was quite interested when I got my copy of his latest book Clean Coder where he 'introduces the disciplines, techniques, tools and practices of true software craftsmanship.' Would his book live up to being a guide for the next generation of developers, or would it go on my shelf as another interesting book that I had read, once?" Read below for the rest of Cory's review.

snydeq writes "Deep End's Paul Venezia discusses the two ways to succeed in IT: through proficiency and hard work, a road that often leads to unending servitude, or the other way; with little effort or proficiency at all. 'I hate to say this, but a number of people in IT positions work harder to make it seem like they're busy as beavers than doing actual work. Quite often this dysfunction starts at the top: When an IT manager doesn't know the technology very well, he or she may hire folks who have no idea what their job is other than to show up every day and answer the occasional email, passing questions along to others with more technical abilities, or to their contacts at the various hardware and software vendors. People like these populate many consulting companies. They rely almost completely on contractors to perform the actual work, serving as remote hands in a real crisis and as part of a phone tree for less pressing issues.'"