Best described as a punk dad of two, Nicolas’s love for all things web began in 1998 when the Web gave him the power to post pictures of cute cats and promote his musical quintet.
A software engineering graduate and ex-TA of ÉTS Montréal, Nicolas has been a partner and the CTO of Deux Huit Huit since 2011. Cumulating more than 20 years as a professional developer, he oversees the design company’s technological innovations, DevOps, and quality of technological development.
Through methods rooted in performance, accessibility, usability, and digital security, he collaborates closely with the agency’s entire team. This results in the recognized Deux Huit Huit signature of flawless and performing programming — where fluidity meets performance and durability.
Tailwind is ubiquitous: its ease of use and speed make it an easy choice for dev teams that embrace the “atomic” CSS mindset. Tailwind JIT engine also generates only the required CSS class based on its tokenization of the provided source files.
One problem many devs encounter with Tailwind is that class names MUST be tokenizeable, i.e., they need to be identifiable in the source code whole. You can not use string concatenation or interpolation to create class names or pass theme values as parameters. These constraints lead to code repetition and harder-to-read code, which violates many software design patterns (the open-closed principle being one of them).
At Deux Huit Huit, we had a silly idea: What if Tailwind could understand our svelte and typescript code? What is required to design and implement such a system?