Skip to main content

Open Office trend: my opinion

Reading Jef Claes post on The open plan fallacy inspired me to share my opinion too. (Go read Jef’s post before you continue reading).
I don’t know how it is at other places in the world, but here in Belgium, the ‘Open Office’ idea is really popular. The idea is that everyone is sharing the same workspace. In the morning, you enter the building, take your first cup of coffee and go sit where ever you want. Everyone is sitting in the same open office. In the evening you remove everything from your desk, put your stuff inside a locker and the next day it start’s all over again. (And if you don’t like the person sitting next to you, the next day you can go and sit somewhere else).

As Jef mentions in his post the open office layout certainly has some advantages. It stimulates communication, creates more networking opportunities, optimize the usage of the available space and reduce costs. 

I have to agree with all those advantages (it’s always fun to chat with a colleague you have not seen for a while), but this comes with one cost: productivity. In my experience I have seen that teams get most effective when they have their own space, isolated from any distractions. Teams should be able to communicate freely, share ideas, do code reviews and have some fun. But in an open office layout this is hard to do without disturbing others.

I’m not advocating to introduce cubicles and all work in our isolated space but instead to create a mix of team rooms and open spaces. I do think this will increase productivity a lot…

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...