Vladimir Sedach writes "Aside from authoring narrowly focused technical books, teaching university courses, or mentoring others in the workplace, programmers don't often get a chance to pass on the knowledge of the practise of programming as a profession. Peter Seibel's Coders at Work takes fifteen world-class programmers and distills their wisdom into a book of interviews with each of them." Keep reading for Vladimir's review.

imamac writes "Startup Weekend was a 54-hour coding marathon held on Microsoft's campus last weekend. It was designed to encourage the use of MS programming technologies. However, the winner of the contest was an iPhone app: '"Awkward," whispered Startup Weekend organizer Clint Nelsen into the microphone upon announcing the top vote getter.'"

igrigorik writes "First the Netflix challenge was won with the help of ensemble techniques, and now the GitHub challenge is over, and more than half of the top entries are also based on ensembles. Good knowledge of statistics, psychology and algorithms is still crucial, but the ensemble technique alone has the potential to make the collaborative filtering space a lot more, well, collaborative! Here's a look at the basic theory behind ensembles, how they shaped the results of the GitHub challenge, and how this pattern can be used in the future."

EtaCarinae writes "Nokia didn't succeed in convincing Riverbank to change its licensing terms on PyQt, and so decided to create their own LGPL'ed version of it. From the FAQ at the PySide site: 'Nokia's initial research into Python bindings for Qt involved speaking with Riverbank Computing, the makers of PyQt. We had several discussions with them to see if it was possible to use PyQt to achieve our goals. Unfortunately, a common agreement could not be found , so in the end we decided to proceed with PySide.'"

RazvanM writes "At the beginning of this month the Mac OS X 10.5.8 closed a kernel vulnerability that lasted more than 4 years, covering all the 10.4 and (almost all) 10.5 Mac OS X releases. This article presents some twitter-size programs that trigger the bug. The mechanics are so simple that can be easily explained to anybody possessing some minimal knowledge about how operating systems works. Beside being a good educational example this is also a scary proof that very mature code can still be vulnerable in rather unsophisticated ways."

An anonymous reader writes 'At my company, our mis-implementation of Agile includes the employment of some of our most highly-paid, principal engineers as ScrumMasters. This has effectively resulted in a loss of those engineering functions as these engineers now dedicate their time to ScrumMastery. Furthermore, the ScrumMasters either cannot or do not separate their roles as Team Leads with those of ScrumMastery and — worse — seem to be completely unaware that this poor implementation of Agile development is harmful to our velocity. To date, I have chalked this up to poor leadership, a general lack of understanding of Agile, and an inability to change from traditional roles left over from the waterfall development mode. In addition, I have contended that, for a given Scrum Team, the role of ScrumMaster should be filled by someone of lower impact, such as an intern brought in specifically for that purpose. But I would like to put the questions to Slashdotters as to whether they have seen these same transitional difficulties, what the results have been at their respective companies, or whether they just plain disagree with my assertion that principal engineers should not be relegated to the roles of ScrumMasters.'

Underholdning writes "With the DOJ approving Oracle's Sun buyout, the question arises what Oracle might want to do with Sun's hardware business. It's no secret that what Oracle wanted was the software part. Now The Inquirer is running a story claiming that Oracle will sell the hardware business of Sun to HP. This will give Oracle a juicy check while HP can increase its services. Larry Ellison denies that it will take place, but a source for CNN claims otherwise."

Gamasutra is running an article with a collection of anecdotes from game developers who had to employ some quick and dirty fixes to get their products to ship on time. Here's a brief excerpt: "Back at [company X] — I think it was near the end of [the project] — we had an object in one of the levels that needed to be hidden. We didn't want to re-export the level and we did not use checksum names. So right smack in the middle of the engine code we had something like the following. The game shipped with this in: if( level == 10 && object == 56 ) {HideObject();} Maybe a year later, an artist using our engine came to us very frustrated about why an object in their level was not showing up after exporting to what resolved to level 10. I wonder why?" Have you ever needed to insert terrible code to make something work at the last minute?

ChelleChelle writes "During the past half-decade there has been an explosion of creativity in revision-control software, complicating the task of determining which tool to use to track and manage the complexity of a project as it evolves. Today, leaders of teams are faced with a bewildering array of choices ranging from Subversion to the more popular Git and Mercurial. It is important to keep in mind that whether distributed or centralized, all revision-control systems come with a complicated set of trade-offs. Each tool emphasizes a distinct approach to working and collaboration, which in turn influences how the team works. This article outlines how to go about finding the best match between tool and team."

dotancohen writes "Here's an exercise: Write a GPLed server for solving Freecell that the graphical game would communicate with using TCP/IP or a different IPC mechanism. Easy, right? Except for that pesky licensing bit. Our own Shlomi Fish gives an overview of the various options in picking up a licence for one's FOSS project, and tries to give some guidelines choosing one."

k33l0r writes "The BBC is reporting that the US Justice Department has approved Oracle's takeover of Sun Microsystems. The acquisition gives Oracle control over (or a leading role in), among other things, Java, MySQL, (Open)Solaris, ZFS, OpenOffice, and the NetBeans IDE. 'The European Commission has still to rule on the deal, a step that will be required before it can close. That body has indicated it will issue an initial opinion on Sept. 3, according to the Wall Street Journal. It may OK the deal at that time or launch a four-month probe of it. ... The Justice Department ruling came earlier than expected, a possible response to Sun's declining revenues and precarious business position in a steep recession, as the required reviews proceeded.' We first discussed the deal back when it was announced in April."

