Making Good Software

A blog by Alberto G (Alberto Gutierrez)

Written by Alberto G

May 22nd, 2009 at 1:20 pm

3 non technical tips to be a better software developer

with 15 comments

There are many articles on Internet with tips on how to become a better developer,聽 most of them focus on promoting learning attitudes like reading articles, books…

In this article I want to approach this subject from a different perspective I am going to present a few unusual tips which I believe will help you to become a better developer.

Be adaptable to any work environment (there is no “I” in team)

You may be a convinced agile practitioner or a waterfall one, but in the team where you are working they are not. Or you may be in a design session where you don’t agree with what has been decided…

You will always face conflicts, a good developer will know when it’s time for discussion and when it’s time to stick with the team and do as best as possible. The worst dynamic for a team, it’s when the people are not aligned in the same direction. (article from Jeff Atwood – about this issue) .

This means that when a decision has been made you shouldn’t use every opportunity, every meeting, to remind your colleagues how wrong you think they are, you will be just mining the team confidence. One of the worst aspects I have observed from software developers is their ego, I’ve seen many times how attitudes like “If it’s not my way, no way” gets in the middle of getting things done.

This doesn’t mean that you don’t have to fight for your opinions and ideas, there is a time to make decisions and that’s when you have to bring all your ideas, after a decision is made, embrace it as if it was your decision, if you can’t is better that you just talk with your manager and you leave that team.

This doesn’t mean either that you have to give up if you see that the team goes in the wrong direction just because a decision has been already made, wait to have evidence that the team’s direction is not the right one, think on how to improve it and show it to your colleagues with a positive attitude

Understand that most of the times everyone is wrong

Drop the attitude “I’m right, You’re not”, both of you are wrong. In the software development industry I’ve seen very few times situations where someone holds all the truth about something, is very likely that in a software discussion all the parts involved are just partially right, a good software developer has to be able to recognize what can be bundle from everyone’s opinions in order to come up with the best possible solution.

Don’t get stressed. Enjoy what you are doing.

I keep reading articles about telling developers to read blogs, books, to code in your spare time, to write your own posts… And it’s not that I don’t think that it won’t help you to be a better software developer, of course it will, but it can also be really bad for you.

I actually wrote an article about how passion is the main difference between a good software developer and an average software developer, but if that passion is pushing you to the point where you are getting stressed, just take one step back.

  • If you are not enjoying it, why are you doing it?
  • If you are not enjoying it, you will eventually quit.

15 Responses to '3 non technical tips to be a better software developer'

Subscribe to comments with RSS or TrackBack to '3 non technical tips to be a better software developer'.

  1. Good Reminders. Thanks.


    23 May 09 at 3:56 pm

  2. // popular today…

    story has entered the popular today section on…

  3. Hah, I totally agree that everyone is wrong. Good Call.


    23 May 09 at 4:55 pm

  4. most of the times everyone is wrong: reminds me of what someone said about religions: “They can’t all be right, but they can all be wrong.”

    John H.

    23 May 09 at 6:37 pm

  5. but..if really you always are less wrong than your partners? 馃槢


    24 May 09 at 4:33 pm

  6. I am doing all bad things in developer team which you think are bad, but the problem is I never did mistake yet in the end. And now I motivated to disagree. I am against all team and what I’ve done without approval never created a bug and the customers always liked.


    24 May 09 at 5:22 pm

  7. I can improve on this. Everybody is NOT wrong. But there are ways to be creatively wrong and get to a point where you are right.

    In general, everyone should be *willing* to be wrong, in other words, not put up a veil of “correctness” just to shut down the discovery process.

    In general, several people who have alot of experience, but are willing to be wrong and brainstorm solutions, will kill a couple of “gurus” who assume they are right and shut everything else down.


    25 May 09 at 8:12 am

  8. […] Gutierrez provides 3 non technical tips to be a better software developer. “The worst dynamic for a team, it鈥檚 when the people are not aligned in the same […]

  9. […] 3 non technical tips to be a better software developer There are many articles on Internet with tips on how to become a better developer,聽 most of them focus on promoting […] […]

  10. […] We all make mistakes, and there’s nothing better than asking some other person to have a quick and informal review in our code to find them, in order to make the reviews,聽 it’s better not to wait until the code is completed, it’s better to ask for reviews whenever some important part of the code has been completed or when a few days have passed from the previous review. no comments yet « Refactoring: The 5 main questions: Why? When? What? How? Who? […]

  11. […] Todos cometemos errores, y no hay nada mejor que preguntar a otra persona para que  nos ayude a tener una revisi贸n r谩pida e informal de nuestro c贸digo. Para hacer estas revisiones, es mejor no esperar hasta que el c贸digo est茅 completo, es mejor preguntar por revisiones en cuanto alguna parte importante del c贸digo se haya completado o cuando hayas pasado unos d铆as desde la 煤ltima revisi贸n. […]

  12. “If you’re still on the fence: grab your favorite earphones, head down to a Best Buy and ask to plug them into a Zune then an iPod and see which one sounds better to you, and which interface makes you smile more. Then you’ll know which is right for you. “

    "Luigi Fulk"

    20 Oct 09 at 11:06 am

  13. […] This post was mentioned on Twitter by Eddie Awad, Eddie Awad, guillaume sempe, Richard Laksana, Markus Eisele and others. Markus Eisele said: RT @eddieawad: 3 non technical tips to be a better software developer […]

  14. awesome tips…

    Harsha M V

    28 May 10 at 11:13 pm

  15. […] 3 non technical tips to be a better software developer […]

Leave a Reply