I have yet to toot my first tweet. Most of social networking has been lost on me. Too much noise, not enough signal.

My series against mixins continues. This time I consider using proxies instead of mixins, and I pose a design problem which will be solved in the last issue.

In "The Feel of Scala," a talk I gave at Devoxx which is now available on Parleys.com, I show Scala solutions to real problems to help you get a feel for the language. Along the way I demonstrate how you can get many of the productivity benefits offered by dynamic languages using alternative static techniques in Scala.

More on how and why netbooks might impact consumer electronics.

A preview of the next cycle of Adventures is given. I ask from reader's feedback and I announce the availability of the Adventures in both PDF and HTML formats. Rejoice!

I've observed two, often competing aspects of code readability: clarity of the programmer's intent (the "what") and clarity of the implementation (the "how"). What does code readability mean to you, and what do you think is the best way to maximize it?

Netbooks are becoming price and size competitive with certain classes of consumer electronics. Will this trigger a shift in the market?

In a recent discussion, there were assertions that C++ was a poorly-designed language. I was on the C++ Standards Committee for 8 years, and saw the decisions take place. I think it's helpful to understand the language choices for both C++ and Java in order to see the bigger perspective.

A list of all the Adventures published until now.

Last week I released a new version of ScalaTest (0.9.5) that includes a "matchers DSL" for writing more expressive assertions in tests. In this post I show differences between ScalaTest matchers and those in Ruby's RSpec tool, and discuss some of the general differences in DSL creation in Ruby and Scala.

This episode is about streams, a typical data structure of functional languages. The differences between functional streams and imperative iterators are discussed. En passant, I give a solution of the classic eight queens problem.

Testing APIs that use the current date and time are a pain because those values are variable. In Mailman 3 I hit upon a really dumb, simple way to do this that doesn't suck.

This episodes explains how to implement a functional list comprehension syntax in Scheme. The difference with Python list comprehension is also explained. Moreover, I have decided to distribute the code create for this series as a library: http://www.phyast.pitt.edu/~micheles/scheme/aps.zip

LongPause. Deep breath. Story resumes. Well, yes, it’s been a busy few months in the small, mobile devices field, what with being up to the eyebrows in day-in, day-out, day-job kinds of things.

I am republishing an old article I wrote in 2005 for O' Reilly (see http://www.onlamp.com/pub/a/python/2005/11/03/twill.html). The article is slightly outdated, but not much, and I am republishing it since nowadays to criticize excessive unit testing has become fashionable.