murphee writes "Flight delayed again? Should have asked FlightCaster, a new site using statistical analysis to predict the delay of your flight in real-time. What's even better, the services is fully buzzword compliant: it's built with Clojure, distributed with Hadoop, served with Rails, and hosted on Heroku. This interview with one of the FlightCaster developers gives the gory details on architecture, Clojure tips, and your boss a reason to let you have all the multimethods and macros you can eat. Seems like now that O'Reilly's publishing a LISP book, the Age of Parenthesus has come..."

Ant writes "The Linux Foundation's report (PDF) on who writes Linux — "... Linux isn't written by lonely nerds hiding out in their parents' basements. It's written by people working for major companies — many of them businesses that you probably don't associate with Linux. To be exact, while 18.2% of Linux is written by people who aren't working for a company, and 7.6% is created by programmers who don't give a company affiliation, everything else is written by someone who's getting paid to create Linux. From top to bottom, of the companies that have contributed more than 1% of the current Linux kernel, the list looks like this: ..."

angry tapir writes "MenuetOS is an operating system written entirely in assembly language. As a result it's extremely quick and compact (it can even fit on a floppy disk, despite having a GUI). It can run Quake. Two of the developers behind MenuetOS took time out to talk about what inspired them to undertake the daunting task of writing the operating system, the current state of Menuet and future plans for it."

igrigorik writes "Most web applications are built with the assumption that the client / browser is 'dumb,' which places all the scalability requirements and load on the server. We've built a number of crutches in the form of Cache headers, ETags, and accelerators, but none has fundamentally solved the problem. As a thought experiment: what if the browser also contained a Web server? A look at some of the emerging trends and solutions: HTML 5 WebSocket API and ReverseHTTP."

inkslinger77 notes a Computerworld interview with Martin Odersky on the Scala language, which is getting a lot of attention from its use on high-profile sites such as Twitter and LinkedIn. The strongly typed language is intended to be a usable melding of functional and object-oriented programming techniques. "My co-workers and I spend a lot of time writing code so we wanted to have something that was a joy to program in. That was a very definite goal. We wanted to remove as many of the incantations of traditional high-protocol languages as possible and give Scala great expressiveness so that developers can model things in the ways they want to. ... You can express Scala programs in several ways. You can make them look very much like Java programs which is nice for programmers who start out coming from Java. ... But you can also express Scala programs in a purely functional way and those programs can end up looking quite different from typical Java programs. Often they are much more concise. ... Twitter has been able to sustain phenomenal growth, and it seems with more stability than what they had before the switch, so I think that's a good testament to Scala. ... [W]e are looking at new ways to program multicore processors and other parallel systems. We already have a head start here because Scala has a popular actor system which gives you a high-level way to express concurrency. ... The interesting thing is that actors in Scala are not a language feature, they have been done purely as a Scala library. So they are a good witness to Scala's flexibility..."

mr_sifter writes "There's a large lexicon of monosyllabic, four-letter words for describing something you don't like — but only PC gamers use the word 'port' with such a fervent degree of repulsion. Common complaints about console ports include meager graphics options, dodgy third-person camera angles, poorly-thought-out controls and sparsely distributed save points. In this feature, Bit-tech talks to developers of games such as Dead Space, Red Faction and Tales of Monkey Island to find out why porting games between the three major consoles and the PC is so difficult. Radically different CPU, graphics and memory architectures play their part, as do the differences in control methods and the rules Microsoft, Sony and Nintendo set about how games should work on their systems."

ttsiod writes "I want to 'lure' my nephews/nieces towards Science and Engineering (to whatever extent that's possible, in the age of consoles). To that end, I have coded simple physics simulations, like falling snow, exploding fireworks, and 1D/2D wave simulations. My efforts are here, in the form of portable SDL mini-programs (GPL code, compilable under Windows, Linux, Free/Net/OpenBSD, Mac OS/X and basically every OS with GCC and SDL). Try them out, and do offer any suggestions on other programs that can trigger scientific interest in young minds. Myself, I am teaching them Python, so that they can code 'fireworks' on their own."

An anonymous reader writes "I am an author working on a technical book about an open-source software package. I am looking for a publisher, and I would like to hear experiences from any Slashdot authors. Who are the best publishers to work with and why are they great? Who are the worst publishers in the tech book business, and what nightmare/horror stories can you tell us about them? Any publishing company in particular you recommend avoiding? Any gems of advice (rights reversion, etc.) you can provide for first-time tech book authors?"

snitch writes with this snippet from InfoQ about the current state of Google Wave: "With the Google Wave Preview scheduled for public availability on September 30th, Wave API Tech Lead Douwe Osinga has posted on the Wave Google Group about what the team has been working on along with some future directions. Up until now, with the limited availability of testing accounts there have been complaints on the Google Group from users that wanted to get their hands on this new technology but didn't have access to the sandbox. As Douwe explains, the team has been busy all this time with stability issues and more."