Whenever I talk to other developers these days, the conversation eventually lands on the same topic: AI. What does it mean for our craft? Is it a threat? Is it a superpower? Are we becoming less relevant, or more?

I don't think the role of a developer has changed as fundamentally as people fear. But I do think AI has made something very visible that was always true — something most developers quietly knew, but rarely talked about.

Let me explain.

Let's be honest: code generation has never been the bottleneck in good software engineering.

Even five years ago — before AI could write a React component from a comment — the best engineers on any team weren't valued because they typed fast or wrote the most lines of code. Nobody worth their salt was measuring engineering quality in LOC. We all knew that.

The real bottleneck has always been shipping — getting real results into the real world. Delivering on time. Delivering what's actually needed. Knowing the difference between those two, and navigating the gap.

That's the skill. The ultimate engineering skill. It's harder to track than code output. You can't see a PR for it. There's no metric. But every senior engineer has lived through projects where someone got it done — not because they were the fastest coder, but because they held the whole picture in their head, asked the right questions, navigated blockers, and kept moving.

That's what I mean by "shipping skills." That's what I mean by "getting real results."

Every day, every developer faces a stream of small opportunities: a refinement session, a ticket description, a stakeholder conversation, a design review, a Slack thread going sideways. Each of these is a chance to either move things forward — or miss it.

Missing opportunities is easy. You didn't prepare enough. You didn't listen closely enough. You didn't ask the clarifying question. You didn't speak up when something felt wrong.

And the thing about missed opportunities is that they're invisible. Nobody counts them. There's no retrospective item for "the feature that took six months instead of two because we didn't nail down the requirements." There's no post-mortem for "the technically correct solution that didn't solve the customer's actual need."

But those missed opportunities are exactly what it costs a team — and a company — dearly. They are rare chances wasted.

Not missing them. Recognizing them in the wild and acting on them. That's what seniority actually looks like. That's what experience earns you.

One of the most important things a developer can do is understand their environment:

• the tech stack
• the data
• the company
• the stakeholders
• the market
• the big picture
• the things other teams and teammates are working on — even if it feels irrelevant today

Because you are the one who connects the dots.

Code generation is getting cheaper. It's not free — not even close — but it's cheaper every month. What is nowhere near being replaced by AI is the ability to take responsibility for carrying something from beginning to end and to create actual added value for the people you're building for.

You understand why a feature exists. You understand what the customer is actually trying to do. You know which edge cases matter in your system, with your data, in your context. An AI doesn't have that context. You do.

That's the thing that creates value. That's the work that matters.

A friend of mine recently gave me the best metaphor I've heard for AI-assisted development:

> The future of coding is Paint by Numbers.

At first it sounds deflating. Are we just coloring in? But here's what he actually meant:

You set the lines. You set the numbers. (Someone or something) paints them in. You own the picture.

The template — the lines and the numbers — requires vision. Taste. Knowledge. Judgment. You need to know which lines to draw, what belongs in each section, and whether the finished picture solves the actual need.

The painting — the code generation, the boilerplate, the implementation details — that's the step that AI is rapidly taking over. And you know what? That's fine. That was always the least interesting part of the job.

What AI can't replace is knowing what picture to paint in the first place.

You judge whether the outcome meets the need. You are responsible for knowing which lines to draw, where to put which numbers. You are responsible for the result.

So what actually changes in the age of AI?

One step in the game gets faster — and cheaper. The "painting in" step. That's real, and it matters. Don't get stuck there. Don't spend your growth energy optimizing for the part that AI is commoditizing.

What doesn't change: the need to understand your environment deeply, to spot unseized opportunities, to take end-to-end ownership of outcomes, and to connect the dots across systems, teams, and contexts that no model has fully internalized.

The best description I know of a senior engineer isn't "writes excellent code fast." It's: someone who creates something that has genuine value — and knows how to make that happen.

AI doesn't threaten that definition. If anything, it clarifies it.

There's a temptation right now to be anxious — to feel like the ground is shifting under your feet. Some of it is, honestly. But a lot of the anxiety comes from confusing code writing with software engineering.

Software engineering is a much bigger, more interesting, more human thing. It's the thinking before the code, the communication during, the judgment calls throughout, and the ownership after.

Keep honing your skills — all of them. Learn your tools deeply. Stay curious about the systems around you, not just the ones you directly control. Practice the discipline of understanding before building.

And do not forget the big picture.

