It's the same old same old.

A gap appears in our (strictly hypothetical) development team and suddenly we're running around like headless chickens trying to fill it.

It's a desperate situation that we've created for ourselves. Because we only actively recruit when we have an urgent vacancy, we end up with whatever and whoever happens to be available at that exact time.

By Miško Hevery

People are good at turning concrete examples into generalization. The other way around, it does not work so well. So when I write about general concepts it is hard for people to know how to translate the general concept into concrete code. To remedy this I will try to show few examples of how to build a web application from ground up. But I can't fit all of that into a single blog post ... So lets get started at the beginning...

Posted by Philip Zembrod

So the Test-Driven-Development and Extreme-Programming people tell you you should write your tests even before you write the actual code. "Now this is taking things a bit too far," you might think. "To the extreme, even. Why would I want to do this?"

In this post, I'll tell you my answer to this question. I now really do want to write my tests first...and here's why!

My web testing tool (WebInject) is now being used as part of the Advanced Java class being taught at SMU's Engineering school.

They will be using it for testing Servlets.

very cool!

http://engr.smu.edu/~coyle/cse7345/

This is a an ordered list of programming languages I have learned in the past 15 years:

1. BASIC
2. LISP (Scheme)
3. C++
4. Shell
5. Perl
6. JavaScript
7. Java
8. Python
9. C#

What does your list look like? (add it to the comments)