Skip to main content

An Exploration of Symbiotic Design Practice workshop at NorDevCon from Michael Feathers

Feature Orthogonality and Health In Large Code Bases

Too often as software developers we take features as given – EE are there to give the customers whatever they want. The thing we neglect to realize is that feature choice impacts the longevity and maintainability of systems. In this keynote, Michael Feathers will explore this idea and describe now we can move toward a model where business weighs these impacts in the context of systems development.

Collection Pipeline Design Techniques

The resurgence of functional programming has had an odd manifestation in today’s technologies. Although we’re learning the value of immutability and starting to see that we don’t need class hierarchies to solve every problem, the type of code that we’re writing is actually stricter than what has been common in traditional functional programming languages. We’re using LINQ, Rx, Java Streams, and Ruby Enumerable to compose pipelines that transform data from stage to stage without access to any other state. This calls for a different design approach. In this session, Michael Feathers will outline strategies you can use to decide when and how to use this style.

Workshop: An Exploration of Symbiotic Design Practice

Decades ago, Melvin Conway coined what is now called Conway’s Law: “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” Conway’s Law is a deep insight but it is only the tip of the iceberg when we try to understand the interaction between organization and software. We fail to appreciate that we can use team structure, day to day process, and the interface between business and development as levers to affect the quality of design and code. With this perspective we can also see that concerns like technical debt and portfolio management lend themselves to new solutions when we understand software’s sensitivities upon its environment.

In this workshop, we’ll explore the intersection between software and organization through a series of group exercises and discuss ways of putting this understanding into practice.

About Michael

Michael Feathers (@mfeathers) is the Founder and Director of R7K Research & Conveyance, a company specializing in software and organization design. Prior to forming R7K, Michael was the Chief Scientist of Obtiva and a consultant with Object Mentor International. Over the past 20 years he has consulted with hundreds of organizations, supporting them with general software design issues, process change and code revitalization. A frequent presenter at national and international conferences, Michael is also the author of the book Working Effectively with Legacy Code (Prentice Hall, 2004).

Michael's workshop is on Thursday 25th of February at the Kings Centre in Norwich and tickets cost just £20 + fees.

Comments

Popular posts from this blog

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...