Hamstaa!

We recently had two new businesses move into the offices next door. Looking through the doors highlighted to me how important the first impression of an office is to the energy you bring when you walk in the door.

One of the offices is very evidently a call-center. It’s clad in shades of grey and blue with small cubicles. It seems to suck the energy out of you just looking at it.

The other (pictured) seems to draw you in. In fact, upon entering, I had not idea what they did¹, but you felt that it would be an interesting place to work.

It may seem obvious, but it’s important to consider the impact your office environment has on potential employee’s as well as the current ones.

When recruiting, if a candidate walks in the door thinking, “wow, I want to work here”, or compares favorably your office/team with their current office and team part of the hiring process just got simpler.

For your own staff, having a place that they want to work in, along with an outstanding team to work with brings it’s own rewards. Higher productivity, less down-time due to illness and greater retention to name just a few. These rewards have value not easily measured but a lot higher than what it can cost to make a great environment.

1 – My wife’s first guess from the photo was travel, but it turns out they are a tattoo artist.↩

Ephox is 10 years old and to celebrate we flew everyone in from our US and UK offices to where it all began … Brisbane.

The celebrations kicked off with a party on Thursday followed by a weekend away at the Hyatt Coolum for employee’s and their partners.

While the weekend away did provide an opportunity to talk shop, it was the personal conversations that I feel pay the biggest dividend.

At Ephox we make great use of digital communication tools like Skype, e-mail and instant messenger to keep in touch. There is something however about talking to someone face-to-face, that allows you to connect on a different level. It’s the conversations over breakfast, the corporate dinner, pre-dinner drinks and while playing tourist that allow you to connect with our colleagues in a way that electronic means just can’t achieve.

In this relaxed environment, you find yourself talking about previous experiences and roles as well as sharing a joke or two. Add to that the ability to meet and talk with your colleagues partner and you begin to build a more complete picture of the person.

So what does this mean for us now we are all back home? The personal connections made enhance our business relationships and communication. The insight gained allows us to filter digital communications through their respective personalities, enriching the experience. In addition, the “back-story” of each person will allow us to better utilise their previous experiences/skills.

One of the driving forces of “Clean Code” is that while it takes a certain amount of time to write code, that same code is read many times. Clean Code is aimed at reducing the reading and hence understanding time of the code.

We recently had a practical session, as part of our continuous learning practice, on TDD. After the first few tests, Doug got into some serious refactoring to make the code clean. As Doug progressed, I found myself becoming increasingly frustrated with the numerous methods, many of which had 1 or 2 lines of code, that he created.

I started trying to understand what Doug was trying to achieve and why I was finding it frustrating. As we discussed the aim of Clean Code and how Doug would “read” the code, it dawned on me that the difference was in detail. Doug would read the initial method, accept the definition inherit in the method names called, and drill down to those lower methods only when required. I on the other hand found I needed to drill down through the many layers of methods to better understand the initial method.

It was this difference to how we went about understanding a program that was making his extreme Clean Code approach work for Doug and not for me.

In previous lives both Doug and I have done a Myers-Briggs assessment and interestingly he is an N while I’m an S. In the Myers Briggs assessment, the Intuitive (N) preference person works from the “Big Picture” drilling down to detail when required, while the Sensing (S) personality is the opposite.

When I did my Myers-Briggs assessment we discussed the need, when presenting to a room of people, to take into account the various understanding approaches inherit in the S and N preferences. Similarly, when you are teaching, my wife informs me, you need to take into account the learning styles people have. For example Auditory versus Kinesthetic.

So, when you are “cleaning” code, take into consideration that the people reading it in the future, may not approach it the same way you do. You need to strike a balance between cleaning up the code into more manageable methods, but not to the point where you have many layers of increasingly smaller methods. Not everyone will save time reading this code, but rather it will take them significantly longer.

Andy recently pointed me at an interesting article, “The Paper Version of the Web” that shows some great examples of UI designs sketched on paper. In the article Sean collects together some of the publicly available UI sketches for well known websites like Flickr and Twitter.

At Ephox, we have quite a lot of UI design required and as such we’ve tried a few different things from quick Java mock-ups to Photoshopped images. To me however the best solution is the paper sketch. Why, well other than it being pretty cheap to develop and modify, anyone can do it, including the “client”. Finally, there’s also no chance you will be tempted to use the “prototype/mockup” as the basis for the final version.