Most imperative languages are designed to express control flow explicitly. Unfortunately, this makes it difficult to program in a more reactive style. Proposed are two constructs, Generators and Grammars to help ease the burden.

3 Laws of Software Complexity analagous to 3 Laws of Thermodynamics.

Next week Bruce Eckel and I will be co-interviewing Anders Hejlsberg, the chief architect of C#. Although we already have several topics lined up to ask to Anders about, I'd like to give Artima.com readers a chance to post their own ideas for the interview. What would you like to hear Anders Hejlsberg talk about?

Java serving 1 billion pages per day for eBay! I'm always looking for Java case studies. It's fascinating to see just what people have done. This set from JavaOne lists eBay, The Wall Street Journal, American Airlines, several huge governmental organizations, and many more.

In which I consider the changing of my employment situtation

While I'm all for healthy competition, the open source world might be taking it a bit too far.

Programming is complicated, and the problems that "they" ask us to program are complicated. As a "bear of very little brain", my only hope is simplicity. My primary theme in these logs will be to explore how to find simplicity amid all the mess.

How much method overloading is a good thing? How much is just bewildering?

Observations on the summertime mating practices of systems engineers, well-versed in moving data into and out of everything non-human, with interface designers, who it turns out are obsessed with more than just collecting new fonts for annoying ad banners.

Software engineering is a lot less like other kinds of engineering than most of us would like to think. There is an aspect of art to what we do, that is learned not in school but by finding a master and serving an apprenticeship.

The JavaOne prgramming puzzlers session is well worth a look if you have any Java geek in you.

With the advent of languages such as Python, the debate over typing has heated up again. Contrary to some claims (notably from Bruce Eckel), I believe Python has strong typing, and this article explains why.

After being offline longer-than-expected, I can finally post my blog entry on last week's Open Source Conference

As software craftsmen, we have rules. Sometimes we feel bad when the rules mut be broken. They're just rules though. What's important is that we have a moral center, a professional core, that refuses to compromise the quality of our work.

What matters in the end is working code, not the tool that made it. I propose that developers buy their own tools and be held responsible for installing, maintaining, and dealing with them just like auto mechanics do.