1,333 karma · joined October 20, 2011
Some of the most effective solutions to this I've seen require solutions beyond visual representation. They address the problem through dimensions independent of viewport size and space.
For example, LukeW's "Don't Divert the Train" http://www.lukew.com/ff/entry.asp?1798 moves content from behind navigation and into the user's already-occurring action stream. The button is removed entirely, as is the designer's need to consider how communicative icons are for representing actions.
This requires a broader view of how features relate to each other through a design process that discovers other paths to successful behavior. Approaches like the hamburger menu, in addition to the usability issues you note, solve functional goals but have fallen out of vogue for their ineffectiveness at encouraging specific actions. Label-less icons, while attractive and convenient, suffer similar problems. As getting users successful quickly is generally an important goal (before they've internalized your app's unique visual language), the current trend of putting core functionality behind opaque symbols seems counterproductive.
From my normal user perspective (not advertising, not a celebrity...) they've never been an internally innovative company - @mentions and retweets are community inventions, the best clients for niche, power, and general use have always been 3rd party, and after stumbling onto a private messaging hit they shot DMs behind the woodshed just before the world went wild for whatsapp and snapchat. The community continues to come up with interesting ideas, never to be implemented. There's no doubt Twitter has stellar engineers. It's strategy that needs to be externalized. A shame they've spoiled so many developer relationships.
I don't remember much about the plot, but can't ever forget that VR. <curmudgeon>The trends in "expressive" animated interface design make me think that dystopian future is still an aspiration for some designers. Just as soon as we all get headsets...</curmudgeon>
Conference organizers should probably keep things like this in mind when booking male-dominated lineups ("we just can't find any woman engineers" is a common refrain).
But hey, good luck drawing lines where you choose.
An integer point difference on a single play is huge.
Is Facebook uniquely untrustworthy in this category? Is there anything about Gyroscope that makes it uniquely trustworthy, if only they gathered your data directly?
The character's name is "John, The Carpenter".
bob plissken - http://en.wikipedia.org/wiki/Snake_Plissken the thing - http://www.imdb.com/title/tt0084787/ escape from new york - http://www.imdb.com/title/tt0082340/ they live - http://www.imdb.com/title/tt0096256/
FWIW, I don't get the connection to javascript interviews either.
If my phone is in my pocket (it will be) this takes longer and involves much more juggling than typing in the computer's password directly.
What are the others?
I wonder if NY Times is using this 3D map of El Capitan? http://news.nationalgeographic.com/news/2013/06/130612-yosem...
http://updates.html5rocks.com/2013/12/300ms-tap-delay-gone-a...
There are a number of plugins to remove the 300ms delay from other touch browsers. Here's one: https://github.com/ftlabs/fastclick
Fortunately, #2 can be resolved easily by setting input,textarea{font-size:16px}. There are problems with 16px for all inputs (especially if using a custom font with different metrics than the default), but it preserves a significant usability feature. A fair trade, even if it means using system default inside of inputs.
Regarding blurry images, I favor suboptimal delivery of content over failure to deliver every time.
Great work on the framework, keep it up!
I'm not the article author or site creator, I'm just OCD about the myriad ways a seemingly simple page can fail to render.
If your intention was to be helpful in any way (always a safe assumption with username223), you could have at least said what browser you use.
Because CSS rules are applied by specificity (http://specificity.keegan.st/) first and source order second, any property overwrites later in the document require equal or greater specificity than rules in the middle. A chart with a mountain in the middle today will probably develop more mountains on the right over time - it's a leading indicator of poor maintainability. Pairing this tool with one that tells you the line number of offenders would help in identifying areas in need of refactor.
Total vs Unique declarations reveals opportunities for reusable OOCSS-type classes (which itself can be difficult to do in a stylesheet full of specificity mountains).
The colors aren't terribly useful without a histogram and some of the other stats do seem a bit superfluous, but they may just need someone more experienced than I to draw the right conclusions.
Even lacking missing those features, the 12x compilation speed improvement in libsass is pretty compelling.
https://www.google.com/search?q=how%20much%20does%20a%20cubi...
I've made quick pushes via web IDE on my phone while commuting. I doubt improved tooling would increase frequency, but it would certainly increase the complexity I'd be capable of and my confidence in not pushing janky brokenness.
Salt Lake City recognized the total cost of a large homeless population was significantly higher than building permanent homes paired with services to accommodate them. Reducing the chronic homeless population increases capacity of emergency services, saves the community money, improves quality of life for both homeless and those living/working in an area with a large homeless population, and creates a setting where support services (health, wellness, education...) can be more efficiently and effectively provided.
The 2013 report goes into detail: http://jobs.utah.gov/housing/documents/homelessness2013.pdf
Some highlights:
Salt Lake City has 779 permanent housing units for supporting chronically homeless. On a random night's count, 87% of the homeless population was sheltered.
Chronic homelessness decreased 9% from 2012-2013, and has decreased 74% since program start in 2005.
2005 - average annual cost for emergency services and jail time for each chronically homeless person was $16,670. The cost to house them and provide case management services was $11,000 per person.
Over half of those housed by the program moved on to permanent destinations. Only 8% returned to homelessness.