Definitely, although I don't have much experience in this area.

Container queries is the big one for me, since responsive design in its current form effectively clashes with the component-scoped CSS model. I also wish we could get a greater focus on local scoping. For example, while we now have variables, they all exist in a shared global scope. Apart from that, I'm finding that the more I properly leverage the component model, the less I rely on preprocessors. For anything that's left over, I actually think CSS-in-JS is preferable to preprocessors, so I'd be interested to see how browser vendors can better enable this approach.

This is a really interesting question, and I'm definitely not going to do it justice in this forum. I definitely feel myself becoming focused on higher level problems over time. I find that staying relatively close to the code helps keep my feet on the ground, and so far I'm planning to maintain this balance. Whether this trajectory leads me towards more leadership roles or even going off on my own, we'll have to wait and see.

Thank you! 😄 It doesn't do cross-platform styling well (React Native, React Sketchapp) compared to CSS-in-JS. It also forces all of your CSS to be static, which I think is often a good thing, but it occasionally gets in the way when trying to build low-level reusable components—having to generate the CSS for all potential consumer states ahead of time is less than ideal. For a lot of projects, though, these are very minor points, especially since this is also true of all traditional CSS approaches.

Cats—they fit much more easily into a life spent in front of screens 😄

I know about it, but I've never used it personally. I think it's a really, really interesting idea, but I find the interface a bit too awkward for my tastes.

Mentoring is very important, but I think it's best coupled to an open source workflow that forces you out of your bubble. You can learn very effectively by looking at other projects online and then creating your own. With package managers like npm, you can easily create and publish tiny utilities, whether they're standalone libraries or plugins, and share them with the world, get feedback and iterate. In some sense, this is just an open, asynchronous form of mentoring, and one that works surprisingly well.

Already answered this one :) https://hashnode.com/ama/with-mark-dalgleish-cj6feo72s00ltb2wtdvjaj8xt#cj6mlki36008p1uwtpqrueqhj

In terms of design on the web, I find the majority of it centres around typography. If you can make a page look good with black text on a white background, you're most of the way to being a strong web designer. Read books, look at typographical hierarchy libraries, read their source code, experiment. Most importantly, keep your eyes open! You're looking at web typography on a daily basis, so pay attention to it. Whenever you see typography that you like, try to deconstruct it. What do you like about it? Why does it work? How could you break it, and why? Feed this back into your experimentation. Do this for long enough and you'll find your design skills naturally improving.

To me, they're the perfect sign of why React (or at least, the React model) is here to stay, and why there's still so much we can do with it. Love the work you're doing in this space 👏👏👏