I am an agile and pragmatic software engineer and technology consultant with a passion for driving innovation and excellence.
My role often transcends traditional boundaries, embodying the essence of an enabling team consultant, tech lead, architect, full stack developer, and QA.
Software engineering is a multifaceted discipline that has to integrate technology, social team dynamics, and business strategy.
This makes software engineering a complex domain and many decisions are tradeoffs.
The only constant is change. Coding agents have moved the bottleneck from writing code to
specifying intent and verifying results —
and as review itself becomes automatable wherever the code is simple and well-tested, the constraint settles back onto intent.
The work shifts from conductor to orchestrator: from pairing in dialogue to dispatching tasks that run autonomously for hours.
-
Technology
-
At the core of software engineering lies a robust set of technical practices encompassing programming, testing, debugging,
and architectural design.
- Clean code
- Test-driven development (TDD)
- Continuous integration and delivery (CI/CD)
- Automated builds
- Domain driven design (DDD)
- Extreme programming (XP)
- Shift security left with threat modeling
- Object-functional programming
-
AI-assisted development
-
Working with coding agents does not remove the need for discipline — it relocates it.
Rigor moves out of the code itself into the specifications, tests, and scaffolding that surround the agents.
The mode shifts from conductor to orchestrator: from pairing in dialogue to dispatching tasks that run autonomously for hours — a double diamond (discover, define, develop, deliver) verified by AI agents, trustworthy only when the specs, the harness, and the QA gates are good enough.
- Spec-driven development (SDD): the specification as the primary artifact, code as a derived one — intent is now the bottleneck
- Engineer for reviewability: simple components and high branch coverage with BDD-style tests, so review can increasingly be automated
- Context engineering: agent-readable conventions, steering files, and living documentation
- AI as adversarial reviewer of requirements, designs, and code — not just as a generator
- Keep humans in the loop where compliance, security, or business risk demands it
- Vibe coding for prototypes and spikes, structured workflows for production
- The durable craft is human: clear communication, abstract thinking, mental modelling
-
Team collaboration
-
The success of software projects often hinges on the dynamics within development teams.
Agile methodologies promote iterative cycles of planning, prioritization, and execution, fostering a collaborative environment where communication and fast feedback is key.
- Pair programming
- Team topologies
- Four key metrics ("Accelerate"/DORA)
-
Operations
-
A strong DevOps culture, which blends development and operational activities, enhances the efficiency and reliability of software by fostering
closer collaboration and integration between teams.
-
The three ways of the DevOps handbook: flow, feedback, continuous learning
-
Architecture
-
A decentralized approach to architectural decision-making is important, to empower teams to make choices based on their specific contexts and challenges.
-
Evolutionary architecture
-
Business alignment
-
The strategic aspect of software engineering involves aligning projects with the organization's broader goals and objectives.
The overarching aim is to ensure that software engineering efforts support the organization's direction and add value.
- Fast feedback, e.g. sprint reviews
- Enterprise Architecture
- Lean thinking
