97 Things Every Programmer Should Know

(Chris Devlin) #1

Collective Wisdom from the Experts 195


with them. Talk to them about the things that happen just before or just after
the topic you’re talking about to get better context. If at all possible, have mul-
tiple people tell you about the same topic in separate conversations. They will
almost always tell you different stories, which will uncover separate yet related
facts. Two people telling you about the same topic will often contradict each
other. Your best chance for success is to hash out the differences before you
start your ultra-complex software crafting.


Use visual aids in your conversations. This could be as simple as using a white-
board in a meeting, as easy as creating a visual mockup early in the design
phase, or as complex as crafting a functional prototype. It is generally known
that using visual aids during a conversation helps lengthen our attention span
and increases the retention rate of the information. Take advantage of this fact
and set your project up for success.


In a past life, I was a “multimedia programmer” on a team that produced glitzy
projects. A client of ours described her thoughts on the look and feel of the
project in great detail. The general color scheme discussed in the design meet-
ings indicated a black background for the presentation. We thought we had it
nailed. Teams of graphic designers began churning out hundreds of layered
graphics files. Loads of time was spent molding the end product. On the day
we showed the client the fruits of our labor, we got some startling news. When
she saw the product, her exact words about the background color were, “When
I said black, I meant white.” So, you see, it is never as clear as black and white.

Free download pdf