Put the knife down and take a green herb, dude.
One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com
Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!!
Back-up your data and, when you bike, always wear white.
MarkUpDown is the best Markdown editor for professionals on Windows 10.
It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support.
Features you won't find anywhere else include...
You've wasted more than $15 of your time looking for a great Markdown editor.
Stop looking. MarkUpDown is the app you're looking for.
|Monday, November 18, 2013|
Design Patterns Isn’t a Golden Hammer (from Phil Haack):
All too often, I’ve encountered code that uses a pattern because the developer felt he should use a pattern there, not because he needed the pattern.
Welcome to where I work right now. In a post that links, Haack gets waaay too close to home describing what this can feel like.
If you need to instantiate a factory, implement an adapter class and use a bridge to the toilet just to [go No. 2], then you probably live with a developer with a premature generalization problem.
What I've heard to explain mindless pattern usage is that many of our folks don't understand when you've gone from code that doesn't deserve major abstraction to code that does. While ultimately that's a hiring problem (you don't have coders competent enough to know how to factor their code), that fact doesn't help you solve the problems your current staff already has.
That's a tough quandary -- do you beat your head against the wall trying to teach those who seemingly can't be taught, spending yet more time making sure they go back to clean up their messes as they slog along -- or do you simply force them to follow the patterns all... the... time?
I think you have to try to teach folks, and if they continually can't handle refactoring, you have a reason to let them go. It's expensive to fire and hire, but it's got to be more expensive to keep using folks who can't code.
Great quote from Erich Gamma in that same post:
So far, I love this series of posts by Haack...
Design Patterns Isn’t [sic] a Golden Hammer
Avoid Premature Generalization
Avoid Premature Standardization
He apparently also has some posts on avoiding premature optimization. I'm just starting in on reading the series, and will probably feel compelled to blog about them a few more times...
posted by ruffin at 11/18/2013 07:02:00 AM
All posts can be accessed here:
Just the last year o' posts: