Fully committed · Contact me

Hi 3NNE, what are we building today? Full-Stack Software, Industrial IoT, Edge Systems, Cloud Platforms, Secure Systems, Data & AI, Automation, Interfaces.

Sense.Protect.Build.Think.

Independent engineering for systems that run in the real world.

Be strong and courageous. Do not be afraid.

Joshua 1:9 (NIV)

[ Method ] Operating cycle

Listen first.
Then build.

Every good system starts the same way the device does: by listening to its surroundings.

01 / LISTEN

Listen to what is actually being said.

Before any line of code: conversations, site visits, logs and data. Requirements are signals. A few are loud, most are faint, and I take the time to capture all of them, including the ones nobody thought were relevant.

02 / UNDERSTAND

Find the need behind the request.

What is asked is rarely all that is needed. I take a census of everything I heard: regulations, technical limits, deadlines, workflows, budgets and real needs. What doesn’t hold up is dropped. What is left is the need behind the request.

03 / ANTICIPATE

Design for what comes next.

Systems outlive the brief. This is where the latent needs surface: the evolutions, the integrations and the opportunities nobody wrote down, but the next version will ask for. I design for them now, so that today’s solution doesn’t become tomorrow’s constraint.

04 / DETECT

Catch the problem before it is one.

Threats, failure modes, weak spots, metrics quietly drifting. Spotting them early, in code, in networks or in machines, costs less than any fix that comes after.

[ Build ] From thought to machine

Then the idea
takes shape.

Everything I deliver starts as a conversation and ends as something you can switch on, measure and trust.

[ Inside every project ]

  1. 01Every project is a stack.Not of chips. Of people, goals, constraints and habits, each one resting on the one below.
  2. 02Signals at the bottom. Decisions at the top.Down there, what really happens every day. Up here, the choices that depend on it.
  3. 03Everything in between has to hold.Processes, tools, rules and data. When one layer is weak, every layer above it feels it.
  4. 04I work across all of it.From the first conversation to the thing you switch on. Technology is the means, never the point.

[ Layers ] What I work on

Four layers.
One engineer.

[01] SENSE

Industrial software & IoT

Machines talk. I listen.

Data acquisition at the edge, condition monitoring and diagnostics for industrial assets, field-bus and protocol integration. Software that lives next to the machine and survives the plant floor.

  • Condition monitoring
  • Edge devices
  • OPC UA
  • Modbus
  • IO-LINK
  • MQTT

Part · Piezo element · acquisition ring

[02] PROTECT

Cybersecurity

Trust is a design constraint.

Threat modelling, secure architecture, hardening and assessments, from firmware to cloud, IT and OT. Security designed in from the first layer, not bolted on at the end.

  • Threat modelling
  • OT / ICS security
  • Hardening
  • Assessments
  • IEC 62443
  • Secure SDLC

Part · Secure element · guard rings

[03] BUILD

Software, web & apps

Software that ships, and stays up.

Desktop applications, web platforms, APIs and integrations, engineered for long lifecycles, real users and the people who will maintain them after me.

  • Desktop apps
  • Web platforms
  • APIs
  • Integrations
  • Cloud
  • CI/CD

Part · MCU · main board

[04] THINK

Data & AI

From raw signal to decision.

Signal processing, analytics pipelines and machine learning that turn measurements into answers people can act on, and explain why.

  • Signal processing
  • Anomaly detection
  • Time series
  • ML pipelines
  • LLM tooling
  • Dashboards

Part · Neural accelerator · memory bus

[ Handshake ] Contact

Open a channel.

A machine that should talk. A system that should be trusted. Software that should ship. Data that should answer. Tell me what you are seeing. I'll listen first.

HANDSHAKE…