More from ALA
on the Human Web
We’re obsessive about collecting input from a wide range of potential users and stakeholders. But with such an onslaught of feedback, there’s always a risk of having your motivation and faith in humanity sucked right out of you. Sometimes, you just need calm critique from the few people who really get you. So which kind of feedback is best? The answer is both.
on Freelance Design
From the Blog
As a freelancer, I work in a lot of different code repos. Almost every team I work with has different ideas of how code should be organized, maintained, and structured. Now, I’m not here to start a battle about tabs versus spaces or alphabetical order of CSS properties versus organizing in terms of concerns (positioning styles, then element layout styles, then whatever else), because I’m honestly not attached to any one system anymore.
Part of getting comfortable with the command line is making it your own. Small customizations, shortcuts, and time saving techniques become second nature once you spend enough time fiddling around in your terminal. Since Git is my Version Control System of choice (due partially to its incredible popularity via GitHub), I like to spend lots of time optimizing my experience there.
I recently read Greg Smith’s piece on Bocoup's blog about how they think about time tracking, including all the fascinating data about how your brain works to solve problems. It interested me a lot, since I've been thinking about not just how I track projects, but also how I structure my day as a freelancer.
On Saturday, Benjamin Hollway, a 16 year old front-end developer, wrote a post about his recent experiences attending industry events. He’s been coding since he was eight, and earlier this year he was shortlisted for
Netmag's Emerging Talent category. Yet none of the people in this category are able to participate fully in the sort of activities most of us take for granted.
A newly-discovered Linux flaw may be more pervasive, and more dangerous, than last spring’s Heartbleed.