Did you silence the 'unique key prop' warning with 'index' because it was annoying? That habit is destroying your form data and driving users crazy. I share my debugging nightmare where inputs swapped values and focus jumped around, explaining specificially why 'index' keys are evil in dynamic lists.
Tired of naming classes? Writing CSS directly inside HTML sounds ugly, but it became the world standard. Why?
Class is there, but style is missing? Debugging Tailwind CSS like a detective.
For visually impaired, for keyboard users, and for your future self. Small `alt` tag makes a big difference.
Think Android is easier than iOS? Meet Gradle Hell. Learn to fix minSdkVersion conflicts, Multidex limit errors, Namespace issues in Gradle 8.0, and master dependency analysis with `./gradlew dependencies`.
Install eslint-plugin-react and enable this rule:
"rules": {
"react/no-array-index-key": "warn"
}
This rule will slash red lines whenever you use index as a key.
It does allow it for static lists that never change.
But in my experience, "lists that never change" don't exist. Product Managers always change their minds.
Happy Coding!