When it comes to working as a business analyst, I’ve learned that there are just three things you need to keep in your mind when meeting with your customers (the project sponsor (gold owner) and domain experts (“goal donors”)) to gather requirements. These three thoughts will keep your meeting on track, lead you to the next question, and will help you know when your work is done.
Twitter UI redesign: After using Twitter for the last several months, it seems like their user interface is out of sync with how I want to use their data. As I was waiting for dinner to cook last night I spent a few minutes thinking about the Twitter user interface (UI) and how I might redesign it. Here are my thoughts.
The current Twitter web interface
The things the Twitter web interface does well currently are:
I’ve been thinking about getting a new tablet recently, and after looking at the Nexus 9 yesterday, I have to say that I like Google’s latest UI design. Android 5 looks good, and this image from Google+ is also pleasant enough to look at.
Every time I go back to writing GUI programs, I find that I want to document my UI layout code, especially when I use something like a JGoodies layout in a Java/Swing application. I just took a look around and found some ASCII drawing programs, which may help me create the documentation I’m looking for, i.e., an ASCII drawing I can put in my Java/Scala comments, above my UI layout code. I created this particular drawing with asciiflow.com.
Sorry folks, I hoped to be able to release the source code I created for a Nagios Web Interface, but after starting on it a few hours ago, I'm giving up on this project. The code works just fine, as you can see from the screenshots below.
The problem is the amount of work it will take to make this code "clean" for public release. It currently has my client name all over it, and removing all those references is just going to take too long. (Unless of course an angel investor wants to contribute a few week's pay into my PayPal account.)
I'm not sure how much call there is for a simplified Nagios web interface (user interface), but I wrote one last year, and I'll be releasing it here soon, after many comments on my Nagios MySQL database design article, along with many, many personal emails.
The grand experiment has begun. The problem: I've been on a project developing a very deep application for four years now, and lately it's become so complex and intertwined that things are starting to break. Developers have been known to say "The application is smarter than I am." I'm just a wee bit concerned about our software quality.
Throughout all of this I started to notice that many of these bugs could be found if we had ... (drumroll) ... automated GUI tests.