If we are obsessed with our tools or technologies and want them to work in vast and different ways, you will get a system that has a lot of technological complexity.

Technological complexity is excessively reliant on technologies and tools, especially new and shiny ones.

The challenge of complexity is not only a software problem - it’s a human challenge too.

Most software systems today have a lot more than 14 micro-services, which gives them over 87 billion possible combinations. This is where the complexity comes in because people can only have four to seven different things in their mind at one time, and do not inherently understand things like large numbers. If you have a system with seven components, and those components can interact with each other without constraints, you will have a system that has 5,040 possible combinations and permutations of the seven components. Engineers have a better grasp of complexity than most others do because they have been exposed to mathematics and real-world constraints.

Here Are Some of the Key Points Discussed in This Episode: In this episode, we talk to Jeff Doolittle, a software architect and transformational leader with more than 20 years of experience designing and architecting software systems about the importance of complexity in engineering, and how engineers and engineering leaders can manage complexity in their organizations. Podcast: Play in new window | Download | Embed

Trimble license manager