d3sandoval

I'm going to use this for user interviews since I have a hard time talking too much during the introduction. Also, stand-ups...

We have a PHEV from Chevy (the Volt) and it has the best dashboard ever. Knobs for the stuff you want (A/C, Volume, Skip, etc.) And touchscreen for the stuff you don't (GPS, Apple/Android Auto, etc.)

Just chiming in here as a UX professional to say that design decisions like hiding controls that people obviously need to use the product is 98% of the time a business decision - made by a CEO or anyone far enough away from the product team that they'll disregard any research and overrule the designers because "it just looks better" and their name is on it.

I wholeheartedly agree. Making automatic alt-text available for those types of posts would go a long way in addressing the accessibility issues that plague image posts on Twitter. Their current UX for adding alt-text is painful and content authors are unlikely to use it... Seems like a great place for automation/OCR

The article does not detail steps on how to disable all service workers, though. It only explains how to unregister the existing twitter service workers. I assume twitter goes and re-registers a new one, once you visit twitter.com again.

With the release of WSL2 and the new versions of Docker that take advantage of it, I would say that most of the pain around the WSL toolchain has been resolved.

Compared with trying to get anything working in powershell or dealing with the slowness of git bash or Cygwin, WSL2 is a breeze.

The only pain point I still have is running Linux GUI applications. It requires running an XWindow server on the Windows side and letting WSL talk to it over TCP. Apparently MS is working on that now and hopes to have a solution later this year on the slow ring of windows update. That'll make running things like Cypress a hell of a lot easier and (fingers crossed) prevent me from squinting on HiDPI displays.

Wallabag. It's fantastic and I use it daily!

This is awesome, Tanner! Thanks for writing it.

One thing I think may be missing from this post is examples on what "include design early and often" and "leverage design for more than UI" looks like.

Some examples–like how design artifacts (like service blueprints, context maps and personas) can help non-design team members contextualize their problem and get to actionable solutions earlier–have helped me in the past make the case for involving designers early and often.

I've often seen how centralized design orgs can get caught in the trap of only getting called when there's "there's some UX to wireframe". Getting ahead of this perception early on in establishing a company's software development culture can do wonders for cross-discipline collaboration!