Hi, I'm Braden.
I build software around the way structural teams actually deliver projects.
I've spent most of my career inside structural engineering consultancies, working somewhere between design, delivery and software.
For years, I've had a job that's hard to explain.
For years, I was the "digital person" inside structural engineering teams.
I've built applications, tools, scripts and workflows for engineering firms and live projects. The role never fit neatly into engineering, drafting or software development, and the industry has never quite agreed what to call it.
My job is to solve project problems with software while understanding the physical work behind them.
I turn a messy, repetitive problem into a tool your team can rely on.
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 they weren't thought through properly. The code was rarely the difference.
What mattered was communication and understanding. The tool had to fit the way people actually delivered the work.
So I started CodedConstructs.
I wanted to bring that way of working to structural teams without someone in-house to do it.
Before I build anything, I turn the messy workflow into a process we can explain, test and repeat.
See services →Understand
Understand the workflow and agree what the tool needs to do before writing code.
Build, test and document
Build around how the team works, then test it against agreed criteria and document it properly.
Adopt
Help the team use it confidently on real project work.
Maintain
Keep it working as projects, teams and requirements change.
Have a workflow your team keeps doing by hand?
Tell me how it works now. I'll help you work out whether a custom tool would make sense.
Where else to find me.
I'm also active in a couple of other places on the internet.
