What would you do if you ended up with 4-5 times the number of bananas you expected?

Smoothies for days? Gift banana bread to friends?

My friend Amit is a developer. He knows the importance of the commands he sends to a machine.

And yet…

Amit opened up an app on his phone and “went shopping” for groceries.

Among his order, he requested six bananas.

Delivered groceries can be more expensive, so perhaps the price didn’t catch his eye…

Instead of six individual bananas, Amit received six bundles of bananas.

An error like this in his code might have been caught with tests. In the physical world, 27 bananas arrived at his door.

Word choices and other small decisions can impact your developer experience, too.

Often, you can make a big difference with minimal updates to documentation:

• A reframe around languages and frameworks
• A guided first-time experience
• Both functional and contextual docs

​
You may still send too many bananas on occasion, but at least you can catch the most common documentation mistakes.

Of course, some are a matter of perspective.

Neither Amit nor the grocery app was “wrong” in their interpretation of “six bananas.”

Sometimes we get blinded by our own experience and it becomes impossible to see things any other way.

​For a fresh-eyed view of your developer experience, reach out to our team.