Nyle Connolly

Lead Web Engineer at asos.com. Specialising in building modern, user-friendly, performant and scalable Web experiences.
Canvas is not supported!




I started writing JavaScript professionally in 2014, starting with jQuery and then venturing into "vanilla" JavaScript (once I finally got my head around what var that = this was all about). Since then, my love for programming grew almost as fast the number of JavaScript frameworks in the NPM registry.

After spending a few years working with various JavaScript tools and frameworks, my current stack of choice comprises React & Redux, Webpack, Node & Express and all the other bells and whistles that go with them.

I'm a firm believer in always ensuring my JavaScript skills remain grounded by regularly participating in, and leading, TDD-based code craftmanship sessions.

React & Redux


I've been using React since around version 0.13.0, it's been a reliable tool to have at my disposal and is still my framework of choice.

Whenever I do opt to use React in a project, I tend to use it both server-side and client-side along-side a Node server.



In recent years I've been working a lot more with Node & Express for building server-side applications in the form of Web servers and APIs.

These have been deployed to IaaS & PaaS services on Azure and Heroku.

Through building Node applications, I've gained a lot of experience in building scalable, performant and secure server-side applications.



I've been working in Azure since 2017, and have undertaken a number of Microsoft certifications to ensure my knowledge and experience is always up-to-date.

My experience in Azure spans creating and maintaining everything from IaaS Cloud Services through to PaaS Serverless Functions, and everything in between.



The first thing anybody learns when wanting to build a website, this is where I first started in 2012 and I'm still learning new things today! Particularly in the world of the WCAG AA and AAA Accessibility standards.



The second thing anybody learns when building websites, I've been working with CSS since 2012. I've experienced everything from writing CSS that supports IE7, through the modern pre- and post- processors that came along with Grunt and Gulp builds, and now to CSS Modules we use today for component-based workflows.



A topic that has gained a lot of traction in recent years is accessibility on the Web. Accessibility is incredibly important, especially as we become increasingly reliant on the Internet, and it's important to ensure that we do everything we can to give all of our users the best experience we can. As a result, I've gained a fair amount of experience in building and testing AA and AAA WCAG standard websites.

For me, the first step in building accessible Web applications, is focussing on building simple,semantic and logical markup. This makes accessibility a great exercise for validating your markup.

Platform Engineering


In recent years I've been focussing a lot of effort into broadening my Platform Engineering skills. A key part of every development lifecycle is ensuring that an application can reach its intended audience as quickly as possible, whilst also running through enough automated and manual test scenarios that you have confidence the application is going to run as expected. My current toolkit consists of TeamCity, Octopus Deploy, Azure Powershell, Azure CLI, ARM Templates, Bash, and a little SQL admin.