There's no AI bot for that yet.

—

This post is adapted from a keynote talk on the role of developers in an AI-accelerated world. The core ideas — shipping skills, environmental awareness, and the "Paint by Numbers" metaphor — came from a developer summit where we asked ourselves: what does it actually mean to do great engineering work today?

• Navigating difference and disagreement
• The Engineering Executive's Primer [Book]
• The conflict continuum — Confident Communicators, LLC
• Rethinking Interviewing In An AI Era
• Thinking in Systems Book Sale - The Donella Meadows Project

• Checkly: Application Monitoring Powered by Playwright & OTEL
• Swarmia: Rethink developer productivity
• Uptime Labs

• Prompt Engineering Ebook
• DORA | State of AI-assisted Software Development 2025

• jstanier/bragdoc: Generate a doc from your activity in Linear.
• Gamma | Bester KI-Präsentations- und Website-Builder

• 2024 State of DevOps Report | Google Cloud
• DORA | Get Better at Getting Better
• DORA | Research
• DORA Community of Practice

• The Caring Techie Newsletter | Irina Stanescu | Substack
• Newsletter of Lena Reinhard
• Circles of Influence, Concern, and Control (link suchen)
• Service Catalogues
  • mapping all the things (ist das eine Prozesslandkarte?)
  • people us Backstage Software Catalog and Developer Platform for this
  • plus 2 more? see ? Lisa Karlin Curtis (@LisaKC_) / X presentation
• Shape Up Product development workflow by 37Signals/Basecamp

• xkcd: Is It Worth the Time? I use this graphic every other month.
• The Pets Table: Healthy Dog Food Developed With Vets HelloFresh for dogs

I got married and therefore changed my family name from Christian Bäuerlein to Christian Dewein!

I always liked my old name as well, but getting rid of the Umlaut is - even in 2024 - very convenient!

I live in Frankfurt am Main and still enjoy living in this city!

I am the CTO of the ioki GmbH in Frankfurt. Since 2017 I am part of this company and I am very proud of it.

Over the last years, I did quite some travelling. I like to explore nature and experience wildlife. Most notably, I travelled to Costa Rica, Namibia, the west coast of North America and South Africa.

I love being part of Frankfurt's meetup scene. I organize a couple meetups myself and visit even more. I also like to serve as a host for other meetups at my company.

Most notably I organize the Mechanicon - Europe's biggest mechanical keyboard conference.

• KeebKaigi 2023 Japanese Keyboard Conference
• PicoRuby The smallest Ruby implementation for one-chip microcontrollers
• picoruby/prk_firmware A keyboard firmware platform in PicoRuby
• Raspberry Pi Pico can be programmed with PicoRuby/PRK and can be mounted via USB to flash it

• Bret Victor does interesting things
• Domain-Driven Design Crew Repo with all kinds of resources
• Ultimate C64 Reference C64 BASIC & KERNAL ROM Disassembly

• llamafile Distribute and run LLMs with a single file
• Rabbit the tool that Matz uses to do his presentations (turtle races bunny)
• VICE the Versatile Commodore Emulator
• VRoid Studio is a tool to create and use virtual avatars (Twitch streamers do this?)

• FOSSGIS 2024 - media.ccc.de
• Favorite Talk: Räumliche Fragmentierung im ÖV-Angebot sichtbar machen - dank offenen Fahrplandaten von Theodor Rieche
• Talk Geheimtipp: Prozedurale Kunst mit QGIS von Johannes Kröger

• BBOX Server - Composable spatial services written in Rust
• DuckDB - An in-process SQL OLAP database management system
• geonetwork Github org - GeoNetwork is a catalog suited to publish information about geospatial data
• geonode - GeoNode is an open source platform that facilitates the creation, sharing, and co
• geopolars/geopolars - Geospatial extensions for Polars
• leafmap - Geospatial analysis and interactive mapping in Jupyter
• ol-describe-map - Generate textual description of an OpenLayers map
• pg_featureserv - Lightweight RESTful Geospatial Feature Server for PostGIS in Go
• pretzelai - Open-source, browser-local data exploration using DuckDB-Wasm and PRQL
• public-transport Github organization

• CKAN - The open source data management system
• DKAN Open Data Portal
• Greenpeace Datenportal
• Zenodo

