Seven Deadly Sins of Programming - #4

re: Seven Deadly Sins of Programming - #4

Ricky Dhatt — Tue, 27 Jun 2006 02:59:15 GMT

I prefer to say I live in "South Newcastle".

re: Seven Deadly Sins of Programming - #4

roman — Tue, 27 Jun 2006 10:23:01 GMT

At the university our prof always told us "Optimization is a thing you can ignore while implementing your program. You can'T do any optimization before your program is running and you know where are the hotspots and what is the goal of your optimization"

re: Seven Deadly Sins of Programming - #4

Wife PhC — Tue, 27 Jun 2006 20:54:34 GMT

So you finally admit it and I have witnesses!!!!

re: Seven Deadly Sins of Programming - #4

Mike Dimmick — Tue, 27 Jun 2006 23:30:01 GMT

I'd argue that doing the hash table, binary search, etc is not premature optimization IFF you know that it will be needed. That is, you've thought about the cardinality of the data - how much there'll be, and how critical the accesses to it are - and choose your data structure or search algorithm appropriately. Choosing right now can save rework.

I do see the 'premature optimization' quote given out as an excuse for not thinking about the cost of operations, and that often ends up with an unusable first alpha, beta, or even an unusable production system when it's finally presented with the actual volume of data it needs to handle. In particular, OLTP database systems without enough thought into archiving and analysing historical data, allowing volumes of inactive data to build up.

re: Seven Deadly Sins of Programming - #4

ericgu — Tue, 27 Jun 2006 23:52:35 GMT

Mike,

My experience - and the opinion of a fair number of people who have done more than I have - is that in anything but the most simple situations, developer estimates on how important one section of code is to the overall speed is pretty poor. It's just not possible to know enough ahead of time to do a meaningful analysis.

Note that I'm not advocating putting optimization at the end. That does often lead to the kinds of ills that you mention, and at that point in the project there's often little that can be done about it.

But facts trump thinking every time. That's Rico's point in his posts - if performance is important in your app, then you have to create a culture of performance where you measure performance in real scenarios throughout the project. That will tell you what needs to be optimized.

re: Seven Deadly Sins of Programming - #4

r3n — Mon, 24 Jul 2006 18:25:20 GMT

When I find my self branching out into premature optimisation type code that *may not be needed*, I usually encapsulate it so that it easy to expand on later (if neccecary).

I find, this also helps highlight code that could be optimised later on; rather than allowing it to blend into it's surroundings and otherwise become unnoticed.

Technical Related Notes » Blog Archive » links for 2006-07-19

Technical Related Notes » Blog Archive » links for 2006-07-19 — Tue, 25 Jul 2006 06:34:14 GMT

PingBack from http://technote.thedeveloperside.com/?p=56

Seven deadly sins of programming - Sin #1

Eric Gunnerson's C# Compendium — Fri, 04 Aug 2006 19:46:22 GMT

So, the time has come for the worst sin.
Just to recap - and so there is one post that lists them all...

Magerquark.de » “Seven deadly sins of programming”

Magerquark.de » “Seven deadly sins of programming” — Sun, 06 Aug 2006 00:17:14 GMT

PingBack from http://www.magerquark.de/blog/archive/374

Pyre Blog » Blog Archive » Seven Deadly Sins of Programming

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

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

links for 2006-10-08 | Phil Wallach

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

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

My Bag of Beans » Blog Archive » Seven deadly sins of programming

My Bag of Beans » Blog Archive » Seven deadly sins of programming — Wed, 11 Oct 2006 01:19:07 GMT

PingBack from http://bagofbeans.tsangal.org/archives/203

Double Check Locking and Other Premature Optimizations Can Shoot You In The Foot

you've been HAACKED — Tue, 20 Mar 2007 09:14:29 GMT

Double Check Locking and Other Premature Optimizations Can Shoot You In The Foot

Community Blogs — Tue, 20 Mar 2007 10:46:00 GMT

After reading Scott Hanselman’s post on Managed Snobism which covers the snobbery some have against managed

Optimizing LINQ Queries

K. Scott Allen — Tue, 15 Jul 2008 05:34:17 GMT

I’ve been asked a few times about how to optimize LINQ code. The first step in optimizing LINQ code is...

Optimizing LINQ Queries

Experiments In Writing — Tue, 15 Jul 2008 05:35:01 GMT

I’ve been asked a few times about how to optimize LINQ code. The first step in optimizing LINQ code is

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | Outdoor Ceiling Fans

Sun, 31 May 2009 11:49:56 GMT

PingBack from http://outdoorceilingfansite.info/story.php?id=1123

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | Weak Bladder

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | Weak Bladder — Mon, 08 Jun 2009 04:40:42 GMT

PingBack from http://weakbladder.info/story.php?id=3480

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | Toe Nail Fungus

Tue, 09 Jun 2009 08:57:52 GMT

PingBack from http://toenailfungusite.info/story.php?id=3256

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | home lighting

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | home lighting — Sun, 14 Jun 2009 05:03:58 GMT

PingBack from http://homelightingconcept.info/story.php?id=1175

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | patio set

Eric Gunnerson s C Compendium Seven Deadly Sins of Programming 4 | patio set — Thu, 18 Jun 2009 05:05:34 GMT

PingBack from http://patiosetsite.info/story.php?id=666