Comments on: Approaching another programmer about their code quality

By: Rachel

Rachel — Wed, 11 Jul 2012 13:20:34 +0000

I actually wrote the top answer to that first link, and its the reason this blog post exists today :)

By: haylem

haylem — Fri, 06 Jul 2012 17:50:31 +0000

Oh and:

http://programmers.stackexchange.com/questions/113593/how-can-i-tactfully-suggest-improvements-to-others-badly-designed-code-during-r/113597

By: haylem

haylem — Fri, 06 Jul 2012 17:47:51 +0000

Or directly taken from P.SE:

🙂

By: Sean Bernardino

Sean Bernardino — Fri, 06 Jul 2012 11:22:10 +0000

Great post. I'm not actually in a programming domain but can see how this can be tweaked to be applicable to my field.

By: cs_brandt

cs_brandt — Thu, 05 Jul 2012 18:28:56 +0000

if you have to take all those steps you have already let the problem become bigger than it has to be. Just approach the fellow program the first time you spot the problem and offer suggestions or spark a conversation about what you think is wrong and offer better suggestions to do xyz.

Personally I would be grateful to be on a team where everyone is open because that means I am always learning

By: Tynam

Tynam — Tue, 03 Jul 2012 12:27:08 +0000

@Brandon is exactly right. The hardest part about being a programmer is constantly realising that I suck at coding in (some situation about which I know not-enough), and my ability to produce good code in (some other framework) is irrelevant. Some days I want 'tell me how to do better' painted on my forehead.

By: Brandon

Brandon — Tue, 03 Jul 2012 11:04:46 +0000

This is sound advice. Maybe we who really would like to learn should state from the start our willingness to accept criticism. Maybe we can wear "Feedback is Appreciated" shirts.