Friday at Noon

The first thing that stayed with me was not the software. It was the workday.

In the Montreal office I visited, time seemed less connected to the idea of proving commitment by sitting at a desk for as long as possible. I recorded a minimum number of hours per day and week, and I remember being struck by the idea that after enough hours had been completed, people could sometimes leave around noon on Friday.

There were games too: foosball, darts, billiards. People could play them, and the time did not magically become “work.” That detail amused me because it made the arrangement feel honest. Leisure did not need to be renamed as corporate culture before it was allowed to exist.

The company itself also changed one of my early assumptions about software. I had imagined software companies mainly as buildings full of programmers. Instead, I saw how much work surrounded development: testing, quality, marketing, training, support, and everything needed to move a product from code to customer.

Small details made the office feel human. Notes appeared on private office doors explaining where someone had gone: out for the day, elsewhere in the building, away for a short reason. A piece of paper often did the job well enough.

I also noticed things I liked less. Pay did not seem especially impressive to me, and I was skeptical about some promises made around product support. The office was not a perfect model; it was simply different enough to make comparison unavoidable.

That was the useful part.

Before seeing another workplace, the rules of your own environment can feel natural. Then another office shows you that hours, hierarchy, breaks, and even the relationship between work and ordinary life are designed choices.

After that, your old rules can no longer pretend they are the only ones.