About this chap called Chris Gibbons

What I do

  • Enable better conversations between design and dev
  • Design systems
  • Web Standards
  • Accessibility
  • HTML
  • CSS (Sass)
  • Responsive & Mobile-first
  • UI/UX
  • JavaScript

What I don’t do

  • Backend development
  • Heavy JavaScript
  • OOP
  • Fix printers (or other bits of IT equipment)

A potted history

Chris Gibbons is an experienced and passionate digital developer specialising in the “lost art” of traditional front-end development practises, UI/UX and mobile, with a long time obsession for well written, semantic & accessible code to help deliver cross-device, compliant, usable websites which are accessible & inclusive.

He sits somewhere in the murky waters between design, front-end & engineering. Strongly advocates for the use of design systems and spends large parts of his time rambling on about the use of “proper semantics” and shouting at clouds, all to help make the web a far more accessible and inclusive place, for everyone.

He also hates speaking about himself in the third person, so lets stop.

After working with the amazing folk at Code Computerlove for nearly 8 years, working my way up to Snr. Front End developer, I then spent the next 12 months working as UI engineer at Zuto where I enjoyed the challenge of trying to build a bridge between front-end and UX in the world of car finance.

Happily employed by the nice folk at Auto Trader for 4 years as a Principal UX/UI developer and an advocate of accessibility & inclusive design. Next up was a good stint as lead Front-end engineer with the lovely folks at Co-op, where I helped to shape the future of the design system and other products for our colleages.

Now building on my many years in Front-end, I’m enjoying life at cinch as a Principal practice engineer looking primarily at Front end and accessibility.

Outside of work I live close to the seaside resort of Blackpool and, in my small amount of spare time, like to take photographs — Instagram — bake cakes and support Liverpool FC.

UX Technologist?

A UX what now?

OK, let me explain.

I’ve been trying to find an accurate description for myself within the front end (FE) arena for a number years now, especially with the lines of what is expected of a FE-er becoming blurrier.

It’s no exaggeration to say that the FE landscape has changed dramatically in the 15 years I’ve been in the industry.Task runners such as Grunt and Gulp weren’t even twinkles in the eyes of the people who concieved the ideas. Object orientated approaches to frameworks such as Angular and React are commonplace and expected skills to have. Accessibility & inclusive design is rightly gaining in prominence, but not enough for my liking!

Now the parts of FE I particularly enjoy is around the UI layer and the crafting of a great experience, this along side prototyping & discovery (mainly as I get to play)

In my opinion--and after doing a few Google searches it seems there are many other people thinking the same--a UX technologist works to bridge the gap between design and engineering.

One of the best posts I read on this topic is from Dan Harrelson at Adaptive Path.

  • A comfort level with front-end programming (web, desktop, mobile, device)
  • A tool belt filled with techniques for creating interactive apps
  • The ability to quickly pick up new tools
  • A itch to dive into code and “just built it”

These all appear to reflect where I feel I add most value.

But it was the following:

You also need to find that special someone who appreciates design and wants to be a member of the UX team.

That really sums up my current feelings to FE and my position.