And I am not advising younger women (or any woman) to tough it out. You can lash back, which I have done too often and which has rarely served me well. You can quit and look for other jobs, which is sometimes a very good idea. But the prejudice will follow you. What will save you is tacking into the love of the work, into the desire that brought you there in the first place. This creates a suspension of time, opens a spacious room of your own in which you can walk around and consider your response. Staring prejudice in the face imposes a cruel discipline: to structure your anger, to achieve a certain dignity, an angry dignity.
Even talented web developers often are not aware how to correctly code checkboxes and radio buttons in HTML for accessibility. Read the simple way to do it right and the exception to the rule.
Wow. I can’t believe I haven’t been doing this. I want to go through my codebase and rip out groups of checkboxes and do it this way.
The recent release of Firefox 31 brought an implementation of CSS Variables. Based on that, Daniel Imms wrote an interesting post, What CSS Variables Can Do That Preprocessors Can’t, where he investigates a few use cases for native variables over those provided by pre-processors like Sass and LESS (there’s a common argument that CSS variables …
Some UX Lessons - For FREE!
UX Lesson #1: A username is a username, an email address is an email address. An email address is NOT a username. Stop calling it that, retards. If you’re going to use users’ email addresses as logins, stop labeling it “Username”.
UX Lesson #2: On login, tell users which field is incorrect. “That password is incorrect,” or “That username does not exist”. And if the password is incorrect, don’t clear the username field so they have to enter it twice.
UX Lesson #3: If you do one of these, fix it immediately. If you do both of these, punch yourself in the face. And then fix it immediately.
Simplicity is not the goal. It is the by-product of a good idea and modest expectations.