What's your style. Do you constantly think about performance and put grate effort to make your code as fast as possible or do you just make it work and sort out performance issues when they bite? Somewhere between? Do you profile your code or relay on your knowledge?
Just thinking. For example, I need a relatively simple template engine, I could easily implement a high performance version in 100 - 150 lines of code, or I could just use regular expressions and get it around 50 lines..
Name:
Anonymous2007-08-06 19:56 ID:H9Dv1bgb
And here's an interesting bit of trivia: did you know that the ASP.NET page parser is built with regular expressions, and not only the v1.x, but the Whidbey version too.
Name:
Anonymous2007-08-06 19:57 ID:QzVaAFBs
Somewhere between. If it's not fast enough, I profile.
Architecturally, my code is usually designed to scale. The code itself is written to be as simple as readable as possible unless it later turns out to be a bottleneck.
Name:
Anonymous2007-08-06 20:10 ID:H9Dv1bgb
>>4
Yes, readability is another important factor. Usually slower, but simpler and more flexible code is preferable over faster, but harder to understand and modify.
But how are you "somewhere between"? You write your code to be as simple as possible, solving performance issues only later.
Name:
Anonymous2007-08-06 20:17 ID:8Xpl2fPN
>>5
"Somewhere between" because of the architecture. The code is as simple as possible, but the architecture is designed so that there aren't any (known) bottlenecks.
It's easy to change some code to be performant. It's usually bloody hard to do it if it's an artifact of your program design. As a result, best to take care of it up-front.