CareerPersonal GrowthProject Management

6 Habits for Ace (or at Least Effective) Developer Skills

If you can be asked to build something, and you develop it at a respectable speed and with few errors—great, you have a valued place as a developer. However, a stereotype—and one that is not entirely unearned—about developers is that they procrastinate way too much. Are you capable of more in your work output? Paul Rubens shares some habits to make you more effective in an article for

  1. Code at least four hours a day.
  2. Fit in with the development team culture.
  3. Code in your spare time.
  4. Learn to write “sloppy” code.
  5. Never stop learning.
  6. Get motivated about your work.

The Developer’s Code

In an eight-hour workday, it might sound odd to “challenge” developers to do four hours of coding. But the reality is that meetings, idle chitchat, email interruptions, minor crises, and (yes) general procrastination cut significantly into how much coding actually gets done. So try to dedicate at least half the day to genuine, uninterrupted coding. That being said, project success depends on you working well as part of a team, not just working hard in isolation. Be considerate of team members and transparent with your work.

Really good coders are the ones who code even when not collecting a paycheck for it. They just like to pursue their own interests and build neat things. Make the time at home to let your imagination go wild. In general, you always want to be learning new things, especially in as disruption-prone an industry as tech. And about the aforementioned “sloppy” code, Peter Nixey, founder and CEO of Copyin, says this:

It doesn’t matter if the code is mucky, repetitious or uses bad naming… Code is a manifestation of a solution, and you can then go and refactor it and make it good. If you try to make it perfect straight away, you can get carried away and achieve very little.

Needless to say, keep an eye out for technical debt anyway. You do need to care about the work you are ultimately producing. If you do not feel any excitement for a project or do not understand why it matters, it is going to affect the speed and quality of your output.

You can view the original article here:

Show More

Leave a Reply


We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.