Tag Info

Hot answers tagged

8

In programming, bugs are a fact of life. No developer should expect zero bugs. Large applications have thousands or millions of bugs. Instead plan what to do with the bugs you discover. learn from them. Try not to make the same mistakes again understand why you make these mistakes. Is it a particular class of bugs? Perhaps you need some training in that ...


6

Unless it's a foundational library building project, I think writing perfect code is not fruitful. Since you are asking the question here, you surely agree with me on this. I used to struggle with similar symptoms. I do have perfectionism, and I love fast yet general code, but at the same time I acknowledge leaky abstraction and the evil premature ...


4

Here are some techniques to help: The first is the easiest. Keep a daily journal and write what you are grateful for every day. This starts to refocus your mind on the positive. If you feel able to do this, writing what you are grateful for in a public forum like Facebook or a blog is even better becasue you will get amazing feedback and inspire others to ...


4

For programming, are you writing unit tests? The unit tests are supposed to catch the bugs even before you commit. It's also harder to make the same error in both the code and the test. (unless it is a logic error.)


3

It would help if you described more precisely what exactly is the problem for you. More precise questions often lead to better answers. It's easier to change something if you measure it. So you could start by living one week as usual, just with a pen and paper in your hand, and writing down as many interruptions as you can -- time of start, time of end, who ...


3

If you notoriously code sloppily, there are some things you can do to improve the situation: Use test-driven development (TDD). It is great for avoiding bugs, as it requires you to write tests for your classes and functions. Avoid interpreted and loosely typed languages as programs written in such languages may contain lots of bugs which only occur during ...


2

I think it is a matter of my priorities: Have I been given a deadline by a boss or client? Am I unable to reschedule this task? e.g. Can't wait until next week because I'm at a conference. There is no negative history of contacting this other person. I'd be less inclined to automatically call, but it is something to think about. A big problem in many ...


2

When you read something difficult, like a legal agreement, it's difficult to understand every word. But you read the whole thing first, then go back to understand the words. Similarly, when you code something complicated, it's difficult to keep it bug free. Just keep doing it, finish what you're doing, note down the bugs, and go back and fix the bugs. ...


2

The first thing to understand is that you can get over your past experiences, and you will get over them if you take the appropriate steps. It may take time, and might not always be comfortable, but it will be easier than you expect. Note that this is not empty encouragement: I've been in a similar situation to you, and I'm now making a success of my life. ...


2

its ok, to have write bugs, till they can be detected, resolved and not repeated again..., So learn from your bugs, and if possible document the bugs that you create, it ll help you not to repeat it again...


2

Plan for the long term. Decide what you want to accomplish in your life and how you expect to get there. I have a personal to do list for the weekend and weekday nights, including a few things for long term goals. Usually, I'll schedule one weekend off or several nights off just to waste time, do nothing, and have fun. Refuse anything outside those ...


1

That really sounds exactly like OCD, including the "fear" or superstition about certain letters or letter combinations. Do these sorts of problems manifest outside of writing code? Either way, though, I think what you are experiencing goes beyond perfectionism regarding coding. I really urge you to consult a professional, as OCD and anxiety in general (OCD ...


1

Considering short bursts you may try http://en.wikipedia.org/wiki/Pomodoro_Technique. After you start using it you will acquire a habit of concentration during fixed periods of time. Nothing will distract you then because your motivation to concentrate will increase greatly.


1

I'd say you're lucky your problem is consistency rather than, say, understanding. The fix is repetition, which some may see as lost time but as you say it improves problem solving ability. Unfortunately it can be a bit boring, so one solution is to get problem sets that are -so- simple you don't notice how long it takes. Unfortunately I don't have any ...


1

I am a programmer, I work for others and I have my own products, too. I think you are passionate about programming, so the other problems can be easily solved. I recommend you to follow SDLC (software development life cycle) if your project is not too small. Never start coding right away without a crystal clear understanding of the overall system and what ...


1

Another possibility is to reduce the scope of the project. Pare the project down to the absolute bare essentials and build that. Remove any embellishment, and bells and whistles and instead concentrate on the core. That way you end up with something simple and elegant - the kind of thing you're trying to achieve by rewriting and restructuring.


1

You believe that you may suffer from Obsessive compulsive disorder. It is best treated with Cognitive behavioral therapy. In your case, it means subjecting you to the anxiety that results from not rewriting your code. Start with something small, then leave larger parts of your code as is. In this way, you learn that you don’t need the rewriting ritual to get ...



Only top voted, non community-wiki answers of a minimum length are eligible