Posts

  • What's been missed in remote vs return-to-office? The “first” in remote-first

    Remote vs return-to-office is close to a culture war issue now, so what do I have to add? And having spent years of my life obsessing about the design of physical office space, isn’t it a bit weird that I’m pro-remote? Not at all. I’ve always been searching for a way to make a working environment for software development, that weird mix of deep focus and high collaboration, as good as possible.

  • The past, present and future of Multi-Tenancy - Part 3: The Future

    This is the third post in a 3 part series about the past, present and future of multi-tenancy architectures for enterprise software products. I am a strong believer that understanding where we have come from, and how we got here, helps us predict where are going.

  • The past, present and future of Multi-Tenancy - Part 2: The Present

    This is the second post in a 3 part series about the past, present and future of multi-tenancy architectures for enterprise software products. I am a strong believer that understanding where we have come from, and how we got here, helps us predict where are going.

  • 'Be Less Shit' isn't a real book... but it does show how generative AI can turbocharge creativity

    Perhaps even more surprising than the number of people who browse LinkedIn on a weekend is the number of people who believed that I would write a book called Be Less Shit - No Excuses, No Bullshit: The Brutally Honest Coaching Method. See the original press release.

    I don’t think I need to explain why I decided to pull this April Fools prank. But it is worth explaining how I made it, because it surprised (and delighted) me.

  • New Business Book 'Be Less Shit' Provides Fresh Perspective on Coaching

    Check the date. And read the follow up post.

    The Get Real Group are excited to announce the launch of their new business book Be Less Shit - No Excuses, No Bullshit: The Brutally Honest Coaching Method, comming soon to Amazon, Barnes & Noble and all airport bookshops.

    Drawing on their extensive experience as a coaches and business leaders, The Get Real Group offer a fresh and engaging approach to coaching that is both practical and insightful. Unlike other coaching books that focus on directive approaches, “Be Less Shit” encourages a more collaborative and empathetic approach to coaching.

  • Resource: Did you mean person?

    I’m on a mission against calling people “resources”. It’s endemic. And it needs to stop.

  • The past, present and future of Multi-Tenancy - Part 1: The Past

    This is the first post in a 3 part series about the past, present and future of multi-tenancy architectures for enterprise software products. I am a strong believer that understanding where we have come from, and how we got here, helps us predict where are going.

  • On Error Resume Next / Don't Know Just Guess

    As a young lad, hacking about in Visual Basic, I never really appreciated how wildly dangerous the statement ON ERROR RESUME NEXT slapped at the top of each file really was.

  • Innovation vs messing about

    It is easy to confuse “innovation” with not knowing what you’re doing. Good innovation is quite the opposite: you know exactly what you’re doing, it is just the outcome that is uncertain.

  • Back to the (future) office

    Like many other product development team around the world, the global pandemic has meant we’ve found ourselves as an all-remote team since March. In the UK, there is much talk around “return to the office”. But we’re not rushing to return to the status quo.

  • Noise and the developers

    The impact of noise on development teams is a topic I’ve wanted to write about for a few years. We’re now in the midst of designing our new London office (Deloitte Studios) and this has become incredibly relevant. In our user research, acoustics is coming out as a very high priority. The backlash against open plan, and the poor acoustic experience this tends to deliver, is strong. It’s also giving us a great opportunity to explore this in more detail and test our hypotheses.

  • Single use disposable tech

    Sometimes we don’t need robust systems… we just need to be able to use powerful tech to get an answer. And then it’s disposed of. Think of this an experiment, redefining what we mean by “experimental tech”.

  • Just

    “It just needs to…”

  • Innovation Architect – making it cheap enough to not worry about being right

    Across the software development and IT professions there are so many uses of the word Architect. You’ve got your Enterprise Architects, your Solution Architects, your Application Architects and, my favourite, the Ivory Tower Architect. With the exception of the last one they do each have their place. In general they provide an elevated viewpoint of how a particular development fits into a wider picture and provide a balance between immediate demands and the longer term ambitions of an organisation. They are predominately worried about being right – that is, making decisions that when looked at over a longer time period other people will view as being sound.

  • Culture poker

    I adapted Planning Poker (as used in agile software development) to rapidly uncover where we had alignment and divergence as a management team. As a first attempt this worked well, so I’ve written this play-at-home guide – I’d love to hear how you get on with your teams.

subscribe via RSS