qkeast

The use of urgency here is absolutely a manipulative pattern designed to influence user behaviour for the benefit of the manipulator.

I was eligible for cochlear implants probably more than 15 years ago, but I was getting by, and I heard that getting implants would almost certainly preclude any future therapy like this. I'm ecstatic to finally hear an actual "it worked, in a human" outcome, and can't wait for something that works for my hearing to reach maturity.

Tangential, but I’ve been feeling similarly with startups and tech companies: design needs to be represented at the leadership alongside engineering and product, or it simply is not viewed as an equal strategic function. If there’s a Head of Engineering and a Head of Product, there needs to be a Head of Design to complete the triad.

I'm curious, though: what gives you the impression that the person writing the article "seems to have a very cursory understanding of design systems & component libraries?"

Edit—Responding to an edit in the OP:

>I like working with UX and designers, but more often than not, "we need a new design system" basically means "we want a cool, new theme"

This isn't so much an issue with UX and designers as a discipline, but rather points at larger issues in the organization around process, culture, expectations, and strategy, the perceived role of design in that organizational context, and the specific folks you've worked with.

Thanks for sharing!

I’ve mostly been reading fiction this year. On reflection, I think my favourite book of 2023 was “The Adventures of Amina Al-Sirafi” by Shannon Chakraborty. The “Wool” series by Hugh Howey was also a highlight.

As someone who’s profoundly deaf myself, another less technical approach is to install Rogue Amoeba’s Loopback, and use it to pipe audio from a given app into a tool like Google Meet or Otter.ai using the Loopback device as the audio source. This effectively provides real time captions for anything running on your existing machine.

It gives us great signals into the things we care about in designers: communication skills, design and product thinking, their mindsets and approaches to thinking about and evaluating products and design, and even their craft.

The interviewer could easily craft this question in any number of ways that creates space for the candidate based on what signals they're looking for. And it should be on the interviewer to get this right, not the candidate to interpret it as intended.

Of course, it could also be that the interviewer's looking for signals around how the candidate approaches being placed on the defensive and belittled; but hopefully the candidate will recognize that signal for what it is. Why would a candidate want to work in a place where they'll be expected to be on the defensive and belittled, to the point where it's highlighted in the interview process?

I write about product design, UX, and related topics as they come to mind from the perspective of a product designer.

1. Customise our starting point with the file of your choice: https://docs.sourcegraph.com/code_monitoring/how-tos/startin...

2. Create a new code monitor at https://sourcegraph.com/code-monitoring

Whenever the file changes, you’ll get an email notification.

I've been doing this for more than 10 years and it's the first tool that achieves the same exploratory and collaborative outcomes as an actual whiteboard.

I'm a happy monthly contributor!