Comments on: 3 non technical tips to be a better software developer

By: 5 top non-technical mistakes made by programmers | Making Good Software | the leading lady

Thu, 17 Jun 2010 13:46:41 +0000

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

By: Harsha M V

Harsha M V — Sat, 29 May 2010 06:13:40 +0000

awesome tips…

By: Tweets that mention 3 non technical tips to be a better software developer | Making Good Software -- Topsy.com

Mon, 01 Feb 2010 02:19:24 +0000

[...] 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 http://ping.fm/Veees [...]

By: "Luigi Fulk"

"Luigi Fulk" — Tue, 20 Oct 2009 18:06:24 +0000

“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. “

By: Los 10 mandamientos para crear buen código - Angel "Java" Lopez

Los 10 mandamientos para crear buen código - Angel "Java" Lopez — Sun, 09 Aug 2009 15:13:13 +0000

[...] 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. [...]

By: 10 commandments for creating good code « Making Good Software

10 commandments for creating good code « Making Good Software — Thu, 04 Jun 2009 23:29:23 +0000

[...] 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? [...]

By: Top Posts « WordPress.com

Top Posts « WordPress.com — Tue, 26 May 2009 00:10:27 +0000

[...] 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 [...] [...]

By: Weekly Link Post 95 « Rhonda Tipton’s WebLog

Weekly Link Post 95 « Rhonda Tipton’s WebLog — Mon, 25 May 2009 22:23:58 +0000

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

By: bob

bob — Mon, 25 May 2009 08:12:03 +0000

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.

By: Andy

Andy — Sun, 24 May 2009 17:22:18 +0000

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.