Comments on: The best piece of coding advice I’ve ever received

By: josh

josh — Fri, 13 Apr 2012 11:36:58 +0000

My favorite code advice is “if you need something >3 times, make it a function/object. Otherwise, re-code it inline.” Without this rule, I 1) underestimate the cost of developing reliable objects; 2) overestimate the effort required to code the same thing a second time; and 3) overestimate the likelihood that I’ll need to that function again (in that language/context) in the future.

By: dsp4

dsp4 — Wed, 08 Jun 2011 03:05:14 +0000

It’s all in the single responsibility principle! Most of the time when I feel my code is inflexible, it’s because I’ve shoehorned too much functionality into the same “thing”.

http://en.wikipedia.org/wiki/Single_responsibility_principle

By: Lumooja

Lumooja — Wed, 23 Mar 2011 00:09:08 +0000

I use this kind of one thing does one thing a lot, because it makes programs much cleaner and more logical. For example today I was writing a simple GUI for Monkey, and I implemented buttons which can stick down, and be hovered. So I created simple hovered, down and stick boolean fields into the Button class, and the rendering code relies on those values only. The update code then handles the logic which is very simple once you have established those “one thing” flags in your class.

By: Jake Birkett

Jake Birkett — Tue, 22 Mar 2011 20:03:50 +0000

I recommend Code Complete 2, epic book.

By: Juuso

Juuso — Tue, 22 Mar 2011 09:40:02 +0000

@Igor: not thing.

@Kamil: thanks for the hint. goes to my potential shopping list

By: Kamil Toszek

Kamil Toszek — Tue, 22 Mar 2011 08:26:56 +0000

I recommend reading “Clean Code: A Handbook of Agile Software Craftsmanship”. You will find this one plus much more advices there. Worth reading really.

By: Igor Hardy

Igor Hardy — Tue, 22 Mar 2011 08:11:29 +0000

What thing should I replace the second “thing” with?