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
That's not true! You can get involved as an individual contributor and become a part of the web standards community. There's even a contribution guide: https://wpc.guide/
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.
For those (like me) who are wondering why their Firefox still looks the same, "If you live in Europe, you’ll find the update available today, August 25, 2020. If you live in the USA, you’ll see the update on the 27th of August, 2020" [1]
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!
This is a great idea but the sentence on the demo / example page really irks me, "cross design off your list and get back to working on the hard stuff"
I think I know what you mean but I can't help but feel like that sentence is denigrating the work of an entire discipline that _also_ works on "hard stuff" like figuring out how to address user need with usable interfaces.
If you really care for each other, they'll find a way. My family has realized that group message are the only way to communicate quickly with one another. I have friends and family with whom I correspond via snail mail. And email bridges the gap between those who prefer digital, but not texting. As others have said, the conversations are more meaningful, even if they are less frequent
You can scroll your thumb along the spacebar to "aim" the cursor on android. I do like the knobs of android better than the zoom-and-select that iPhone does.
Employees create value for the company they work for. If you can demonstrate that you are more valuable than what they're paying you now, then it's a pretty straightforward conversation.
One way to do this is to find out what others will offer you on the market, as others have suggested. Another is to identify how your work pushed company/team/individual metrics in the right direction. Being able to say "My work on [this project] led to a 25% decrease in churn" demonstrates your ability to provide monetary value to the company. If they want to keep making more money, they would be wise to keep you.
Came to this thread to suggest squitch. Glad it's mentioned here. I really enjoy it's three generic concepts - deploy, verify, revert - and not having to tie my migrations to any particular language or ORM. In additon, it's supported on every operating system I've used with it and has got a docker image in case that's not good enough.