• ahoi Hamburg by vhh.mobility - Autonomous driving in Hamburg
• comaps - Digitales Werkzeug zur datengestützten Entscheidungsfindung für eine integrierte und nachhaltige Stadtentwicklung.
• GBD WebSuite - Webbasierte Open Source GIS Plattform zur Geodatenverarbeitung
• Geoportal.de - Bundesamt für Kartographie und Geodäsie
• GOAT 3.0 - Entwicklung eines digitalen Erreichbarkeitsinstruments für eine ausgeglichene Raum- und Verkehrsplanung
• GRASS GIS - Powerful raster, vector, and geospatial processing engines in a single integrated software suite
• KomMonitor - Kommunales Monitoring zur Raumentwicklung (Demo)
• Lizmap - Create Web map applications with QGIS and Lizmap
• Mapbender - Lösung zur Erstellung intuitiver und performanter WebGIS-Anwendungen
• Masterportal - Open Source Geo Portal
• Sovereign Cloud Stack - Cluster Stacks
• STAC: SpatioTemporal Asset Catalogs - A common language to describe geospatial information

Let's take a trip back to 2016: The whole world was playing Pokemon Go, the most common password was ‘123456’ and '/r/mk' had around 120k subscribers - merely 10% of the size it has today.

Three programmers were nerding out on their new hobby: Mechanical keyboards.

You all know the rabbit hole we are talking about here: discovering the hobby, the manufactureres, the back and forths of the different parts and also the struggle: what should I get myself?

Back then the keyboards we liked had to be bought directly from shops in the U.S., Japan or South Korea. In other words: ordering a keyboard was going all in, including high shipping costs, import taxes and not really a return policy.

It was clear what we were missing: a chance to try before you buy.

Outside of our office, in real life, we did not know a single person interested in the hobby. So we founded a user group: Mechanical Keyboard Meetup Rhein Main.

The first meetup was given the tongue-in-cheek name 'Mechanicon', suggesting it was a conference. In reality, we hoped to attract about a dozen people. In the end, it would be over 60.

Only on the day of the Meetup it would become clear to us, that there was something special about this community and this event.

People would come from Berlin, huge plastic bags with hundreds of keycaps in the trunk. They would come from France - by bus - with a douzen trackballs in their luggage. Manufacturers, bloggers, collectors, gamers, all came together to celebrate their hobby.

This atmosphere, the excitement of everyone, the respect for the community and the love for the craft is what makes the Mechanicon what it is until this day. And it is also what motivates us to organize this event again and again.

---

Thanks to Alceon for making the video!

---

• Mechanicon Official Website with links and pictures from past events
• Mechanicon on Discord
• Me on Mastodon
• CLICK! CLACK! HACK Podcast about Mechanicon 2023! (German)
• CLICK! CLACK! HACK Podcast about Mechanicon 2024! (German)

When deciding for a keyboard I am really looking for top notch build quality. My daily drivers have mostly been from Leopold or Filco.

I need my keyboard to make me as productive as possible in editing text, be it in the browser, my email application or in my text editor. My whole organization workflow is completely keyboard based and I invested quite a lot of time to get it just the way I want it.

So when a product like UHK advertises deep configurability this means quite something for me. It has to prove that it deserves to be considered in the hours of hours of fine-tuning my setup.

The UHK shop offers a lot of different options for key switches, layouts, keycap printings and cases colors, 240 variations overall.

This is my version of the Ultimate Hacking Keyboard:

• Switches: Kailh Brown
• Layout: US-ANSI
• Keycaps: Mac printings
• Case color: Black
• Accessories: Palm rests

The UHK has a nice packaging and even greets you with a thank you note from the manufacturer, Ultimate Gadget Laboratories.

The onboarding tutorial is very good. You get introduced to the keyboard and how you can use the keyboard in a ergonomic way, something I highly appreciate.

I think there is even room for more: Tenting or Tilting? For now I go with negative tilting, but since you can not have both with the UHK, I would be happy to get even more information to make a decision on this.

The pre-built keyboard case feels nice and solid, all the single parts have a high build quality and get you excited for the next steps.

The next step is to assemble the keyboard. The case, plate, switches and keycaps are already in place. But I still have to connect the keyboard to the bases to get my tilting right.

Again, the manual for this is very good and precise.

The alignment of the components before fixation is pretty straigtforward. There is always some knob or cavity that helps to set them properly.

The fixation itself is a bit trickier than anticipated. The UHK tutorial even provides a video how to drive screws into plastic. But to be honest, I didn't get it - it says the screw should click(?), never clicked for me though (pun intended).

