Wednesday, February 11, 2009

Monitoring a web application

So we got a reliable web hosting service for Teamness and we came up with a security policy to keep the data safe.

All good, but we also needed a monitoring solution, to be informed when something is wrong with the server.

We settled to use Pingdom, a Swedish service built for this purpose. Big guys like Alexa, iStockPhoto, Feedburner and Skype are using Pingdom, but it's also an affordable solution for small startups like us.

This post is not a Pingdom review, but more about the way we're using their services to know that Teamness is up and running.

Our Pingdom account

We set up 3 monitoring options for Teamness, for every web application in Teamness:
For each of the above, there is a check done every minute. If 2 consecutive checks fail, each of us gets an email and an SMS. We're not all the time in front of the computer, but we carry our mobile phones everywhere, so we know in an instant if something is wrong.

There is also the option to pause a checking routine, so the notifications are off while we're doing maintenance work, like uploading a new build.

What do we check for?

We built a special tiny module in Teamness, which performs a couple of sanity checks to be sure the application is running safe. This module is called from a separate page, designed specifically for this purpose, which is further requested in the Pingdom checking routine.

This way we don't only know that the server machine is up and that the web server is running, but also that the inner workings of the application are sane.

Current status pages

You may expose the status of your web application through a public link. We used TinyUrl to generate these custom links for the two websites in Teamness:
They are very useful when our users ask for the uptime. A link to a nice page with the historic of the availability is more valuable than stories and explanations.

The link for the private website, which is the website with your data, is published on the Teamness main page.

Pingdom goodies

They have a set of tools for checking a webpage, by mimicking the way it is loaded in a web browser and also for doing traceroutes or pings.

Tests may be saved for future reference, like this one for The New York Times.

Mr Uptime is a Firefox extension that will let you know when a website you checked and wasn't available is again back in business.

Royal Pingdom is the name they chose for their blog. I like the Swedish humor. And I like the blog, is one of the corporate blogs that issue quality posts and not only blabber about some new offers.

Monday, February 9, 2009

Reclaim your life

I found Idiocracy to be funny in a ironical way, as it was probably intended. At least the first half, since afterward it turns into the usual cheesy Hollywood thing.

This post on Zen Habits reminded me about Idiocracy.

I follow Zen Habits in Google Reader and I like Leo Babauta's honest and smooth writing style. I also enjoyed his free ebook, Thriving on Less - Simplifying in a Tough Economy.

But I don't get posts like the one mentioned above.

It's a guest post with 30 ideas "for high-quality, low-cost, stress-free family fun". So not the stressful kind of fun.

I understand that more and more people are spending their time staring at stuff in the computer screen and sometimes they neglect their families and friends, but who actually needs a list of things to do with their family? Is lack of ideas the issue?

I was looking through the comments to see if there is an answer like: "Oh, wait a minute number 6 is brilliant. I never thought of talking to my family ... yeah, definitely something to go in my task list for the weekend."

No success, but we're close. People are thanking for having a 30 days roadmap with their family.

I'm waiting to see the first part of Idiocracy 2. The second part is probably predictable.

Thursday, February 5, 2009

New member's pocket guide to a virtual team

Two weeks ago, Sorin wrote a juicy post about welcoming a new member in a virtual team. There were a couple of times in the past when I was wearing the shoes of a newcomer in a virtual team and throughout time I learned from mistakes and developed some guidelines to keep me comfortable.

Image by 96dpi


Centralize data
I made a habit of keeping data centralized in a single location. It feels comfortable to know that you have a single place from where to start looking for your stuff. Every document, meeting minutes and conclusions from discussion on email or IM, things that I need to do for the projects and so on were stored in the central place. This doesn't eliminate the need to sometimes look for an old email, but at least it diminishes it.

Keep a worklog
At one point in the past I started to track my daily activity, by writing down as much as I considered relevant. Besides the things that I've been working on, the list also includes mentions of Skype or phone conversations with my colleagues. If you get paid by the hour, this is probably mandatory, but even if you don't, it pays off in time.

Stick to a strict working schedule

When I started working from home, it seemed cool to me to have a loose schedule. More like no schedule at all. But after a while I noticed that I actually didn't know when to stand up from the desk and call the day off. This started to affect my health and my ability to focus.

