- Militarizing Your Backyard With Python and Computer Vision (video) — using a water cannon, computer video, Arduino, and Python to keep marauding squirrel hordes under control. See the finished result for Yakkity Saxed moist rodent goodness.
- Soundbite — dialogue search for Apple’s Final Cut Pro and Adobe Premiere Pro. Boris Soundbite quickly and accurately finds any word or phrase spoken in recorded media. Shoot squirrels with computer vision, search audio with computer hearing. We live in the future, people. (via Andy Baio)
- Why Finish Books? (NY Review of Books) — the more bad books you finish, the fewer good ones you”ll have time to start. Applying this to the rest of life is left as an exercise for the reader.
ENTRIES TAGGED "web design"
Efficient, reusable markup reduces development work while boosting page load time
Optimizing your markup can have a substantial impact on your site’s page load time. Bloated HTML leads to bloated CSS, and vice-versa. For example, during a semantics and reusability template cleanup, I was able to significantly reduce the file size of site-wide HTML, CSS, and stylesheet images.
I achieved this by simply renaming existing elements to have more semantic meaning and then removed unnecessary elements in the HTML (also known as divitis) to focus on reusability. Later in the same cleanup effort, I was able to cut CSS by 39% by removing unused selectors, combining and condensing styles, and normalizing the colors used across the site.
Optimizing images is likely the biggest win for performance on your site
[Ed note: This is the second in a series of posts on web design and performance. You can see the introductory post here.]
Images make up the majority of most sites’ page weight. Thanks to their size and the number of image requests made by an average site, optimizing images is arguably the easiest big win when it comes to improving your site’s page load time.
Let’s start by looking at the various image types available, and then work through the various options you have for optimizing them.
Web design trends often carry hefty performance costs
Web and mobile users continue to expect faster sites and apps–especially when it comes to mobile–and this year I’d like to see people who work on the web spend more time focusing on performance as a user experience priority instead of chasing trends.
I recently ran across this article in Forbes, which lists a number of web design goals/trends that Steve Cooper is eyeing for a site redesign of online magazine Hitched. My intention is not to pick on Hitched or Cooper per se, but the list is a molotov cocktail of potential performance woes:
- Continuous scrolling
- Responsive design
- Parallax sites
You can use most of those techniques without creating performance nightmares, but it is unfortunately rare. I feel like I’m living in an alternate reality where I’m hearing that users want simpler, faster sites, and yet the trends in web design are marching in the opposite direction.
Remember, even a failure can serve as an example of what not to do
The first highly visible component of the Affordable Health Care Act launched this week, in the form of the healthcare.gov site. Theoretically, it allows citizens, who live in any of the states that have chosen not to implement their own portal, to get quotes and sign up for coverage.
I say theoretically because I’ve been trying to get a quote out of it since it launched on Tuesday, and I’m still trying. Every time I think I’ve gotten past the last glitch, a new one shows up further down the line. While it’s easy to write it off as yet another example of how the government (under any administration) seems to be incapable of delivering large software projects, there are some specific lessons that developers can take away.
How to design products and services that help users change behavior
Steve Wendel (@sawendel) is the Principal Scientist at HelloWallet where he develops applications that help users take control of their finances. He’s also currently writing Designing for Behavior Change. I recently sat down to talk with Steve about the importance of testing and iteration, role of psychology, and resources and tools.
Key highlights include:
How to "future-proof" your sites
Users expect to be able to use and bookmark a website by name—always the same name, regardless of the device used to reach and view the site. From a user’s standpoint, a site is a site regardless of which device is being used to reach it. The code that backs up the site should be smart enough to detect the requesting device and intelligently serve the most appropriate markup.
There are several ways to achieve this goal, and at least three realistic scenarios.
Distinct Sites for Mobile and Desktop
Modern websites are built around the typical size of a desktop or laptop monitor. In fact, until the advent of iPhones, web developers rarely considered the need to fit web content into different sizes. Now, however, establishing an effective presence on mobile devices is a necessity. Just because your websites can be accessed by smartphones and tablets doesn’t make them effective. To provide an effective experience, you must optimize your sites for specific classes of devices—typically, smartphones and tablets. For quite some time, it seemed that distinct “m”-sites were a good-enough solution. For example, the website at www.somecompany.com was available in mobile-optimized form using the URL m.somecompany.com. In terms of development, the two sites are completely different; they were projects that simply shared some portions of the back end.
Squirrel Targeting with Computer Vision, Audio Recognition, Single Page Apps, and Persisting at Failing
Compete on Convenience, Minimal Viable Operating System, Awesome Font, Collaboration Integration
- Add Torrent Links to IMDB (Userscripts) — a glimpse at what the Internet could look like: from the site you research movies on, with one click you could then launch the download. If only the company that ran the movie research site had rights to the OneClick patent and the ability to offer movies for download. Oh wait, those aren’t the barriers. If only the movie companies would cease being nutjobs insisting on flogging their DRM-hobbled nags when the black market has x264 racehorses for less. They’re not competing on price, they’re not competing on convenience, they’re competing on the expected value of litigation. Now *that’s* a business model!
- JeOS — I hadn’t heard this term before: Just Enough Operating System. Take a standard distro, and strip it down to the bare essentials that you actually need.
- Font Awesome — a font with a zillion pictograms and icons. “An iconic font designed for use with Twitter Bootstrap”.
- Collabograte — a collection of integration recipes for collaboration tools so you aren’t broken on the “how do I get this thing set up with LDAP auth?” wheel which others have reinvented with their nose to the mixed metaphor grindstone. (via Kartik Subbarao)
Denise R. Jacobs advocates for new approaches to work and community.
Author and web design consultant Denise R. Jacobs reveals lessons she learned about creativity while writing her first book. She also discusses her efforts to give women and people of color more visibility in the tech world.
Human Labour, Kinect in Laptops, Web Fonts, and Brain Boosting
- Improvisation and Forgiveness (JP Rangaswami) — what makes us human is not repetitive action. Human occupations should require human intellect, and there’s no more human activity than making a judgement call when processes have failed a customer.
- Kinect Tech in Laptop Prototypes — “waving your hands around at your laptop” will be the new “bellowing into your walkie-talkie phone”. (via Greg Linden)
- Beautiful Web Type — demo page for the best from Google’s web fonts directory. Source on GitHub.
- Ethics of Brain Boosting, Discussion (Hacker News) — this comment in particular: in my initial reckless period of self-experimentation, I managed to induce phosphenes by accident — blue white flashes in the entire visual field, blanking out everything else. Both contacts were in the supraorbital region. I ceased my experiments for a while and returned to the literature. And you thought that typo where you accidentally took the database offline was bad ….