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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...