The screws are very tiny and I am very proud of myself that I didn't let one slip off my desk. I still appreciate that they threw in three extra screws to prevent possible frustration in case of losing one.

Alright, back to the bases. After some back and forth I managed to screw in the sockets for the feet with no visible gap.

The plastic of the sockets is a bit sensitive and of course I scratch one with the screw driver. If I would want to switch from tilting to tenting the keyboard, I would need to re-assemble the feet/sockets and I wonder how often you can do this without damaging them.

On the other hand, they offer replacement feet at a very fair price, so there is really no risk that you ruin your keyboard by damaging a small part.

Snapping the feet to the sockets is super smooth.

In the end, the whole keyboard looks sturdy and solid and I am very happy and can't wait to try it out.

It has been 45 minutes since I opened the package and the keyboard is not even plugged in.

Compared to building your own keyboard the excitement of opening a pre-built keyboard can wear off very fast. I love my daily driver keyboard but the setup process took about 10 minutes and then it was just there.

Due to the extensive onboarding the UHK creates this kind of journey that you usually only get from DIY keyboards.

I personally crave this customization effort. It makes a tool more worthwhile for me when I have the feeling to have a deep dive up front. So this is a lot of fun for me.

After some more information in the tutorial on the default keymaps, I am finally ready to go!

First things first, the Ultimate Hacking Keyboard is very comfortable to type on!

I never really used a split keyboard and this one comes very naturally to me. Neither having two parts, nor the tilting of the board affects me.

I takes just a few minutes to get me into my typing flow and I feel comfortable. An important part in this is probably the key layout that is very close to a "normal" keyboard, especially when compared to other split keyboards.

The keyboard has a good weight so you can be sure it can keep a stable position on your desk. Nothing clatters or slips, even with the tenting. It is a very solid keyboard and I like it a lot.

However, it comes apparent that the default keymap will not work for me. So let's look into this.

The space bar is split and in the default keymap, there is actually only a Space key on the right, what would be the left part of the Space bar is the Mod key. As a touch typist I use both thumbs to press space, so this is not acceptable for me.

Naturally I am taking these notes in org-mode using VIM-style keybindings. The fact that Esc can only be triggered by Mod+~ causes the most pain at this point.

Outside of my evil Emacs world I use some of the default Mac shortcuts to navigate along text. In my muscle memory, I use the ones that involve arrow keys, like Shift–Command–Right (select the text between the insertion point and the end of the current line) or Option–Shift–Left (extend text selection to the beginning of the current word, then to the beginning of the following word if pressed again).

But on the UHK there are no dedicated arrow keys. You have to press the Mod key to activate the layer that gives you arrow keys. So these slightly uncomfortable three-key-shortcuts become almost impossible four-keys-shortcuts.

As you may have seen on the linked Apple support page, most of this can also be done without the use of arrow keys (in Emacs style, actually). I just have to revert decades of muscle memory, so this will cause some pain over the next days and weeks.

If you look closer at the keyboard, you will also notice that UHK sneaked an additional key between the Cmd keys and the Space bar keys: the Fn key. First I was hesistant to this. But then I realized they took the room for the Fn keys from the Space key which means the position of the Cmd key stays the same compared to other keyboards. After some back and forth I decided to not change the position of the Cmd key. For my muscle memory the physical position of the key seems more important than the strict order of the keys, so in practice it does not bother me that much.

Another important anomaly is that UHK placed the key for the Mouse layer where you can usually find the Caps Lock key. Like a lot of VIM/evil-mode users I mapped Caps Lock to Esc (when pressed alone) and Ctrl (when pressed with other keys), an essential keybinding that I am not willing to lose. So I will need to find another place for the mouse layer key.

The UHK Agent is easy to use and pretty straightforward. You don't need to set the keyboard in to a special flash mode. The keyboard must be plugged in, you start the Agent, everything is ready.

My first change is to remap Caps Lock from Mouse to Esc/Ctrl. The user interface is very self-explanatory and it just takes a second to save the changes to the keyboard.

I also mess around with the Mod mode to change the arrow keys in the mode to VIM-style arrow keys (hjkl).

The UHK supports multiple keymaps and you can use shortcuts to switch between QWERY, Dvorak and Colemak. For me as a Mac-only user it is not of special interest. But maybe it is for others, because it is the one software feature that gets the most prominent representation in electronics.

