I've spent more than 30 years in professional software and
technology work, solving technical and commercial problems.
Senior development, QA and team management have all shaped how I
approach the work today.
That practical approach began in the 1990s as a CAD technician,
digitising structural and engineering drawings in AutoCAD for
buildings and chemical works, with layers for electrical wiring,
HVAC and other infrastructure. Software was not my main role,
but I helped develop the company's website and automated
business processes, including database-driven telephone
answering and outbound sales calling using modems. Even then, I
looked for ways code could make the surrounding business work
better.
Over roughly two years at an ISP, I progressed from technical
support into network and solutions engineering, followed by
about a year consulting at Unisys. Troubleshooting individual
problems grew into understanding infrastructure, designing
solutions and helping businesses choose how to move forward.
During roughly three years in telecommunications, I developed
internal software used by thousands of employees. The main
application was a CRM-style system supporting upselling and
cross-selling. It also gathered information to inform decisions
about products, pricing, uptake, customer behaviour and
commercial opportunities: software serving both everyday
operations and better business decisions.
Later work in broadcast systems, commercial experimentation and
development leadership built on that foundation. The common
thread has stayed the same: understand the technical and
business problem, then build a practical solution.
Understand the problem first. Then use the simplest
technology that solves it.
Neil Webley.