Personal Productivity Stack Exchange is a question and answer site for people wanting to improve their personal productivity. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am programmer and I want to be more productive in my profession. I was searching for how to do this and in many places I encountered the idea that I should "refactor" myself.

So, how can I "refactor" myself to become more productive?

share|improve this question
Are you sure 'refactor' refers to personal productivity and not code? – Jordan Apr 16 '13 at 13:03
@Yoel, sorry if i made any confusion. I mean personal productive which includes coding. If you think still my question creates confusion, please feel free to edit my question. – Md. Mahbubur R. Aaman Apr 16 '13 at 13:06
Maybe a link to this refactoring idea? – JeffO Apr 16 '13 at 17:57
Perhaps the OP means this? – THelper Apr 17 '13 at 8:36
@THelper, Nice resource. – Md. Mahbubur R. Aaman Apr 17 '13 at 8:42

You're a programmer so look at the different strategies to refactor code and see if they apply to your behaviors.

Examples: Repeated Code. Are you repeating things unecessarily like checking voice and email? Abstraction Are there tasks you're doing in one place that you could do in another? Maybe you're sending someone a question in an email that could wait until a meeting or vice versa?

Go back to your calendars and todo lists and see how you're using your time. Are you trying to do the more difficult parts of programming when you are at your best? If you're required to report to the office early, but you're still trying to wake up, this could be the time to do some of the easier things.

share|improve this answer
+1 for good points. – Md. Mahbubur R. Aaman Apr 17 '13 at 7:19

To improve your productivity as a programmer, you should keep a list of best coding practices to adopt and make sure you apply it everytime you work on a project. This include:

  • Use Specifications documents

  • Usage of Source code Control tools

  • Simplified one step build procedure
  • Keeping track of your bugs(may be in a Database)
  • Fix buugs before writing new code
  • Keep an up to date schedule etc ..

You can find the complete list on Joel Test : 12 Steps

Hope it helps.

share|improve this answer
+1 for nice answer. – Md. Mahbubur R. Aaman Apr 17 '13 at 7:20

The question you should ask yourself first is what are your weak spots? In which areas do you think you are less productive than others? What aspects of yourself or your life do you dislike? Don't limit yourself by looking only at how you are writing code, also look at all the other things your do; e.g. drawing up specifications, your contribution to meetings, presentations you give, etc.

I think a lot of posts on this site can help you improve certain aspects of yourself, so once you identify a habit or working method you want to change, come back to this site and ask people for advice on how to change this (or first search if a similar question has been asked already).

One note of warning; don't try to change multiple things at once because change requires energy and may lead to stress. Take it one step at a time. Changing a habit takes willpower, and willpower is a limited resource.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.