The UHK comes with three small fourteen segment displays built into the case. As far as I could find out they are only capable of showing the current keymap. Otherwise they are rather useless for now.

There are amibitons to make them more interesting, which is good, because I don't need to see that I use Mac QWERTY all the time. I hope for this to arrive sooner than later. Until then it is just a bit weird that you have such a prominent component to show only such a specific detail.

Lifehack: The three letter abbreviation that you can see can be changed in the UHK agent. Another alternative is to just set the brightness of the display to zero to avoid any distraction alltogether.

At the first look, I didn't like the small extra buttons on the bottom of the case. But since I am in severe need for extra keys I start to appreciate them. They feel like a mouse key, yet work pretty good as modifier keys.

The Agent has an auto update which will alert you, when a new version is available. In the future new versions of the UHK Agent will also ship with new firmware versions for the keyboard.

To sum it up: UHK Agent is pretty awesome overall. It did exactly what I wanted it to do.

You can see my modified keymap in the screenshot. Some of the changes invoke immediate pleasure, others probably need some time and learning to work for me.

However, note-taking in evil mode is now a pleasure and I am happy to test the keyboard for an extended period of time, to really find out if it works for me.

For two weeks I use the keyboard about 50% of the time and a laptop keyboard for the other 50%. This causes no noticable confusion. Somehow my muscle memory is able to distinguish between the two contexts.

So I remapped the Fn keys between Cmd and Space to Mod and changed the arrow key positions in the mod mode to VIM style. This means, pressing Mod with j and k for up and down now works in every app. I never want to miss this again!

One feature I keep stumbling above: The UHK has the feature to lock modes (like Mouse, Fn, Mod) by double tapping a key that serves as a mode key. This is kind of a two edged sword for me. If you do it intentionally, e.g. with the mouse mode, it is great. When you activate it by accident it still takes me 10-15 seconds to realize what I have done and why the keyboard behaves so strangely.

I would say I have adapted the arrow-less lifestyle about 80%. Just some slight confusion here and then in org-mode specific mini buffers.

The split-factor of the keyboard is pretty nice. I still feel like I don't have to re-learn general touch typing to operate this keyboard. I experimented a bit with the distance of the two keyboard sides and found a setting that is comfortable for me.

I use the keyboard while sitting down and standing at my desk. The keyboard is steady and stays put during usage.

Due to the Mechanicon, I think I was able to try out a lot of switches over the years. I know what I like but in everyday use I am not able to determine the sublte differences between similar switches.

For the last five years, I used Cherry MX Browns, Cherry MX Blues, Gatereon Greens and Topre 45g switches as my daily drivers.

I chose Kailh Brown for this board, because I wanted something similar to MX Brown. In practice I actually can't determine a difference.

Something I learned over the years is that it is not only about the keycaps themselves, but also how they are fixed on the keyboard. Again, the build quality is very good: No clang or vibrations, just a very sturdy construction.

What can you say about the keycaps? They work fine but they don't spark joy in me. A lot of keyboards come with subpar keycaps and unfortunately the UHK is no exception.

Leopold keycaps are my personal standard for off-the-shelf keyboards. And you can see the difference in material and thickness in the photo.

UHK provides you with an extensive guide on the keycaps and layout which is very cool for people that want to use their own keycaps instead. However, since it is a split layout there will be some struggle involved when looking for alternative keycaps (e.g. due to the split space bar).

I get that better keycaps would make the UHK even more pricier and maybe a lot of people are ok with the default keycaps. Due to the exotic layout, I still would wish UHK would provide an upgrade option to get better keycaps.

Update: I got told that UHK actually plans to provide PBT keycaps eventually. I really anticipate it and hope for an upgrade kit!

For me, this deserves a special shout out! The firmware as well as the electronics design and pretty much anything else is freely available.

Additionally, you can clearly see that the keyboard was built by people that care a lot about real and deep customization.

Not only in the software but also in hardware. From the replacable bridge cable to the online shop for the keyboard feet: it shows me that you don't have to be afraid of playing around with your setup.

The UHK is a nice, high quality keyboard that also comes at a high price point.

The defaults settings are sane and well-intended, but let's be honest: This keyboard is for people that want to heavily invest into the perfect custom typing experience. I count myself into this target group.

Usually I am happy when the manufacturer just stays out of my way when I start to fumble with their stuff. UHK goes beyond that and supports me in many ways in the customization process: Great onboarding, tooling, repairability and documentation make it easy for me to get my way with this keyboard.

