For exploring complex software development ideas then a more effective way is to leverage more of the senses. John Udell in fact has come up with a preliminary list of "Screencast Guidelines". I've stumbled upon a couple more screencasts to justify the existence of a trend.

SOAP is comatose, but hasn't declared legally dead by either IBM or Microsoft. But how did this all happen? Isn't SOAP the underpinnings of Web Services, the same technology that was billed as the silver bullet to extinguish our collective integration nightmare? Well the time of reckoning has now arrived.

If one considers hacking as solely an individual activity, then the limits of expression does have a non-negligible impact on productivity. However, when we involve groups of people, then a language that "supports communities" bests out a "Hacker" language.

There are a lot of ideas in software engineering are considered as truth until someone pinpoints the fallacies. Peter Deutsch first came up with his “Eight Fallacies of Distributed Computing” to debunk misconceptions about distributed computing. I happen to have a list of my own. Here are 10 Fallacies of Software Analysis and Design.

Adding Generics to the Java language isn't going to revolutionary change the status quo. People extremely over estimate the value of language constructs in the overall scheme of providing compelling solutions to a customer.

Jim Coplien now has a teaching job, but he's saying that it's about time we get rid of classes. Here's my take on why he may just be on to something.

It's high time we all face up to reality. The network is and will remain "heteregenous". In spite of the sincere efforts of vendors and standards organizations to homogenize the network, the networks insists that it is indeed heteregenous.

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.

Idiomatic java isn't a place to get inspiration on how to build loosely coupled architectures. Even though Java idioms are extremely useful, when you get to "programming in the large" it's a whole different ballgame.

George Santayana, a notable philosopher, coined the phrase, "Those who do not learn from history are doomed to repeat it." A study of the history of the CORBA standard reveals that for WebService standards, history is again repeating itself.

Static Reasoning favors perfect planning over runtime adaptability. This is a favored approach in the software community. However, there are limits to static reasoning, grasping this fact helps achieve better manageability of complexity.

The Hive Mind is asynchronous.  You don't have to be in the same place or even in the same time to be able to converse.

More precisely, "Does Aspect Oriented Programming (i.e. AOP) supercede Component Models?".  It's an interesting question, something we all would like to know before the AOP hype machine gets to full gear.  To answer it, let's get our definitions straight first.

Dumbing down the language by not providing more powerful expressions is a way of promoting to a wider audience. However, is it the only way of supporting communities?