See Linux Notes.md
Installed at: /var/www/wordpress/
function restroomEtiquette(you, restroom) { | |
while (true) { | |
if (you.needToGo === 1) { | |
if (you.okayWithUrinals && restroom.urinalAvailable()) { | |
var urinal = restroom.occupyAvailableUrinal(you); | |
you.evacuate(urinal); | |
urinal.flush(); |
See Linux Notes.md
Installed at: /var/www/wordpress/
Screen width/size: Just because my viewport is 960px wide, doesn't mean I'm on an iPad, tablet, etc. My desktop, as well as the majority of laptops today, are 1920px wide. 1920 / 2 = 960, which fits two browser windows, side by side, very nicely. I hate having to use hamburger/hotdog menus, when "normal" navigation would work just fine on both mobile & desktop. Lets not handicap users, just because we make assumptions about the device they are on.
Device agnostic: Rather than mobile vs desktop, it's becoming a point that we need to design for The Web, not devices. The Web is not just phones, tablets, and desktops. It's also screen readers, TVs, embedded devices, etc. Also, we don't know what's coming next.
Input types: There are a variety of devices today that support a variety of inputs. With just these three input types -- touch, mouse, keyboard -- we need to account for 27 different input combinations. And there may be others we haven't accounted for. My little Andriod phone supp
Notes and guide to Accessibility techniques.
eg. With simulated state/input, call one method. Compare result with expectation.
Ensures the method does what the programmer expects