Neuroses and Programming

Are any of you guys neurotic? (Are all of you neurotic?)

I'm super neurotic. And I fear that, more than it helping me to program well, it gets in my way. I am obsessed with doing things the right way, and I begin to feel very uncomfortable if something I'm working on is becoming too complicated in the wrong way -- but somehow I'll be completely oblivious to how overblown my "clean and modular" solution ends up. But sometimes, the solution isn't obvious to me -- so if something is really stumping me, it eats my productivity and prevents me from feeling good about my work.

How do you deal with this? What general rules do you follow, and what do you do to put your mind at ease? For one thing, I'm thinking of getting a fish to put on my desk so that I can unload my stress on him.

>>19,40
I was under the impression that programming in such a way that it's resilient or receptive to future changes is a key sign of good work.

I'm trying a new strategy where I work the whole thing out on paper. It's hard to do that because I find the class/object diagrams tedious and unhelpful, as well as some flowcharts -- but my theory is that problems like these most often lie in the design, not a detail of the implementation.

I'm also going to start keeping a journal that I post in only when I'm feeling this way, so that I can get a better idea of what the problem domain is. I know that these sorts of issues feel very particular to the case at hand, but I have a suspicion that there are some very general trends to what sorts of problems cause these feelings of anxiety; identifying this will be helpful because not only will it add familiarity to the problem, it will also provide general guidelines for the solution (which also, in the moment, seem highly specific to the case).

Both of these strategies are not novel. The first is common in the enterprise and the second is common among good creative thinkers of any kind. But only recently have I realized that I'm keeping myself in the dark by trying to suss these things out in my head, rather than plotting them on paper.

>>41
Yes and no. You should, of course, write clean and well structured code, but you shouldn't make it more complex than necessary right at the moment. Liek, don't create factories for simple objects, not matter what "future changes" you have in mind, just don't do it, if it isn't necessary.

>>43
Factories? Enterprise bullshit?

>>44
Factories have their place. Don't be such a pussy.

>>45
Only if you are using a crippled language like Java.
;_;

>>21
>The only thing I don't agree with >>19 is that it's not a matter of optimization. I'm not trying to make it fast; I'm trying to make it clean, where clean is ill-defined. I only know that it's dirty when I look at it. That's the root of the neurosis.

i suffer from this as well and it stops me from ever getting anything done.

i keep trying to tell myself that perfect is the enemy of good but anything not perfect is, as far as my brain is concerned, garbage...

>>47
not a matter of optimization. I'm not trying to make it fast; I'm trying to make it clean

That's still optimization, you have something that works, but you're trying to make it better - optimization.

I do the "First it runs, THEN it runs better" approach, too, and while it has its advantages, you'll sometimes find that if you'd gone for the Best Practices approach from the start, shit would've been easier.

>>49
My fear with that is that I spend too much time conforming the code to best practises over getting to run well (if even runs at all). I've found it much easier to do prototypes then reimplement it to something I could be proud of.

The problem with cheap solutions of mine it that i often dont design a framework/interface and the face lots of trouble when i have to bring my programs in some state.

I have a minor problem where I try to make things 'clever' and I'll sit there planning and coding ignoring other tasks until I'm satisfied.
This probably has something to do with rhe large amount of Java boilerplate code that I had to write in a previous life and saying 'This is easy so why does it take so many lines of code to express it?'

The fact that MS has created LINQ makes this problem even worse as I'm doing a pretty large C# project atm.