Hi, I'm Braden.
I help AEC teams turn the repeated work they still do by hand into custom tools they use repeatedly.
I've spent my career inside AEC consultancies, so I know what actually makes delivery more efficient.
For years, I've had a job that's hard to explain.
For most of my career I've been the "digital person" inside structural engineering consultancies.
I've built applications, tools, scripts and workflows for companies and projects. It's a strange place to be in because it's a different kind of technical that most people can't follow and a role that the industry has never agreed on.
But the whole point is to solve problems with computers, not as a pure software developer but a person that connects digital with the physical.
I turn a messy, repetitive problem into a tool your team can rely on.
But what makes a tool valuable is rarely the technology.
I've built tools that whole projects relied on, and tools that collected dust in a folder because it wasn't thought out properly. The difference was almost never the code.
It was communication and understanding, whether the thing fit the way people actually deliver.
So I started CodedConstructs.
To take the approach that actually works on real projects and bring it to your team.
The value is not just making the tool, it's also in turning a messy problem into something that can repeatedly deliver value.
Ways I add value →Understand
Get to the root of the real problem before a line of code is written.
Build, test and document
Build the tool around how your team already delivers. Document everything and test it against criteria to ensure it's production-ready.
Adopt
Make sure it's reliable and trusted by your team.
Maintain
Keep it working as projects, teams and requirements change.
Where else to find me.
I'm also active in a couple of other places on the internet.
The best tools work with your team, not the other way around.
That's what CodedConstructs is here to build, turning your best workflows into tools for more efficient delivery.