Seven deadly sins of programming - Sin #1

re: Seven deadly sins of programming - Sin #1

Peter Ritchie — Fri, 04 Aug 2006 20:02:54 GMT

Sounds more like "Over Generalization" or "Unrelated Abstraction" to me.

If you follow some of the TDD techniques of separation of tests, generalization of almost everything at the class level is a necessary first step, if only to add the ability to stub implementation...

In your example of SetColMargin, you don't have to have a wrapper class in order to generalize.

re: Seven deadly sins of programming - Sin #1

grauenwolf — Fri, 04 Aug 2006 21:34:46 GMT

I think that pretty much sums of the underlying problem in just about every Java library I have worked with.

IndianGeek » Interesting reading for August-05-2006

IndianGeek » Interesting reading for August-05-2006 — Sat, 05 Aug 2006 07:05:35 GMT

PingBack from http://www.indiangeek.net/?p=22

Interesting reading for August-05-2006

Sijin Joseph's blog — Sat, 05 Aug 2006 07:06:23 GMT

A Spec-tacular Failure - A rant by Jeff Atwood on why the ID3 spec totally suxx. Google Code Project

re: Seven deadly sins of programming - Sin #1

Chris Nahr — Sat, 05 Aug 2006 11:29:28 GMT

This time I got the pun when I read it. Groan. ;)

WCF: Navigating the Binding maze

Miscellaneous Debris — Mon, 07 Aug 2006 11:25:14 GMT

A few days ago I ranted a bit about the Binding object model in WCF and how restrictive it feels when

WCF: Navigating the Binding maze

Miscellaneous Debris — Mon, 07 Aug 2006 11:25:20 GMT

A few days ago I ranted a bit about the Binding object model in WCF and how restrictive it feels when...

Pyre Blog » Blog Archive » Seven Deadly Sins of Programming

Pyre Blog » Blog Archive » Seven Deadly Sins of Programming — Tue, 08 Aug 2006 00:57:24 GMT

PingBack from http://pyre.third-bit.com/blog/archives/598.html

re: Seven deadly sins of programming - Sin #1

david_douglass — Tue, 08 Aug 2006 05:01:31 GMT

The excuse I always run into for Premature Generalization is "reuse". People say "We're going to make something everybody in the corporation can use and we'll be heros". But they don't have anybody else's requirements and it's not feasible to get them, so they guess at the requirements. The code becomes more complex, but for no good reason, since nobody wants to use this creation that doesn't meet their requirements. Another part of this is the thinking "We know the best way to do things and our reusable component will ensure that everybody else does things the right way."

re: Seven deadly sins of programming - Sin #1

Björn Waide — Tue, 08 Aug 2006 10:22:38 GMT

I like to recommend this paper from Martin Fowler for further reading: "To be explicit" (http://www.martinfowler.com/ieeeSoftware/explicit.pdf).
Thank you for sharing this list of sins with us. Guess I have to pray for indulgence in some cases! ;-)

Tying MVP To the ASP.NET Event Model

Community Blogs — Wed, 09 Aug 2006 20:01:19 GMT

I knew this question would come up, so I figure I would address it in its own blog post. Mike asks a

re: Seven deadly sins of programming - Sin #1

Will Lynn — Wed, 09 Aug 2006 22:26:49 GMT

I was reading your cycling category blogs and came across this (not sure why it's under cycling). I'm a .NET developer too though. I think one of the reasons this happens is that developers like to think or imagine they can engineer the perfect solution, but it actually ends up kind of like the One True Ring (...to bind them all).

7 Virtues for Software Developers

K. Scott Allen — Thu, 10 Aug 2006 05:51:06 GMT

http://blog.lifebeyondcode.com/blog/_archives/2006/2/7/1750207.html
Diligence - Diligent developers...

Seven Deadly Sins of Programming - The Winner is Announced

ON THE MATTER — Tue, 15 Aug 2006 17:31:09 GMT

Eric finally announced&nbsp;the winner in his series&nbsp;about sins of programming. The winner is "premature...

Интересни връзки 3

Йордан Димитров — Thu, 17 Aug 2006 08:09:12 GMT

Вече има и SP 1 за Microsoft® Visual Studio® .NET™ 2003 download. CTP на нoвата&nbsp;версия на ADO.NET...

re: Seven deadly sins of programming - Sin #1

Chris Anderson — Tue, 22 Aug 2006 19:15:33 GMT

A few years ago, our company owner at the time dished out some cash and had everyone in the company go through the 7 Habits of Highly Effective People (there were only about 12 of us at the time). While going through it, we jokingly came up with a list of 7 Habits of Highly Ineffective Software. All too often we let habits 1-4 get in the way.

Be Reactive
Begin with no Design in mind
Put Fun Things First
Think: Copy, Paste
Seek First to make others understand
Prevent Communication
Dullen the Blade

Chris

re: Seven deadly sins of programming - Sin #1

John — Wed, 23 Aug 2006 07:11:41 GMT

I would say a much more annoying sin is lack of generalization - the swiss-army knife component you describe is the result of too-little generalization, not too much. A system with generalized components you can pick and choose from is much better at keeping code and data grouped, and defining objects that share functionality. A system that does everything for everyone is too specialized, not too generalized.

links for 2006-10-08 | Phil Wallach

links for 2006-10-08 | Phil Wallach — Sun, 08 Oct 2006 03:29:03 GMT

PingBack from http://www.philwallach.com/?p=65

Interesting Finds: November 11, 2006 « Hank Wallace

Interesting Finds: November 11, 2006 « Hank Wallace — Sun, 12 Nov 2006 00:17:04 GMT

PingBack from http://hankwallace.wordpress.com/2006/11/11/interesting-finds-november-11-2006/

Performance Problems Survey

Eric Gunnerson's C# Compendium — Tue, 27 Feb 2007 19:32:08 GMT

Rico (who I am currently listening to on a new episode of " Behind the Code ") posted an interesting

Aquarius! » ?????????? » ?????????????????????? ??????????????????????????

Aquarius! » ?????????? » ?????????????????????? ?????????????????????????? — Wed, 29 Aug 2007 19:06:50 GMT

PingBack from http://skanev.com/2007/08/29/premature-generalization/