Louijie Compo
Menu

Whole-system practice

From electronics to software and AI.

I’m Louijie, a systems and AI engineer. My work connects physical devices, software platforms and AI tools. I focus on how the pieces communicate, what can go wrong and how to check that the result works.

System range

System progression: Physical interfaces to Embedded software to Connected platforms to Applied intelligence to Useful outcomes.

  1. Physical interfaces

  2. Embedded software

  3. Connected platforms

  4. Applied intelligence

  5. Useful outcomes

Embedded systems · connected platforms · applied AI

Whole-system practice

A partner across the system

I am a systems and AI engineer with over 14 years of experience working across the boundaries between physical devices, software platforms, and applied intelligence. I turn complex technical landscapes into dependable systems by making interfaces explicit, testing assumptions early, and carrying ideas from architecture into working implementation.

My engineering foundation was formed close to the physical system, where timing, signals, resources, and device behavior make vague assumptions visible quickly. The practice expanded through software interfaces, connected services, automation, and intelligent workflows. That progression created a broad but coherent perspective: each layer matters, yet the quality of the outcome depends on how well the layers agree.

System range

A systems continuum, not a handoff chain

Each layer informs the next. The value comes from carrying context across the continuum instead of optimizing one component in isolation.

  1. 01

    Engineering close to the physical system

    A foundation in electronics, embedded software, timing, signal behavior, and testing against real constraints.

  2. 02

    Building the software bridge

    An expansion into libraries, interfaces, tools, and user-facing software that make complex capabilities accessible.

  3. 03

    Connecting platforms and data

    An extension across services, automation, edge and cloud components, and operational feedback loops.

  4. 04

    Leading through systems thinking

    Architecture, prototyping, technical communication, and mentorship used to align people and technology around dependable outcomes.

System range

Working principles

The aim is not to be the only person who understands the system. It is to help the people around the system reason about it more effectively.
  1. 01

    Understand the whole system

    Start with the real environment, constraints, users, and interfaces before optimizing an isolated component.

  2. 02

    Make interfaces and evidence explicit

    Clarify boundaries, assumptions, data, and success signals so decisions can be tested rather than merely debated.

  3. 03

    Design for real constraints

    Treat timing, resources, maintainability, security, operability, and human context as design inputs from the beginning.

  4. 04

    Leave the system clearer

    Improve not only the implementation, but also the mental model, documentation, tools, and feedback available to the next person.

Explore public work