I was talking to a junior dev the other week. I kept asking them to remove this duplicate status in one part of the app, and the dev kept sending the app back to me with the same duplicate in place – frustrating! We talked about it, and the dev explained their plan to fix the issue, once and for all.
I asked: “why wrap this div in a conditional render, instead of getting rid of it? To clarify, there is a second div, with class flex items-center space-x-2, that also displays the status, that works just fine and I’d like to keep.”
The dev explained “The reason for conditionally rendering the div with the class inline-flex items-center px-2 py-1 rounded-full text-xs font-medium (which I’ll refer to as the “status badge”) instead of removing it entirely is to maintain its utility when a task is completed.”
I said “Let’s just get rid of the ‘status’ idea” and finally, the problem was solved!
At around the same time, I was working with a junior designer. When I suggested we try a change in design – from boring blue-on-white to green-on-black – there were a LOT of accessibility problems at first! And too many of the calls-to-action were primary. But after some additional feedback, they got their act together, and it’s looking pretty good now.
Continue reading
