• Coding

  • [Discussion] Complexity Threshold

arithma wroteNot an algorithm. Who writes those in the field anyway? We need something of a practical simple, but wide enough task.
No no.

This:
xterm wroteProbably a dozen variation of some algorithm!
was an answer to this:
arithma wroteMy code? Refresh my memory :)
At one point, too much complexity becomes counter-productive and demotivating. As developers our code is in a sort our ambassador, and it exists in a competitive place and competes with code from other developers. So make your code too complex, whether for you or someone else, and other people's code (and their services by extension) will start to look more attractive.
How does Complexity relates to creating best over fast/worst implementation of a problem at hand ?

The subject is out of context.
Why is it so hard to relate the word Complexity to a problem? There's implementation complexity, there's design complexity, there's architectural complexity, there's algorithmic complexity and i was clear enough from the beginning, asking people to pick their own area as an example.

I clearly chose a design complexity and I was quite clear in what I said:
xterm wroteThis has popped very recently in my head every time I try to build something remotely trivial. I end up making things much more complex than they should be, granted I cannot for the life of me go back to doing things the sub standard way.
In my case, I chose to (bar the trivial sample i gave) opt for a flexible design that would provide me with loose coupling, testability, reuse, presentation architectural pattern albeit I do not need it for the problem I had. I chose to do it like this because (refer to the previous quote) I cannot for the life of me go back to doing things the sub standard way.

Someone like rahmu would, when doing the same thing say "I'll go for quick approach and worry about the rest when and if the time comes". That's how he feels and he enjoys doing it.

I don't, hence, i create unnecessary complexity and I always try to find a threshold to restrain myself.
arithma wroteMy code? Refresh my memory :)
Your solution to LebInt code still haunts me.
I cannot for the life of me go back to doing things the sub standard way.

Someone like rahmu would, when doing the same thing say "I'll go for quick approach and worry about the rest when and if the time comes". That's how he feels and he enjoys doing it.
The thing is, when designing a CRUD app, you know pretty much what's the 'standard' way, and what is 'sub standard'. Even if you don't make use of all this complexity, you just know what is the right way to implement something and do so accordingly. All CRUD apps work the same, after all.

When I work on a CRUD app, I tend to have a more 'cautious' and 'perfectionnist' approach. But a big part of my programming consists of extracting data from various file formats (XML, CSV, ...) and formatting it. These scripts I write and maintain tend to grow very big and are meant to last for a long time, so my teammates can still use them years after I'm gone.

While the complex/optimal approach is much needed, I generally favor a "write first - optimize later" approach.
xterm wroteWhy is it so hard to relate the word Complexity to a problem? There's implementation complexity, there's design complexity, there's architectural complexity, there's algorithmic complexity and i was clear enough from the beginning, asking people to pick their own area as an example.
Sorry, but did you read my post ? I said We cannot relate Complexity to the quality of implementation.
Joe3dr wroteSorry, but did you read my post ? I said We cannot relate Complexity to the quality of implementation.
Good code, design, etc, tend to be more complex than bad code, design, etc. (ref: better quality)
Complex code, design, etc, is not always good code design, etc. (ref: worse quality)

So to accommodate what you said, yes, partially this topic is out of context.

If it makes you feel better, I could remove the "Best/Worst" part of the topic :-)