Software developer · product engineer
Servicesa defined path to a verifiable outcome.
Bounded analysis, development and end-to-end delivery paths for applications, automation and connected systems, with explicit scope and verification criteria.
Approach
Start with the problem and how much is already known
I design applications, automation and connected systems for professionals, businesses, startups and technical teams. The work may stop at the software layer or extend into backend services, Linux infrastructure, edge systems and devices when the problem requires it.
Not every need should begin as a full project. When the problem or architecture is still unclear, the decisions can be bounded first; when the technical objective is already defined, implementation can start directly; when one owner is needed across the whole result, the path can cover the system end to end.
After delivery, support, maintenance, operational monitoring and further evolution can be agreed as recurring work only when scope, responsibilities and verification methods are explicit.
Software, data and workflows
Web/desktop applications, backend services, APIs, automation and integrations for digitising processes, coordinating data or evolving an existing product.
Edge, devices and infrastructure
Linux, telemetry, protocols, devices and operational runtimes when software must interact with networks, machines or the physical world.
Engagement modes
Three ways to start without selling disconnected hours
The right mode depends on how defined the problem is and how broad the required responsibility needs to be. Each path is bounded by outputs and verification criteria before work begins.
Analysis / Architecture Sprint
For turning a need, an existing system or an ambiguous product idea into usable technical decisions before committing to implementation.
Development Sprint
For implementing a sufficiently defined technical objective within a bounded scope and ending with a result that can be verified.
End-to-end project
For owning a broader outcome through one coordinated path, from initial analysis to deployment, verification and operational handover.
Distinctive experience
Software, edge and operational infrastructure
Direct experience integrating applications, devices, telemetry, Linux, networks and services used in real environments, including energy and remote-control systems. That technical depth remains available inside all three engagement modes without turning the stack itself into the product being sold.
Working method
Six stages with clear outcomes and decisions
The path is adapted to the project while keeping scope, risks, trade-offs and outcomes explicit and verifiable. A Sprint may cover only part of these stages; an end-to-end project coordinates all of them.
- 01
Analysis
Problem, users, constraints, risks and expected outcome.
- 02
Proposal
Engagement mode, scope, priorities, activities, timing and verification criteria.
- 03
Design
Workflows, data, interfaces, integrations and solution architecture.
- 04
Development
Implementation in stages with shared progress and decisions.
- 05
Testing
Verification of workflows, failures, recovery and behaviour in the real operating context.
- 06
Delivery and evolution
Deployment and documentation; support, maintenance, monitoring or later improvements are scoped separately when useful.
New project
Send a brief — you do not need to have every answer yet
Describe the current situation, expected outcome and main constraint. You can select the engagement mode you have in mind or let the first review identify the most sensible starting point.
Specialist areas
Go deeper where software meets operations
These pages focus on areas where there is already public engineering evidence. They complement the engagement model above rather than replacing it.
IoT and edge software
Data acquisition, Linux edge runtimes, device protocols, local persistence, APIs and operational reliability close to the physical system.
Explore this areaMonitoring dashboards
Telemetry, time-series views, operational dashboards, alerts and interfaces that turn measurements into understandable system state.
Explore this areaAutomation and API integrations
Reliable automation, backend contracts and integrations that remove manual transitions and connect existing software boundaries.
Explore this area