Ninnunännu

-Yeah, The New York Times says the air's bad down here.
-Oh, yeah? Well, fuck The Times. I read the Post.

25th hour

When adding features, we
were better off when there was no preexisting
design to handle that feature.
Adding code that doesn’t exist is easy;
fixing someone’s preconceptions about
a feature first is more costly.

Jim Shore

AOP: Aspect-Oriented Programming Enables Better Code Encapsulation and Reuse -- MSDN Magazine, March 2002

!!! Is Design Dead?: "Getting to a release as fast as possible is vitally important. Any additional complexity is worth doing after that first release if it isn't needed for the first release. The power of shipped, running code is enormous. It focuses customer attention, grows credibility, and is a massive source of learning. Do everything you can to bring that date closer. Even if it is more effort to add something after the first release, it is better to release sooner. "

Is Design Dead?: "Rather than trying to get the right decision now, look for a way to either put off the decision until later (when you'll have more information) or make the decision in such a way that you'll be able to reverse it later on without too much difficulty. "

Is Design Dead?: "Changing the design doesn't necessarily mean changing the diagrams. It's perfectly reasonable to draw diagrams that help you understand the design and then throw the diagrams away. Drawing them helped, and that is enough to make them worthwhile. They don't have to become permanent artifacts. The best UML diagrams are not artifacts."

Is Design Dead?: "A common problem with the common use of diagrams is that people try to make them comprehensive. The code is the best source of comprehensive information, as the code is the easiest thing to keep in sync with the code. For diagrams comprehensiveness is the enemy of comprehensibility."

Is Design Dead?: "The best advice I heard on all this came from Uncle Bob (Robert Martin). His advice was not to get too hung up about what the simplest design is. After all you can, should, and will refactor it later. In the end the willingness to refactor is much more important than knowing what the simplest thing is right away."

Is Design Dead?: "But as one of the developers said 'it's easier to refactor over-design than it is to refactor no design.' It's best to be a little simpler than you need to be, but it isn't a disaster to be a little more complex."

Is Design Dead?: "So to summarize. You don't want to spend effort adding new capability that won't be needed until a future iteration. And even if the cost is zero, you still don't want to it because it increases the cost of modification even if it costs nothing to put in. However you can only sensibly behave this way when you are using XP, or a similar technique that lowers the cost of change."

Is Design Dead?: "If I want a Money class today that handles addition but not multiplication then I build only addition into the Money class. Even if I'm sure I'll need multiplication in the next iteration, and understand how to do it easily, and think it'll be really quick to do, I'll still leave it till that next iteration."

Is Design Dead?: "The way YAGNI is usually described, it says that you shouldn't add any code today which will only be used by feature that is needed tomorrow. "

Two of the greatest rallying cries in XP are the slogans "Do the Simplest Thing that Could Possibly Work" and "You Aren't Going to Need It" (known as YAGNI). Both are manifestations of the XP practice of Simple Design.

Fowler

Finally, I must point out an important caveat: Only provide
accessors if you really need to. Accessors often lead to
code where one object pulls data out of another and then
does something that the original owner should have done directly.

Fowler

David Parnas observed that
modules should be arranged around system secrets,
each module hiding its secret from the
other modules. Then if the secret thing changes,
you avoid a ripple effect.

Instead of using your fingers to type, try using the end of a pencil for an hour. Frustrating at the time, but it will have negiligible impact apart from distracting you. What does a good developer do when they start refactoring code? They start hitting the delete key, that's what. Type less, not faster.

Lastcraft
http://www.sitepoint.com/forums/showthread.php?t=173308

There are many ways to be beautiful - (don't know who first said this).