Working on a voice app? Check out Dave Rupert’s Anthology of Mute Buttons in Voice Chat Apps and get an excellent overview of all the confusing ways the mute function is presented. Mute has existed for a long time, we all use it, but it is so hard to get right.
He really is on to something with the push to talk idea. That should really be the default for conference calls and group chats.
I was going to use one of the popular frameworks for a very little project when three things conspired to put me on a different path. One was a problem of my own doing: I seemed to have hosed my NPM installation whilst trying to upgrade something. Then I read these two posts, which really came at the right time:
I have a suspicion that there’s a silent majority of developers who are working with “boring” technologies on “boring” products in “boring” industries …you know, healthcare, government, education, and other facets of everyday life that any other industry would value more highly than Uber for dogs.
Anyway, I got an initial version of my tiny project done in a couple hours. I’d still be fighting with the framework if I had continued in the original direction. I’m sure I’ll get my NPM fixed, and I’m sure I’ll use a framework in the future, but I’m glad I gave myself permission to just hack this thing out in very, very basic HTML, CSS and a few lines of JS.
In this video, Martin Fowler sums up my experience with agile throughout the years. In my experience, it ends up being tiny waterfalls that everyone calls sprints. The only reason upper management is willing to give it a go is because when they hear “sprint” think “go fast”.
Of course, it doesn’t have to be that way, and Fowler touches on some reasons to be optimistic about agile towards the end of his talk.
Nielsen Norman Group’s Top 10 Application-Design Mistakes is a good reminder of common pitfalls when creating complex applications. This is recommended reading for everyone (not just designers) working on these sorts of applications. As they point out, it’s challenging to get this right.
A couple weeks ago, I downloaded all of my Flickr data. At the time, I wasn’t sure what I’d do with all of it. Today, I uploaded everything to this WordPress site with the help of some Python scripts I created. The scripts are available on Github, if that’s your sort of thing: flickr-wp-upload.
I won’t go into the details here, but I will leave you with my final thought from my worklog on the project:
My justification: 2,001 photos were uploaded (with meta data), 31 albums were created and 150 comments ported over. At a conservative 3 minutes per manual upload, it would have taken about 12.5 working days for me to upload this stuff. Let alone assembling the albums, and the comments would have been lost. Plus, I learned a few things along the way (e.g. how to rotate images with Python).