Gregory Brown

@practicingdev Isn't clean code a medium through which many of of the others manifest? 1/

@pacoworks Definitely not, sadly. They can happen at the same time because of coincidental improvements on right side.

@pacoworks That said, an incredibly messy codebase can hinder, but *always* a symptom of deeper non-code problems.

@practicingdev I can see that point, I've been at both sides for the right and wrong reasons :)

@pacoworks My thought is that "I'd like to clean up the code here so that I can ____" where blank is filled by a goal on right is good

@practicingdev "Clean code" makes for a good book title, the items on the right don't. Uncle Bob discovered that

@victorwu416 Yep, pretty much the motivation for the actual book I ended up writing... titles be damned. :-)

@practicingdev If you haven't already, you can blog/tweetstorm about marketing/communicating your ideas, including diff mediums, titles too

@victorwu416 Very important stuff, even for people who are mostly working on internal systems.

@practicingdev @rballard Writing clean code seemed like such a daunting task, so I'm relieved I don't have to worry about that.

@msavichtweet @rballard I know that's meant as a joke but huge truth there. Clean code rarely the bottleneck.

@practicingdev @rballard *submits awful pull requests to major codebases*

@practicingdev @skamille I *wish* naive programmers asked "how can I write clean code"! But they seem to ask "how can I write FAST code."

@practicingdev I feel it's easier to write clean code when I focus on these "other" things.