A milestone is set to occur this week in the Turner household: After more than half a year of dedicated effort, we will complete a full viewing of the entire Buffyverse. We’re just four episodes of “Angel” away from the end of the tunnel, and then our 256-episode, 169-hour journey will be complete. And people say geeks don’t have lives …
Elsewhere, the wacky world of software continued to churn out stories, of course.
Show me the money!
The conventional wisdom is that the days of high-paying software jobs for newly minted computer science undergrads are over, as work flees overseas. But, if you take the numbers in this recent blog posting seriously, there’s still good money to be made if you can attract the interest of big players like Google, Microsoft or Amazon.
Software is still a great job, evidently, with starting salaries around $100K. To put this in perspective, a newly minted PhD can expect to earn around $50K as a postdoc at a university. Perhaps it’s not surprising, therefore, that students declaring a CS major are up 10% over last year.
Anyone got JavaDoc for org.apache.judicial.proceedings.JudgeBriefing?
As frequently documented in this space, collisions between the law and software development are occurring more and more frequently. For jurists required to oversee such cases, understanding the nature of the beast is becoming a necessity, so it should have been expected that the judge trying the Oracle v. Google Java suit would need some background on the language. That’s just what happened this week, as William Alsup of the U.S. District Court in San Francisco was given the lowdown on the details of virtual machines and class libraries.
The influence of this new knowledge on the legal community is already being felt. Last week, a circuit judge in Texas informed the lawyers in a case that he was wrapping the testimony in a try/catch block to handle IllegalArgument exceptions, and another in New Jersey will no longer accept written motions with a CCN > 20.
Next: Twyla Tharp hired as Google’s chief architect
One of the trickiest challenges that developers face is explaining how software works to non-programmers. Thus, it was refreshing to see a totally new approach to documenting algorithms this week. Here, for your viewing pleasure, are a number of sorting approaches, represented in dance.
While I usually find the comments on Slashdot somewhat inane or even nasty, someone had my all-time favorite comment on this: “See, that’s what you get with interpretive dance. A compiled dance would be much more efficient.”
Please send tips and leads here.