Project notes and static-site work
Web applications, public source archive projects, portfolio pages, structured data, metadata, and technical SEO foundations.
Christchurch, New Zealand
Software developer and tech consultant working on practical web tools, SME systems, technical SEO, automation, project notes, and source archive work.
Current work
John Finnerty is based in Christchurch and works across software development, websites, business email, DNS, networking, technical documentation, and support workflows for small teams. The focus is simple: useful systems that are understandable, maintainable, and easy for real people to operate.
Web applications, public source archive projects, portfolio pages, structured data, metadata, and technical SEO foundations.
Email, Microsoft 365, VoIP, DNS, domains, fibre troubleshooting, networking basics, handover notes, and support documentation.
Repeatable checks, data quality, documentation, browser diagnostics, support trails, and practical automation for common tasks.
Selected work
These project notes are useful reference points for John's current technical work. They are presented conservatively: no audience numbers, client outcomes, or formal credentials are claimed unless evidence is available.
Low-barrier support discovery for people in New Zealand.
Early-stage mobile-first cooking and meal-planning prototype.
Independent New Zealand radio directory experiment with broadcaster links and stream-health notes.
Private C++ and Qt SDR desktop prototype for spectrum UI and receiver workflow experiments.
Independent public-interest archive with source, methodology, and publication-caution pages.
Private Android prototype exploring low-friction personal check-ins and careful interface wording.
Technical strengths
The current evidence base supports a profile centred on web development, structured data, technical SEO, support systems, SME infrastructure, and project documentation.
Working style
The common thread is practical problem solving: make the system understandable, document what changed, validate the result, and leave the next person with a cleaner path forward.
Useful technical help should make decisions easier, not hide behind jargon.
Pages need accurate metadata, schema, canonical URLs, and internal links to support discovery.
Good notes, repeatable checks, and rollback paths reduce stress when something changes later.
Practical support paths
These pages translate the professional profile into practical support areas for websites, DNS, email, networking, fibre, VoIP, and SME technology setup.
Profile links
These links help connect the professional site, personal identity hub, project notes, and third-party profile references.
Need help with a practical tech problem?