And there is another side effect of the schedule-free work style: your friends will consider you're always available and ask your help with different chores. If you don't commit to a time schedule, you'll end up doing other things when you should be focusing on work and you'll find yourself pushing working hours late into the night.

Schedule and timezones
Since the team is distributed geographically, the members could be on different timezones and it's good to know who is available and when. Worldclock and FoxClocks are two useful tools to see the current time of your colleagues.

Image by monkeyc.net


I used to convey upfront the time interval when I was going to be available. Even if I wasn't working in an office I still needed lunch breaks, so this was also included in the schedule.

Communicate often to keep yourself on track
Have a chat on IM each morning with the whole team, if possible, or only with your coordinator to say what you were working on, what do you intend to do that day and also ask what others are working on. Keep it short and concise!

Asynchronous interaction is your friend
Your colleagues are not in the office near you. Take advantage of this. You cannot be interrupted from your work flow and I suppose you don't want to. Rely heavily on email, collaboration tools, wikis and other non-interruptive mediums.

Invest in your workspace
If you're working from home and you just started your virtual work adventure, it's probably better to create a proper environment. Separating home from office is an advisable thing to do, even when the office is at home. So make it look like a nice office rather than a cozy place at home.

The Home Office Planner is a dainty book that comes to your help in transforming any space into a functional work area. You may also use IKEA 2008 Office planner, a desktop application for designing your office in a 3D view. The software let's you try various colors and also see the total cost.

Monday, February 2, 2009

Avoid the maintenance nightmare of duplications

In software development, duplicate code is considered a sacrilege. It leads to maintenance issues of the system, requiring more work to fix the same problem in a couple of places.

So then, it's pretty easy: just don't duplicate the code, right? It's basically as easy as saying don't eat bad food. Some people have the discipline to stick to healthy nutrients to an extent to which they find junk food disgusting, but the rest of use enjoy a juicy burger once in a while.

Image by Sam UL

As noted by Dave Thomas, one of the two authors of The Pragmatic Programmer:
If you have more than one way to express the same thing, at some point the two or three different representations will most likely fall out of step with each other.
To keep these representations up to date and therefore synchronized with each other, you'll find yourself stuck in the wasteful process of changing them in parallel, which I call the maintenance nightmare. And the nightmare reaches its climax when contradiction makes its way in.

The duplication plague extends beyond code. It reaches areas such as requirements or specifications as well.

It happened to me a couple of times to be directed to obsolete documents, when I started in a new team. These documents usually become obsolete because a colleague sends an email with a few notes, which become new requests upon subsequent replies.

Later on, someone else puts together a Word document that summarizes what has been discussed, which will probably get to be obsolete in a couple of weeks.

A solution that I found working was to establish a procedure of maintaining specifications and, more importantly, to stick to it. This may sound overblown, but it doesn't need to be: a simple guidance, presented as text is usually enough and also newcomers will benefit from it.

When a new email comes in with notes on how a process or a feature must be changed, make sure to update the single location where it was described so far and point everyone to it. Referencing that location in future discussions will habituate your co-workers into using the procedure you established together, eliminating the confusion induced by obsolete docs.

Friday, January 30, 2009

Eliminate assignment confusions

So you finished brainstorming over an idea and now it's time to get your hands dirty and do the work.

This moment is critical. A task doesn't necessarily mean the same thing for two different persons. Your idea about how to write the new contract may differ from John's, so if the task is not detailed enough, it might lead to the team pulling in different directions.

Image by Sean Rogers1


A solid approach would be to dissect the task down to manageable sub-tasks, that don't allow different interpretations.

Let's say you have to Promote the website for your business. It's a pretty complex task that can be interpreted in many ways.

But if you slice it into more manageable things to do, the bewilderment fades away:
  • Find 10 website directories and enter the website under the proper categories.
  • Write a press release which includes the 5 most useful services the company provides.
  • Submit the press release to 5 online agencies.
  • Write an whitepaper about a solution your company/product is offering.
  • Set up a Google AdWords account and start a campaign.
Besides clarifying the work to be done, other benefits of breaking down a complex task include:
  • You get a better estimation of the duration of the task.
  • The progress gets easier to follow. In my opinion, this approach is more useful than using flimsy percentages which usually get out of control.
  • You have a list of actionable things to do, instead of a complex unclear assignment.

Wednesday, January 28, 2009

5 tips and tricks with Teamness

1. The startup project

