| Kevjs1982's shared items in Google Reader | |
|
|
|
The list goes on and on. Reasons for failure on a software project are legion. At the end of the development cycle, you end up with software that is a pale shadow of the shining, glorious monument to software engineering that you envisioned when you started. It's tempting, at this point, to throw in the towel -- to add more time to the schedule so you can get it right before shipping your software. Because, after all, real developers ship. I'm here to tell you that this is a mistake. Yes, you did a ton of things wrong on this project. But you also did a ton of things wrong that you don't know about yet. And there's no other way to find out what those things are until you ship this version and get it in front of users and customers. I think Donald Rumsfeld put it best:
As we know, In the face of the inevitable end-of-project blues -- rife with compromises and totally unsatisfying quick fixes and partial soutions -- you could hunker down and lick your wounds. You could regroup and spend a few extra months fixing up this version before releasing it. You might even feel good about yourself for making the hard call to get the engineering right before unleashing yet another buggy, incomplete chunk of software on the world. Unfortunately, this is an even bigger mistake than shipping a flawed version.
Instead of spending three months fixing up this version in a sterile, isolated lab, you could be spending that same three month period listening to feedback from real live, honest-to-god, Now, I'm not saying you should release crap. Believe me, we're all perfectionists here. But the real world can be a cruel, unforgiving place for us perfectionists. It's saner to let go and realize that when your software crashes on the rocky shore of the real world, disappointment is inevitable … but fixable! What's important isn't so much the initial state of the software -- in fact, some say if you aren't embarrassed by v1.0 you didn't release it early enough -- but what you do after releasing the software. The velocity and responsiveness of your team to user feedback will set the tone for your software, far more than any single release ever could. That's what you need to get good at. Not the platonic ideal of shipping mythical, perfect software, but being responsive to your users, to your customers, and demonstrating that through the act of continually improving and refining your software based on their feedback. So to the extent that you're optimizing for near-perfect software releases, you're optimizing for the wrong thing. There's no question that, for whatever time budget you have, you will end up with better software by releasing as early as practically possible, and then spending the rest of your time iterating rapidly based on real world feedback. So trust me on this one: even if version 1 sucks, ship it anyway.
Jenson Button seals the drivers' championship with a superb recovery drive at a dramatic Brazilian GP won by Red Bull's Mark Webber. Brawn GP becomes the first team to clinch the Formula 1 constructors' championship in their maiden season. Thanks to Matt Moore from The Telegraph who featured a couple of pictures from my blog for a article on Guerilla Rail & Road Signs. They're spoof signs from around the world which fight back against ones we face each day telling us what or what not to do. ![]() He featured one of my favourites from Gatwick Express. Also the alternative Penalty Fares photo was selected: ![]() Thanks again to Fimb & Peter F who sent both of those into me. Although this one taken by James Whatley wasn't featured in the article, I think would have been a contender. ![]() To me, great spoof signs, are ones that you hardly notice, but when you do, you start looking around the carriage wondering if other people have seen them too. You then start getting hopeful that some tourists might also see them & ask fellow passengers or staff what the deal is with them. You kind of hope they will appear in blogs around the world or in letters back to friends & families. "You know in London the subway is so crowded people have sit on each other's laps. It's true I saw it. There was a sign and everything". If you see any other spoof signs on your Tube or rail journey please let me know. In the meantime enjoy the signs in the Telegraph. The first fruits of the Galileo project are being seen, as the EU launches its EGNOS network What kinds of music does BBC radio play? Which bands are played most? Which DJs play 70s music? Radio Waves is a prototype visualisation that takes data about music played recently on BBC Radio and creates a time profile for any individual radio network, musical genre or radio show. The graph shows, year by year, how many albums were released by the artists recently played on BBC Radio. Click here to explore the visualisation or read on to find out more. After our recent hackday on music visualisation we ran a quick two week sprint with the R&D Prototyping team to develop a combination of the best and the most feasible of the ideas that came out. Radio Waves is the result of that sprint. What it doesInitially the visualisation represents all four of the BBC radio stations we are using; BBC Radio 1, BBC Radio 2, BBC 1Xtra and BBC 6 Music. The graph represents how many albums were released by the bands and artists recently played by shows on that network - so if it has a peak in the 1950s then that network has played artists who were active in the 50s. The visualisation can then be filtered to show the graphs for a particular radio network, a genre or show.
Individual years within the graph can be selected to show a list of artists who released albums in that year and have been most played by the selected radio network or show. Clicking on an artist will show more detail about them and reveal the complete list of albums they released and when. How it worksWe start by collating the data for what music BBC Radio has played over the last few months - from tracklistings like this. Note that this prototype is only using a static data set for now. From this we can link to /music data about these artists, and from there to releases from each artist. From the complete list of releases we try to only use albums, not compilations, EPs or singles, as we believe that albums sufficiently represent an artist’s historical profile (this is arguable). We can then take the release dates of all these albums, and the number of times each artist has been played on that radio network or show, to draw the graph. In total we're using about 300 shows, each with a play count and top artists for every year and a list of about 9000 featured artists. We have to tidy up the data a bit; not all tracks played have MusicBrainz IDs attached, we have to remove duplicate releases (there are lots of “disc 1” and “disc 2” in the MusicBrainz data) and we also remove any albums from “Various Artists” because that's not particularly helpful for our purposes. And we've left out Radio 3, Asian Network and the regional services because we don’t have that much play data from them at the moment. Radio 3 in particular would be difficult because the "releases" they play don’t represent a composer’s active career in the same way as releases for pop and rock bands do. It’s a prototypeRadio Waves was built so we could explore the possibilities of visualising our music data and we deliberately constrained ourselves to only use data that we have available right now. We think it has one major but surmountable problem. Our current architecture and data mean we can only go from a show » songs » artists » albums » release dates. So this doesn’t actually represent the release dates of the music that is played on the radio, rather it represents the careers of the artists whose music is played and that’s not completely intuitive. Ideally we would go directly from show » songs » release dates, and at some point, with the help of the MusicBrainz next-generation schema and some dedicated volunteers, we should get this data.
As an end note, we probably also need to tidy up which album releases we use. If you look at the graph for Elvis you can see his original career (he reportedly died in 1977) and then a resurgence in popularity (and therefore re-releases, sessions, best-ofs…) in the last decade. So maybe we should limit the data to releases within the artist’s (or bands) lifetime. If you liked the feature from Picasa Web Albums that detects the faces in your photos and clusters them, it's now available in Picasa 3.5. Face recognition works locally, without sending data to Google's servers. For some reason, the feature is enabled by default and it starts to process your photos right after installing the software. It's pretty slow and the accuracy is far from perfect: you might see multiple clusters for the same person and different people addded to the same cluster. ![]() ![]() If you sign in using a Google account, you can choose people from your contacts when you're asked to add names for each group of photos. There's also the option to download the name tags from Picasa Web Albums if some of your photos are stored online. "As with Picasa Web Albums, your reward for trudging through your photos to add tags is better organization, which for a massive library of old, archived shots can be hugely helpful," thinks Josh Lowensohn, from CNet. Another new feature in Picasa 3.5 is geotagging using Google Maps. Until now, you had to install Google Earth to add locations to your photos. The latest version of Picasa has a "places" sidebar that lets you drag photos to a map. Three years ago, when Google acquired Neven Vision, a blog post mentioned the goal of the acquisition: improving the way you organize photos in Picasa. "It's not always easy to search through your personal photos, and it's certainly a lot harder than searching the web. Unless you take the time to label and organize all your pictures (and I'll freely admit that I don't), chances are it can be pretty hard to find that photo you just know is hidden somewhere deep inside your computer. We've been working to make Picasa (Google's free photo-organizing software) even better when it comes to searching for your own photos — to make finding them be as easy as finding stuff on the web. Luckily we've found some people who share this goal, and are excited that the Neven Vision team is now part of Google." Update: For now, this is an English-only release, so it's not available if you set a different language for the Picasa page. Here are the direct download links for Picasa 3.5: Windows: http://dl.google.com/picasa/picasa35-setup.exe Mac: http://dl.google.com/photos/picasamac35.dmg A company has discovered that transferring data via pigeon is much quicker than doing so by broadband Mozilla aims to improve Firefox security and stability by reminding users to upgrade Adobe plugins Oooh, it's be a busy radio morning, hasn't it? We've got Mr Moyles celebrating becoming the longest serving Radio 1 Breakfast DJ and Sir Tel announcing (after a little Daily Mail intervention) that he's abandoning his TOGs for a weekend show and letting that young whipper-snapper Chris Evans have another BBC breakfast show. I don't think there's any particular surprise in the Radio 2 announcements – they've replaced a hugely successful presenter with the next most sucessful presenter on the network. Though, as Adam points out, there is a bit of a demographic issue. What it doesn't do is help the arguments about Radio 2 moving younger in the commercial heartland. However, and I think we all know this, they really couldn't care less and so carry on regardless. However, what I think this does do, is open up the opportunity to make a stab at turning drive into something a bit more public service-y. Already Drive with Chris has business and sports elements to make it more than pop and prattle, but with a likely move of Mayo to 2 from 5 there's a real opportunity to make it even more striking. Though his heritage proves that Simon can do mainsteam pop really well it would be great to see him bring things like his book reviews and more in-depth interviews (along with the Good Doctor) to a new drivetime show. Radio 2 already does this marvellously at lunchtime, it would be in keeping with Tim Davie's recent announcement if they made their new drive show even more distinctive. Meetings run over all the time. In fact, you might say that that's their natural state. Meetings think gases are lazy. Whereas a gas expands to fill its container, a meeting expands to exceed the size of its container. It requires good management skills to keep all your meetings on schedule. And it takes great management skills to get them all to finish early. Even someone with poor management skills sometimes valt met je gat in de boter and a meeting will finish early by some fluke. And unfortunately, I've been at meetings where the meeting organizer decides that this is not an acceptable state of affairs. "Okay, it looks like we still have ten minutes, so Bob, why don't you tell us about Topic X," where Topic X might be "how your part of the project is doing" or "the meeting you had with Team Y." Whatever it is, it's something that wasn't on the meeting agenda. It's just there to fill time. Of course, it takes Bob fifteen minutes to talk about Topic X, because a meeting expands to exceed the size of its container. What started out as a meeting that came in early turned into yet another boring meeting that ran over. There's no law that says a meeting can't end early. If you're finished early, then finish early. |