This is the most important tech story of the week, and everybody has chosen to write about it. This just happens to be the one I’m linking to. It’s by Tim Wu on the New Yorker’s Elements blog.
This is the most important tech story of the week, and everybody has chosen to write about it. This just happens to be the one I’m linking to. It’s by Tim Wu on the New Yorker’s Elements blog.
Tim Bray: Software in 2014
Solid summary of where things stand right now.
Update: Sam Ruby follows up.
Felix Salmon: Netflix’s dumbed-down algorithms
Good piece on the evolution of the Netflix user experience, necessitated by the transition from the “rent movies by mail” model to the streaming content model, and the licensing fees for streaming content online. I find that Netflix is OK if you just want to watch something, and mostly terrible if you want to watch a specific thing. The Netflix experience has been changed to discourage you from attempting the latter.
Camille Fournier: 2013: The Constant Introspection of Management
Nice post on the hard parts of being a manager. One thing I’d add is that as a manager, the mistakes you make all too often have an impact on real people, an impact that’s impossible to undo. If you put someone on the wrong project and they spend six months not really learning anything, that’s six months they can never have back. It’s a tough job.
Katie Siegel: It’s Not “Too Late” for Female Hackers
Paul Graham’s comments in an interview behind the paywall at The Information (and unflatteringly excerpted by ValleyWag) have been the subject of much discussion this week. Siegel’s post gets at what was really problematic about them. I’m one of those people who started programming at age 13, and it has always been easy for me to advocate hiring people like myself, for exactly the reasons Paul Graham gives. Siegel ably makes the point that this line of thinking is unfair to everybody who doesn’t fall into his select group, but I’d argue further that it’s also just bad business. More on that later.
Update: Paul Graham says he was misquoted. I’m glad Graham cleared things up. In his update, Graham says:
If you want to be really good at programming, you have to love it for itself.
That’s a sentiment I agree with completely. One reliable indicator that a person loves programming for itself is that they started as a kid. The problem arises when we treat that as the only reliable indicator, which Graham does, at least based on this passage from the transcript:
The problem with that is I think, at least with technology companies, the people who are really good technology founders have a genuine deep interest in technology. In fact, I’ve heard startups say that they did not like to hire people who had only started programming when they became CS majors in college. If someone was going to be really good at programming they would have found it own their own. Then if you go look at the bios of successful founders this is invariably the case, they were all hacking on computers at age 13.
Philip Walton: Interviewing as a Front-End Engineer in San Francisco
Walton reacts to the types of questions he got interviewing for front-end developer positions with Internet companies. He was asked lots of abstract questions and few questions about the practicalities of front-end development. I think that it’s a mistake to focus too much on a skills match when interviewing candidates, but I also think that you should verify the skills candidates claim to have in the interview process. In other words, a company that mostly uses Python shouldn’t be afraid to hire Ruby developers, but they should make sure that those Ruby developers really can program in Ruby. Front-end skills are more generalized, and it seems crazy not to interview front-end developers about those skills.
Charlie Stross: Why I want Bitcoin to die in a fire
BitCoin is one of those things I’ve found vaguely irritating since the beginning. Stross has a strong list of legitimate reasons to be irritated. Relatedly, this post by Jason Kuznicki explains why BitCoin is likely a speculative bubble.
Patent war goes nuclear: Microsoft, Apple-owned “Rockstar” sues Google
In 2011, Microsoft, Apple, RIM, Ericsson, and Sony (basically everyone not in the Android camp in the mobile handset business) teamed up to buy Nortel’s patent portfolio. Today they filed a suit to recoup some of that investment, suing Google and six Android handset makers for patent infringement. Interestingly, they’re not suing them for violating a telecommunications patent, but rather for patents related to search advertising. I hope Google fights this one to the bitter end and wins.
(And yes, I know that Google has been on the offensive side in patent lawsuits as well. My stance is simple. I’m for the utter collapse of the patent system, and failing that for the defendant in every case.)
Mike Ash: ARM64 and You
I’m linking to this, because it’s first class nerdery, giving real insight into CPU design and performance. I always operate many layers of abstraction above this, but I find it absolutely fascinating. By the way, the comments on this post are a tonic against the general pessimism about blog comments.
© 2024 rc3.org
Theme by Anders Noren — Up ↑
Peter Seibel on code reading
Code is not literature
Interesting thoughts on code reading and how we should educate ourselves by exploring code that we didn’t write, from Peter Seibel.