If you're working on a few projects at a time, but one of them is the one that takes most of your time, you may choose one of your projects to be the startup project.

This means that each time you enter into your account, the current selected project from the projects list will be the active one. You can set the Startup project in the My details page.

2. Login through Google, Yahoo or both

You don't need to create a new account to be able to use Teamness. Just login with your Google or Yahoo account and you're all set. And if you already have an account created in Teamness, you may associate it with both your Google and Yahoo accounts and login with whichever you prefer.

3. Task titles

You may turn on and off the detailed list view of the Tasks page. When the detailed list view is disabled, only the first line of text from each task is displayed, like a title. This is especially useful when the tasks are quite verbosely described and you want to get an easier overview.



4. Print your project pages

You can print the information from each page with data from your projects, by using the print button available in the upper right corner of the page. For instance, this is how the View milestone page looks like:



5. Browser search bar for Teamness projects

Installing the search plugin allows easy searching your projects' data in Teamness directly from the browser search bar.

Monday, January 26, 2009

Brainstorming remotely

Today I started a short conversation with Pawel Brodzinski, about how teams respond to working exclusively remote. By the way, his blog, called Software Project Management, is a great resource of posts about working with teams and managing the process of software development, so make sure you subscribe to it.

Pawel was talking about the lessons learned from a startup product called Overto, which was closed some time ago. One of the things he mentioned was the value of working in the same place and the way his team started to feel the negative effects of being separated.

Image by timabbott


Since I believe in the remote proficiency of virtual teams, I had a different opinion. I think that after the preliminary discussions around the fresh idea of the product, collaborating in writing instead of ad-hoc meetings may bring great effectiveness into the product.

Written communication versus spoken brainstorming

I mentioned the following arguments for communicating over writing mediums, like email, as opposed to verbal meetings:
  • On email it's more natural to keep the discussion focused on an aspect. Talking makes this a bit chaotic.
  • It's easier to follow a point of view, when you have it written on the screen, maybe with additional links to external resources.
  • When you need to write, you focus more on the points you'd like to add to the discussion. Talking is faster, so it might lead to loosing the focus.
  • Everything that's discussed gets logged, so you avoid the post-meeting confusion over some pieces of conversation or forgotten parts.
  • You're undisturbed in your own mind-mapping flow process and you don't disturb the others.
Brainstorming over emails might be a bit sluggish from the point of view of generating ideas based on ideas being generated by the others, but in my opinion it's better in refining an idea before exposing it.

Let ideas flow, then examine the results

It's pretty common that once an idea is out, it's exposed to being examined. This leads to context switching and instead of focusing on building a list of things to discuss about, you'll find yourself analyzing ideas.

For instance, when you discuss holiday destinations with your spouse, it's probably the case that you find a place, discuss about it, then find another, comment on it and so on.

The drawbacks of this approach are presented more explicitly in the book The Myth of Multitasking. The book includes a demonstration that switching back and forth between two different tasks, makes them take more time than doing them sequentially.

Image by h.koppdelaney

The above example is a bit extreme, since it involves the spouse. Don't do it at home unsupervised. But in my opinion, the same thing applies to teams and brainstorming. It's nothing wrong with getting together for a drink/lunch and discuss about a new product or feature, but I find writing more efficient.

Use mind-mapping, build a list of things that you think are suited, and then pass it on. If the others are doing the same, undisturbed, your team ends up with a more productive flow of ideas and better yet, you have everything written down.

Experiment and stick to what works for you

I'm not trying to say that this model is supposed to work for everyone. We are a team of two people, me and Sorin. It's been like this not only for the time we've been working on Teamness, but since 2005 when we started our company. We used to work from home on different projects for some clients and we always collaborated remotely. This is basically the reason for building Teamness in the first place.

In the beginning we were talking on Skype about clients, implementation details, decisions and so on. We used to have long conversations and sometimes we didn't remember everything that was discussed. We still have conversations, but when we talk about new features or design decisions, we use Teamness. We write the proposal in a message and then comment on it. This keeps it focused. We also use email from time to time, but what I want to stress upon here is that we're trying to keep the verbal communication related to our projects to a minimum, since it didn't prove efficient for us.

Please also note that I'm not trying to express that social interaction is bad, like having lunch with your colleagues or coffee breaks discussions. But when your product has 1000 features, writing things down becomes the key ingredient for a solid collaboration.