Y encima de todo, representación femenina en el equipo locutor y en la selección de entrevistas. Que buena vibra! Excelente proyecto!

Haha slow clap that's fun :) Gotta play around with the z-index next, and make the bounding box squares transparent

Gotta say... I'm really digging this custom cursor

Relevant story...

A year ago I faced a huge career dilemma as a designer when I quit my job at a small software shop (we built sites and apps for clients). Over there I really enjoyed writing CSS w/Sass — huge fan of OOCSS/SMACSS/BEM, and democratizing and documenting the CSS code I was writing (design systems, FTW), but I really didn't enjoy doing any JS related implementation. We were all over Angular back then and I was seriously not interested.

I wasn't sure what I was. All the positions I stumble upon for front-enders talked about being responsible for building applications using MVC based frameworks and whatnot. That wasn't me. I loved designing experiences, but I also enjoyed a small piece of the building part (the html/css part). Yet, I couldn't find a position that described my mixed set of skills… so I panicked about my future.

It also hurt my confidence. When I measured myself against the requirements for these front-end positions, I felt like an amateurish developer. And when I looked at designer positions, I didn't have the case-study type of portfolio that would show I had a solid design process, so again I looked unskilled.

So, I decided to stop being in the middle of the spectrum (designer vs front-ender) and chose a side. I'm now focused on design (research, testing, visual design) and don't really do coding for work, only for personal stuff.

TL;DR... I don't think the industry has decided on who's job it is to care for CSS architecture in a product, so job posts aren't clear about it. Consequently, job seekers get the impression that there's no demand for this mixed set of skills and that might be causing a "drought".

This is great. I really wish I had heard about it sooner.