PL
DevConE #5 — comfort at work, Atypical meet-up.

DevConE is our standing conversation about teamwork, technology, and the environment in which those decisions get made. At edition #5 the headline theme was comfort at work — understood broadly: body, attention, the rhythm of the day, and the quality of how we talk to one another.

Why “comfort” belongs in a serious engineering and business discussion

Comfort is not a fluffy line item on the roadmap. A worn-out body and a splintered mind shorten your planning horizon, inflate error rates, and cost you every bit as much as a tool outage — only the invoice is harder to spot in a dashboard.

We circled back to a handful of questions worth asking before any major change lands:

  • Can this decision actually be executed at the team’s current load, or only on paper?
  • Where in the week does information noise pile up (notifications, channels, meetings with no clear decision owner)?
  • What in the physical setup — desk, lighting, acoustics, hardware — feeds straight into the quality of meetings and code?

Three threads that stuck after #5

Ergonomics and movement. Marathon sessions in one chair-and-monitor configuration are not “a minor HR detail”. Small course corrections (posture, breaks, movement) often cost less than a single wasted hour of debugging when you are already running on fumes.

Boundaries around attention. Continuous partial attention — constantly context-switching — is great for your calendar and lethal for work that needs a single thread of thought. In practice: carve deep-work windows, fewer “urgent” channels, and define what “urgent” actually means.

Team cadence, not calendar cadence. If the plan assumes people are always running at full utilisation, the plan was risky from day one. Comfort also means a realistic buffer — for learning, for the awkward first weeks of a new tool, for life happening.

What is next

DevConE will be back with another theme — follow our channels or drop us a line about what strains comfort most in your team (technical or organisational); often naming the friction in plain language is already half the battle.

Our methodology Write to us

Book a conversation

Fill in a few details — we will send your request and a confirmation to your inbox. We will reply within one business day.

Step 1 of 2 — topic

What is this conversation about?

Programme inquiry

Choose how you’re contacting us, then add email and phone. For a company, include the name. We’ll follow up about the programme you picked from the catalogue.

Required — min. 9 digits (including country part).