If you are willing to invest a lot of time and effort into customizing your setup the price of the hardware is usually a secondary factor, compared to the time that you will pour into it.

So if you are into ergonomics, if you want to discover the world of split keyboards and you want to customize the sh\*t out of your keyboards, then this is the keyboard for you.

When you work together with other people in a team, and they care about what the team is doing and the team is somehow successful, you probably already share some unsaid values among the members of this team.

I am lucky to work in such a very well performing and friendly team.

Sometimes this is not the case and working with the team is frustrating. But even if the collaboration is inert or exhausting, there may be a good chance that you also share some values. They are just misinterpreted or not recognized.

The point is: You will talk about values one way or the other. Everyone has personal values. They will come up at some point, in a discussion, an argument.

The more stressful the situation is, the less likely it is that you will really understand each other. Perspectives and approaches differ and it takes some time to realize which values you share. It is much easier to really get each other when you put some time aside to specify upfront what’s important to you. It will also be easier to remember the values and live by them, once they are clarified and written out.

For me, this is like the technical part of developing software. You can take your time now to think about how things should be and write some specs for it. Or you can wait until production is on fire. You will think about it one way or the other, but I am sure the former approach is much more efficient and pleasant.

Sometimes these kind of “core-value-finding team offsites” are primarily a way to get to know the colleagues a little bit better and create some common ground. This is fine too, but I wanted to go further.

I didn’t want us to define core values as an end in itself, but as a base for further actions to take our team to the next level. If you don’t live by a value, it’s not really a value to you. In order to live by these values, they must be actionable.

So an additional task, beyond the definition of values, would be to put some thought into actions that bring these values to live. Which daily routines, tools, processes, behaviours or events can support a value?

By reflecting about the values and how to make them actionable, we would have a much more intensive and detailed discussion about every proposed value.

I looked for the best way to do this and found my answer in the book Tribal Leadership. It defines two terms:

Core Values – What does the team stand for. The shared values of the team. A value can be defined by terms like “Quality”, “Courage”, or “Trust”.

Noble Cause – What does the team live for. It is meant as a credo, a short description of what the team aspires to be. The book gives some very good examples. In other words, I would define it as the mission statement of your team.

It is important to understand the difference between both.

The Core Values are the foundation, the basecamp of which the team starts off right now. The Noble Cause gives the team the right direction, reminds them of what they want to become.

Therefore it is important to look out for actionable items. They should build upon the values and support the team to move in the right direction, towards the noble cause.

Based on these ideas we did a one day offsite with the whole team. In the next section, I will describe what we did and how it went.

This was the first time I organized this kind of event for my colleagues and I was very nervous. They were all very supportive of the idea, but I know that this kind of events can get a kind of cheesy vibe, which will result in eye-rolling and snarky comments and would basically undermine the whole idea. So one of my top priorities was to get my teammates into the mood to give it a serious and honest try.

We took a whole day for this. We were eight people and met in a creative space outside of work, to not be distracted. I brought coffee and some soft drinks. We started slow.

I wanted everyone to feel comfortable, because I think it was crucial to the success of this event that people were relaxed and open to the work we wanted to do.

I waited one month to write up this article, because I wanted to see if the results of this offsite would last. The offsite was not meant to change the life of every team member, but I really hoped it would have a positive, sustainable impact on the way we work.

Here are some of the actionable items that we already took action on:

• We created a Slack channel to discuss and remind ourselves of our core values and noble cause.
• We printed the core values and noble cause on two large posters to hang it in our office.
• We shared and explained the core values and noble cause to candidates and new team members during our hiring process and onboarding process.
• We discussed concrete rules for better commit messages.
• We settled some heated discussions by stopping for a second and reminding ourselves about our values.
• We revived a company internal book club and read a book together.

A lot of different ideas were created in this initial workshop. Sometimes the scope is very broad (book club), sometimes the scope is very specific (better commit messages). But they all pay into the same values, our values. I think it is great that we have such a wide variety of small enhancements coming from this.

I am very proud of our core values and noble cause, so a part of me really wants to share them. But I won’t. This is something we did for us, that is important to us, and tailored for us.

Maybe someday we will decide to publish them. For now, we will keep them hidden in our little dev tribe. We just want to see where this goes.

---

This article was first published September 21st, 2017.

Thank you for reading my article! If you spotted a mistake or you want to provide some feedback, please get in touch with me.