Thebe Space

Home

Thebe Space
Decision Advantage for the Warfighter.

Let's build something great together.

Jupiter rotating in space

The Thebe Space Design Process

This is a brief overview of our custom design process, which forms the first part of our SDLC.

BMC3I flyer, back side: the Thebe Space design process from understanding the problem through to human validation

Software for difficult mission problems

You have just seen the process above:

Understand the problem → Model the language → Design the solution → Write the specification → AI implements it → Humans validate the outcome

This page explains who is behind that process, what I do now, and where I am looking to contribute.

About me

Maryanne Lynch
Maryanne Lynch — Sydney, Australia

I am Maryanne Lynch, a lifelong software developer from Australia.

I started programming as a teenager and have worked professionally in software for more than 26 years. I still design systems and write software myself. That is the work I enjoy, and it is where I am most useful.

Today I run Thebe Space, working on software for defence and space systems.

I am based in Sydney and operate through:

  • Thebe Space Pty Ltd in Australia
  • Thebe Space LLC, registered in Colorado

Thebe Space Pty Ltd is an AUKUS registered supplier.

What I do now

I design and build software for complex operational environments.

My work focuses on:

  • mission software
  • distributed systems
  • systems integration
  • service-oriented architecture
  • browser-based applications
  • AI-assisted software engineering
  • 3D visualisation and simulation
  • software for disconnected and air-gapped environments

I work across the full engineering lifecycle: understanding the problem, defining the architecture, specifying the system, implementing the software and validating the result.

I am not just advising from a distance. I still build the systems.

Technical experience

Maryanne's multi-monitor development setup at home
My desk — mission software doesn't get built in isolation.

My main development experience includes:

  • C# and .NET
  • C++
  • TypeScript
  • Unity
  • CUDA
  • 3D development
  • Web technologies
  • Service-oriented architecture

I also have strong experience with the infrastructure around the software, including:

  • Ubuntu
  • Windows Server
  • networking
  • containers
  • virtualisation
  • identity
  • secure communications
  • on-premise systems
  • private cloud
  • disconnected systems
  • air-gapped deployments

That matters because operational software does not exist in isolation. It has to work across real networks, real infrastructure and real organisational boundaries.

Why I work this way

AI can generate code quickly, but speed is not the same as understanding.

The important work still happens before implementation:

  • defining the real problem
  • using the correct domain language
  • separating concepts clearly
  • designing the system boundaries
  • writing a specification that removes guesswork

Once that work is done, AI becomes very useful.

It can accelerate implementation, testing and repetitive engineering tasks. Human judgement remains responsible for the problem, the design and the outcome.

That is the method shown above.

Current focus

My current work is centred on defence and space.

I am interested in:

  • Battle Management
  • Command and Control
  • Space Domain Awareness
  • distributed operations
  • degraded and disconnected environments
  • mission integration
  • interoperability
  • operator decision support
  • AI-assisted engineering

I am also developing the Thebe Domain Framework, a browser-first foundation for applications that need to operate across cloud, on-premise, sovereign, disconnected and mixed environments.

The goal is not to replace every existing system.

The goal is to help existing systems, people and information work together more effectively.

Why I am here

I am in Colorado Springs to meet the people working on real Space Force mission problems.

I want to understand:

  • what is not working
  • where systems do not connect
  • where operators carry unnecessary cognitive load
  • where software is too difficult to change
  • where a new approach could make a practical difference

I am looking for technical conversations, mission problems and opportunities to contribute.

Let’s talk

If you are working on mission software, distributed systems, interoperability, BMC3I, Space Domain Awareness or AI-assisted engineering, come and find me.

I am Maryanne Lynch. I am a developer, an architect and a builder.

Contact

Bottom drawer

Placeholder drawer content for supplementary page actions, contextual details, or future interactive regions.