control_shift

About Control Shift

Software has always been the work.

Control Shift is led by Dominic Duke, an experienced software engineer who remains personally involved from the first conversation through to the software taking shape.

Portrait to come

Dominic Duke

Founder · Software engineer

Meet the founder

Dominic Duke

Dominic combines hands-on software experience with an unusual ability to make complex technical ideas clear.

In the final year of his studies, the University of Tasmania hired Dominic to run software tutorials. He continued teaching for several years, helping hundreds of students build confidence with complex technical ideas.

Since then, he has worked in industry and independently across real organisations, products and operational systems. Today he remains personally involved in the thinking, technical decisions and development behind Control Shift's work.

Software changes quickly. Staying current is part of the work Dominic genuinely enjoys; experience provides the judgement to know which ideas are useful and which will only add complexity.

What that means for clients

Senior judgement stays close to the work.

01

Direct access

You work with the person responsible for understanding the opportunity, shaping the solution and leading the development. Important context does not disappear through layers of account management.

02

Clarity before code

Complex technology should be explained in plain language. Options, trade-offs and decisions stay visible, so you can understand what is being built and why.

03

Working software, early

Progress is demonstrated through the real product taking shape. Regular working reviews create better decisions and keep the project connected to the people who will use it.

04

Built to remain useful

Maintainable code, clear documentation and thoughtful technical choices matter. The software should be ready to evolve as the business and technology change.

Start with clarity.

A focused Software Direction Session can turn an opportunity into clear priorities, a recommended approach and practical next steps—before you commit to a larger build.

Talk through your idea