What to put in a README
How to minimally document software - 23, March, 2021
Allow varied national telephone number formats
Why telephone numbers don’t add up - 23, February, 2021
Respect people’s full names
Don’t call someone’s name ‘invalid’ - 16, February, 2021
Forgive user input in the wrong format
Don’t make people normalise data manually - 2, February, 2021
Omit salutations in automated notifications
Don’t waste time on fake greetings - 26, January, 2021
Build unisex software
Don’t ask people to tell you their gender - 13, January, 2021
Implement a zero-bug policy
How to manage bugs during software product development - 5, January, 2021
Validate email addresses to level 4
First person to say ‘regex’ loses - 1, December, 2020
Allow all printable characters
First person to say ‘special characters’ loses - 17, November, 2020
Use localised language names for language selection
Don’t use flags for languages - 3, November, 2020
Sort every collection you display
Unsorted is never the right order - 20, October, 2020
Numbers that aren’t numbers
‘Numbers’ that you can’t represent numerically - 29, September, 2020
Software review: Shipright
A single source of truth for your customers’ product feedback - 1, July, 2020
Software review: Delibr
Structured writing for feature documents - 19, May, 2020
Software review: productboard (roadmaps)
Sharing product roadmaps in @productboard - 7, April, 2020
Software review: productboard (insights board)
Capturing customer feedback in @productboard - 31, March, 2020
Software review: productboard (features board)
Managing a product backlog in @productboard - 25, March, 2020