Re: What's more important optimisations or debugging?
- From: BubbaGump <BubbaGump@localhost>
- Date: Wed, 30 May 2007 19:21:57 -0400
On 30 May 2007 15:15:07 -0700, rhapgood@xxxxxxxxx wrote:
I'm trying to get a feel for what people now consider more important,
optimisations or debugging ability. In the past with such tight memory
limits I would have said optimisations but now with expanded-memory
parts becoming cheaper I would think that debugging ability is more
important in a development tool. It's is not exactly a black and
white question, debug or smallused, but more a ratio. eg. 50% debug/
50% optimised or 70% debug/30% optimised, etc.
Any feedback would be greatly appreciated.
I don't understand the question. Debugging features in a development
tool or extra debugging information in executable code?
Programming is an art. Not only is it not a black and white question,
but percentages don't make sense either. The style of a product
depends on the circumstances and the arbitrary preferences of the
a-holes involved in its development or its use. There is no right or
wrong.
.
- Follow-Ups:
- Re: What's more important optimisations or debugging?
- From: CBFalconer
- Re: What's more important optimisations or debugging?
- From: Ryan H
- Re: What's more important optimisations or debugging?
- References:
- What's more important optimisations or debugging?
- From: rhapgood
- What's more important optimisations or debugging?
- Prev by Date: Re: Trust 1-man headhunter operation?
- Next by Date: Re: What's more important optimisations or debugging?
- Previous by thread: What's more important optimisations or debugging?
- Next by thread: Re: What's more important optimisations or debugging?
- Index(es):
Relevant Pages
|