Skill 04
Automation & enterprise packaging
Build recurring work properly once – and never do it by hand again.
In larger IT departments, rollouts and operations tasks run through orchestration platforms and software packages. I know both sides: building flows and packages, and the tooling around them that is missing when a review shows nothing but thousands of lines of XML.
The same principle applies on a small scale: the annual accounts of a small company or importing bank statements is manual work that a script does more reliably – as long as it states its assumptions and cross-checks its results.
What I do
- Developing and reviewing flows for OpenText Operations Orchestration
- Analysing and building MSI, WiX and InstallShield packages
- Windows administration and PowerShell scripting
- Developer tools: VS Code extensions, CLI tools
- Automating accounting and tax processes
Tech stack
| Layer | Technology | Why |
|---|---|---|
| Orchestration | OpenText Operations Orchestration | operations processes as versioned flows |
| Packaging | MSI, WiX Burn, InstallShield, Inno Setup | rollouts without surprises |
| Windows | PowerShell, Active Directory, GPO | standardisation across the corporate network |
| Tooling | TypeScript, VS Code Extension API, Python | tools where the work happens |
| Finance | XBRL, ERiC SDK (ELSTER) | officially validated output instead of retyping forms |
Related projects
Planning something similar?
Tell me by email what you have in mind. The first conversation is free.