ICT systems work grounded in long-term operational responsibility
My ICT systems experience has been built over more than eighteen years of practical infrastructure work, much of it in remote, harsh, or low-connectivity environments where reliability was not theoretical. I have supported Linux systems, network services, communications platforms, customer equipment, web and mail infrastructure, cloud-connected services, and secure remote access in settings where distance, weather, limited local resources, and service continuity shaped every technical decision.
I approach ICT systems engineering as a reliability discipline. A working system is not merely a server that boots or a service that responds. It is an environment that can be understood, maintained, secured, documented, recovered, and improved over time. That means thinking through the full lifecycle of an infrastructure stack: deployment, naming, DNS, routing, authentication, certificates, updates, monitoring, backups, documentation, user support, and service recovery.
Good infrastructure should remain understandable when something breaks. I value systems that are observable, recoverable, well documented, secure by design, and practical enough to maintain under real operational pressure.
What I do in ICT systems engineering
Linux infrastructure
Deploying and maintaining Linux servers, command-line administration, service management, permissions, package maintenance, storage layout, logs, firewall considerations, automation habits, and practical recovery workflows.
Network engineering
TCP/IP networking, wired and wireless infrastructure, remote access, VPNs, routing diagnostics, DNS, service naming, connectivity troubleshooting, and performance optimisation across distributed environments.
Web, mail, and communications services
nginx, Apache, TLS certificates, reverse proxies, Postfix/Dovecot-style mail environments, SPF, DKIM, DMARC, PTR alignment, webmail, Matrix, IRC, Nextcloud, Jitsi, and other self-hosted communications platforms.
Infrastructure reliability
Preventative engineering, structured diagnostics, backup awareness, documentation, service recovery, hardening, fault isolation, and designing systems so routine maintenance and unexpected failures can be handled calmly.
Cross-platform support
Supporting Linux, macOS, and Windows users; computer hardware; endpoint devices; local networks; printers and peripherals; application faults; remote support; and customer-facing technical troubleshooting.
Hybrid and remote operations
Supporting cloud-connected and locally hosted services in environments where connectivity constraints, geography, weather, and logistics affect the design and support model.
Knowledge areas that shape my work
Operational environments I understand
My background has included independent ICT practice, telecommunications business ownership, military communications training, veteran service organisation support, self-hosted public infrastructure, and software-backed technical platforms. That range gives me a practical understanding of how ICT systems interact with people, communications networks, regulatory expectations, customer needs, and physical infrastructure.
Independent ICT systems engineering
Delivering end-to-end infrastructure support for commercial and remote clients, including Linux servers, network troubleshooting, secure communications, hardware support, operating systems, documentation, and ongoing service maintenance.
Telecommunications-integrated ICT
Designing and supporting ICT environments connected to satellite systems, PBX/telephony, radio communications, customer networks, remote access, and communications-dependent operations.
Mission-critical technical foundations
U.S. Army Signal Corps training and service introduced structured troubleshooting, electronics diagnostics, Linux-based operational tools, communications reliability, and the responsibility attached to safety-critical systems.
Public-facing infrastructure and platforms
Current systems work includes public web hosting, email infrastructure, Matrix and IRC communications, Nextcloud, Jitsi, Vaultwarden, software distribution pages, exam platform support, and documentation designed for real users.
Why this matters for New Zealand
New Zealand’s geography, rural communities, maritime environment, severe weather exposure, and distributed infrastructure needs reward people who understand more than one layer of the stack. ICT systems do not exist separately from communications networks, power availability, user behaviour, field conditions, or resilience planning.
The value I offer is the ability to connect those layers: Linux systems, networks, communications services, field support, documentation, security, and operational continuity. I have been doing this work long enough to understand that reliable infrastructure is not built from tools alone. It is built from judgement, disciplined troubleshooting, clear documentation, and the ability to keep systems useful when conditions are imperfect.