Category: Development

Education and Support are Golden

“In this case, our approach worked, and the client’s cumbersome media management time was significantly reduced. The difference between the outcome of the two projects was simply education and support.

…

We should be teaching our clients to use their website, app, content management system, or social media correctly and wisely. The more adept they are at putting our products to use, the better our products perform.”

90% of my day job is education and support. 100% of any glimmer of success I’ve ever had is in properly aligning capabilities in what is being developed and expectations on how that will be used. Things are often built with all sorts of bells-and-whistles – that never get used. Why? Because no one took the time to set expectations, educate, and support the customer. Drew Thomas knows what he’s talking about here folks.

 

 

Clients are not Your Friend and That’s OK

“The first time I presented design to a client I absolutely choked. I put the work in front of them and stood there like an idiot. It was humiliating. The next time was a little easier. And the time after that, well, you get the idea. I have done every one of the things on this list. I’m sharing them with you in the hopes that they’ll spare you a humiliating experience or two. It’ll take time.”

Mike Monterio (again) shares some practical wisdom for anyone who works with clients. You can design the most amazing thing, but if you can’t present it’s no good. I cringed reading this, knowing I too have made some of these mistakes.

Louie Mantia on Making Opinionated Software

“Making software isn’t easy. You have to make a lot of decisions and have good strong reasoning for doing so. A lot of the decisions I make are with my gut, and revolve around my personal taste. But there’s another way to design things, and that’s “safely.”

It’s not easy either, but designing safely means designing for everyone (80%+ of the population). Often, designing safely means making decisions that don’t make you happy personally. You include a feature so that someone else will like it.”

I think Louie should take it one step further. Write Opinionated Software. Don’t write mushy middle-of-the-road swiss army knife software. Write something with a voice.

Smart Albums for iPad Air Screenshots

A few years ago I wrote this tip on creating Smart Albums for your iPhone or iPad screenshots. I’m a big screenshot taker. I use them for keeping track of UI problems with projects I’m working on and even as a quick “note” to look into something later.

The problem is sorting the screenshots out from the rest of my 80 billion photos in my library. I use Aperture (yes, me and two other people) and created this Smart Album to sort out my screenshots from my iPad Air. You can probably adopt the logic for other devices as well.

Screen Shot 2014-08-22 at 4.04.59 PM

Basically it looks for files that match all of the following:

  • Text starts with “IMG_” – standard filename prefix for iOS device screenshots.
  • Pixel height and width is between 1,536 and 2,048 – this allows for both portrait and landscape screenshots to be returned
  • Camera Model is empty – pretty much all of my other images are photos from cameras that record their model. iOS devices do not store a value for “Camera Model” in their EXIF data.
  • File Type is other – no RAW or jpegs showing up here!

If you have suggestions or modifications, please let me know in the comments below.

Cognitive Biases in Software Engineering

“This is one of the harder biases to get over in my opinion, because it means acknowledging our own limitations, and really stressing the fragile parts of the code that we write. We all want and expect our software to work, so we are inescapably drawn to evidence that confirms this desire. Keep fighting this urge, keep testing, and always question your assumptions.”

Jonathan Klein on how our brains deceive us when encountering issues in software development.