user experience
I've largely been ignoring Nicholas Negroponte's One Laptop Per Child initiative. I appreciate the nobility of the gesture, but how interesting can sub-$100 hardware running Linux really be? Well, that was before I read about the novel user interface they're building into those
programming languages
Eric Lippert is one of my favorite Microsoft bloggers. He's one of those people who reminds you that Microsoft, despite all its problems, still employs a lot of incredibly thoughtful, near-genius programmers. Take a look at his greatest hits: * How many Microsoft employees does it take to change
programming languages
In an earlier post on the philosophy of code comments [https://blog.codinghorror.com/when-good-comments-go-bad/], I noted that the best kind of comments are the ones you don't need. Allow me to clarify that point. You should first strive to make your code as simple as possible to
programming languages
A recurring theme in Edward Tufte's books is the massive difference in resolution between the printed page and computer displays. Printed pages lend themselves to vastly greater information density. Sparklines are one particular technique of Tufte's designed to exploit the greater resolution of the printed page.
software development concepts
Anil Dash and I have the same job title: evangelist. I share Anil's reservations about his job title, too: You see, these days my business cards describe me as "Chief Evangelist". On the plus side, it's the first time in the history of the
software development concepts
Simplicity isn't easy to achieve, and John Maeda's short book, The Laws of Simplicity, provokes a lot of thought on the topic. Programmers swim in a sea of unending complexity. We get so used to complexity as an ambient norm that we begin, consciously or unconsciously,
programming languages
Here's an excellent bit of halloween advice from Mike Gunderloy: go read some source code you wrote five years ago for a real scare. It's a good idea to go occasionally back to the well and get a sense of your progress as a so-called professional
programming languages
Ian Landsman's 10 tips for moving from programmer to entrepreneur [https://web.archive.org/web/20070306071950/http://www.userscape.com/blog/index.php/site/comments/10_tips_for_moving_from_programmer_to_entrepreneur/] is excellent advice. Even if you have no intention of becoming an entrepreneur. > One
programming languages
How in the world wide web did I not know about the "I Rock at BASIC" t-shirt [http://glarkware.com/adult/i-rock-at-basic]? [http://glarkware.com/adult/i-rock-at-basic] We've all written this program at some point in our careers. But only those of us who truly rock
programming languages
O'Reilly's History of Programming Languages poster is fascinating reading. If you trace programming languages back to their origins, you'll find that we've been at this programming stuff a long, long time. * Fortran (1954) * Cobol (1959) * Lisp (1958) * Basic (1964) * Forth (1970) * Pascal
software development
For the last few days, I've been surveying a software project. Landing on a planet populated entirely by an alien ecosystem of source code can be overwhelming. That's why the first first thing I do is bust out my software tricorder -- static code analysis tools.
programming languages
When you're starting out as a technical blogger, you'll inevitably stumble across Joel on Software [http://www.joelonsoftware.com/]. He's been blogging since the year 2000, when computers were hand-carved of wood and the internet transmitted data via carrier pigeon. He has his own