I have opinions about good and bad when it comes to UI and UX. Some of these are hills I could die on.

Row numbers for list items

When you have a list, table, log or similar, where you display items that you can scroll through, one of the most important things is to have row numbers.

If you have more than a couple of items, I would argue that row numbers need to be mandatory, so the readers get some feeling about the ordering of the items.

If you share these lists, tables, logs with others, for example, in a shared digital meeting, it will be almost impossible for all other participants to follow you when scrolling if you don't have row numbers. It will also be cumbersome to unambiguously refer to any of the items. Much unnecessary time is spent trying to understand each other.

It is not enough with random unique identifiers for each item. You can have such identifiers also, but you really need separate consecutive row numbers in the list.

Note: Example of using row numbers in tables.

Date range pickers

The vast majority of solutions I have seen are not what I would define as good user experiences. I have written a lot about and created a proof-of-concept web component for picking date ranges.

BGIOSZ

When you can choose on your own, if you want to use digits or alphabetic characters in your passwords/tokens/UUIDs, there are no problems.

But when you receive an automatically generated password/token/UUID and these contain any of the uppercase alphabetic characters BGIOSZ or any of the digits 861052, it may be really hard to distinguish these if you see them in a small or bad font.

Note: You often see examples on router labels with minimal font sizes.

So, if you have the possibility, think before using BGIOSZ and 861052 in passwords/tokens/UUIDs. Your users will thank you.