Read the full story here

We’re excited to share that Structure101 has been acquired by @SonarSource! Folding Structure101’s capabilities into Sonar’s products will empower developers to better architect their code early in the development process.

While it’s fairly normal for technical team leads to work to minimise #technicaldebt, they often fail to communicate the importance of resourcing these efforts?. According to @CapeofGoodCode1, they may be using the wrong messaging @InformatikAktue.

Who is to blame when complexity spirals out of control?. Until someone is made directly accountable for controlling measurable complexity on a project, inevitably complexity will end up controlling the project. #complexity.#codequality.#softwarearchitecture.#softwarearchitect

“The purpose of software engineering is to control complexity, not to create it.”.- Pamela Zave. You have ‘a level’ of complexity by the second line of code. After that, it’s simply orders of magnitude. Complexity is necessary. It’s unnecessary complexity which should be avoided

If you can improve the structure of your #code, you’ll find that it actually becomes an intrinsic part of the quality of your #codebase. #Structure is built over time. #Complexity can happen very quickly…. #technicaldebt.#softwarearchitecture.

While it’s fairly normal for technical team leads to work to minimise technical debt, why is it so often the case that they completely fail to communicate the importance of resourcing these efforts to management?. #structure101.#technicaldebt.#codequality.#softwarearchitecture

Taking a look at #complexity in #softwarearchitecture, how it can get out of hand very quickly, and why it's so destructive. #structure101.#codequality.#cyclicdependencies.#cplusplus.

One thing is for sure – cycles make it much harder to tell the story of a codebase. The fact that this quote from John Lakos' book is almost 30 years old, but still resonates, says as much about the point as it does about the book!. #softwarearchitecture.#codewisdom.#codequality

In the early ‘90’s the US Department of Defense commissioned Mitre to develop guidelines for the successful acquisition and management of #software systems. One of the reports significant conclusions stated:. #softwarearchitecture #structure101 #codequality

RT @vincentdnl: A drawing I made today: technical debt (or more likely a rotten codebase), explained to non-technical people! https://t.co/….

RT @unclebobmartin: ⁦@KevlinHenney⁩, consistently brilliant. Refactoring Is Not Just Clickbait - Kevlin Henney - NDC London 2023 - YouTube….

Managing Engine Updates in C/C++ #GameDevelopment. #Gamedevs are making use of a new #Structure101 dependency database to manage #gamesengine usage and updates in a more informed and predictable way. #cplusplus #gamedev #softwarearchitecture

#C/C++ models can be difficult to interpret if the file structure of the model doesn't reflect the structure that the project team are used to. #Structure101 has a set of features for manipulating the generated file and folder names. #SoftwareArchitecture.

API control between projects using the #Modules feature in #Structure101 Studio:.1: Controlling access to a folder by other projects #softwarearchitecture #cplusplus.

'Using Structure101 “modules” to control APIs in #C/C++'. How to achieve API control between projects using the #Modules feature in #Structure101 Studio. #SoftwareArchitecture.

Great #podcast from @sglebs on managing #technicaldebt. Worth listening to for the "amazing analogies" alone.

Thanks @ewolff for hosting @chedgey and @mike_rainford on your live stream today. And thanks to @Teapot4181 for the annotations. Playback available from

RT @Teapot4181: Thanks to @mike_rainford, @chedgey and @ewolff for the demo of @structure101 in today’s episode of #SoftwareArchitektur im….