Making time to get better

Most software companies say they value learning. Fewer put time and money behind it in a way you could point to. A few months ago we started doing exactly that, and it has become one of the things we are most glad we built.

How it works

Anyone at Isotoma can put forward an idea. It might be a technique worth learning, a tool worth trying, a process worth testing, or a problem worth poking at. It does not have to be about code. A small team reviews what comes in, and the ideas we think are worth it become proper projects: someone is given the time, on work time, to explore the idea and write up what they found. Those findings then go back to the whole company.

That last step matters. An experiment nobody hears about is a hobby. The point is that what one person learns, everyone gets to use.

Why we bother

1. For the people who work here. Good engineers, designers, and delivery people want to get better at their craft, and they rarely get paid, uninterrupted time to do it. Giving them that time is one of the few things that genuinely earns loyalty, and it is a large part of why people stay.

2. For the people who hire us. When you bring us a problem, you are buying judgement as much as hours. Judgement comes from having tried things, including the things that did not work, on someone else’s time rather than yours. A team that keeps deliberately getting better is a team whose next call is a little sharper than its last.

What it looks like in practice

The clearest example so far is CSS Shine. One of our developers has a real interest in frontend detail, took it through this process, and came out the other side with a hands-on lab on the modern CSS that makes software feel polished. It is now something the whole team can learn from, and something we can show you rather than tell you about.

That is the shape we are after. Not innovation as a poster on the wall, but a steady habit of getting better, in the open, with something to show for it.