Software Craftsman and #CleanCode Evangelist
@pragprog Author of http://java.by-comparison.com #Java #BestPractices
We seem to do a lot of that on this website.Simon Harrer wrote:. . . find a mentor that reviews your code! :-) . . .
Campbell Ritchie wrote:
We seem to do a lot of that on this website.Simon Harrer wrote:. . . find a mentor that reviews your code! :-) . . .
Junilu Lacar wrote:consider also recommending Corey Haines' "Understanding the Four Rules of Simple Design"
Software Craftsman and #CleanCode Evangelist
@pragprog Author of http://java.by-comparison.com #Java #BestPractices
Simon Harrer wrote:
Regarding your other code refactoring: hm, we should have named that boolean variable "useCaptainsLog" or something like that instead. Thanks for the hint. We'll try to get that fixed in the next edition. :-)
Software Craftsman and #CleanCode Evangelist
@pragprog Author of http://java.by-comparison.com #Java #BestPractices
Software Craftsman and #CleanCode Evangelist
@pragprog Author of http://java.by-comparison.com #Java #BestPractices
What about this?I think the old version breaches the suggestion of Winston's that Strings Are Bad, and including the status in the Message object is more object‑oriented.Junilu Lacar wrote:. . . The original code was:
. . .
Campbell Ritchie wrote:What about this?I think the old version breaches the suggestion of Winston's that Strings Are Bad, and including the status in the Message object is more object‑oriented.
Don't get me started about those stupid light bulbs. |