No i18n is probably fatal for an international company. Americans get confused by ddmmyyyy and all other people get confused by mmddyyyy. If you write 1/7/2026 the Americans show up in January and all other people in July. Translations might be optional, but not dates/numbers.

Agreed, not saying they're not important. I'm saying they're not often given the time of day in terms of sprint prioritization planning

How is testing a nice to have 😅 I feel like I work in a different profession sometimes

These are not from a technical perspective, these are from a non-technical business perspective. If you try to articulate the value of a test to biz folks it quickly becomes visible that for many in the non-technical space it's a "nice to have"

This chart is the primary center around the Frontend developer, I wonder how it looks for backend engineer's

I’d also add handling empty states to the list. A big plus would be to also add an action what to do when a in an empty state (if it makes sense)

Could you do more of these? They are fun

Light/dark mode is my top priority always. Then I won't go blind while developing the rest of the app

Would actually move i18n all the way to the polish side of the spectrum. Most startups are not launching globally, so wasting time on i18n when you haven’t even found PMF is a great way to kill your own velocity.

Tech convos on this platform drastically over-optimize on the smallest of startups.