Category: Agile Development

If Architects Had To Work Like Web Designers…

Dear Mr. Architect:

Please design and build me a house. I am not quite sure of what I need, so you should use your discretion. My house should have somewhere between two and forty-five bedrooms. Just make sure the plans are such that the bedrooms can be easily added or deleted. When you bring the blueprints to me, I will make the final decision of what I want. Also, bring me the cost breakdown for each configuration so that I can arbitrarily pick one.
Continue reading “If Architects Had To Work Like Web Designers…”

Recognition gap

Esther Derby describes a notice from Gallup about the lack of recognition and appreciation in modern companies.

Continue reading “Recognition gap”

Don’t Overcomplicate Things

A gentle reminder to myself: don’t make things more complicated than they need to be.

Continue reading “Don’t Overcomplicate Things”

Python Paradox makes sense…

Paul Graham wrote about The Python Paradox. Unlike his earlier talk, this one actually had a good point.

Continue reading “Python Paradox makes sense…”

Why it’s important to be able to unit test outside the container

Daniel Steinberg has a “note on Java.Net”:http://weblogs.java.net/pub/wlg/1732 about testing EJBs out of the container, and wonders why people make a fuss about it. There’s a simple reason: speed.

Daniel Steinberg has a “note on Java.Net”:http://weblogs.java.net/pub/wlg/1732 about testing EJBs out of the container, and wonders why people make a fuss about it. There’s a simple reason: speed.

Continue reading “Why it’s important to be able to unit test outside the container”

Wow… Free Visual Studio versions

One of the great strengths of the Java community is the quality of the free (as in both speech and beer) development environments, Eclipse and NetBeans. Although Microsoft let you have the .NET SDK for free (as in beer), there was no free IDE. Until now.

Continue reading “Wow… Free Visual Studio versions”

Circle/Ellipse Paradox… NOT!

There’s a (somewhat controversial) design principle in object-oriented programming called the Liskov Substitution Principle. One of the classic examples is about Circles being Ellipses.

Continue reading “Circle/Ellipse Paradox… NOT!”

/** Still no comment */

Cedric takes exception to my earlier post another who didn’t get what I was saying. I think that says a lot for my ability to explain ideas, uh?

Continue reading “/** Still no comment */”

Commenting example

In response to Chris Justus again, here’s how I’d comment his example.

Continue reading “Commenting example”

/** no comment */

Chris Justus managed to totally miss my point. He assumes that I was advocating for crappy uncommented code. That is not the case.

Continue reading “/** no comment */”