Refactoring Pro-Tip: When I’m scanning, I’m not just reading fast, I’m feature-detecting, something the unconscious part of me is very good at doing, especially when the code helps. Part of the made, the making, and the maker as a guiding theme for me is the idea of "leaning in" to the strengths of my maker […]
Refactoring Pro-Tip: Scanning Isn’t Just Fast Reading Read More »
Refactoring Pro-Tip: I optimize my code for scannability, readability, and writeability in that order. I won’t argue my case in detail, there’s a video if you’d rather watch me make it instead of reading it, and I’ll just sketch the case briefly here in the muse. http://geepawhill.org/optimizing-a-program-and-programming/ When I’m coding, I notice that I spend
Refactoring Pro-Tip: I Optimize Scannability, Then Readability, Then Writability Read More »
A thing that happens to me a lot. I want to say, "Yeah, that’s not how that works," about some over-simple explanation, usually something around using inorganic reasoning about humans. But when I go there, I know we’re gonna go instantly to vast areas of study & insight that most folks aren’t comfortable with. And
The Whole Geek: Geekery Is Just The Tip Of The Iceberg Read More »
Refactoring Pro-Tip: When I tackle a long method, the first thing I do is make my local variables maximally local. Consider this psuedo-code. It’s basic stuff, I’m betting virtually any geek can read it, but if not, lemme know. longMethod( int y ) { int x; x = 0; // … // IRRELEVANCY #0: 87
Refactoring Pro-Tip: Making Local Variables Maximally Local Read More »
Refactoring Pro-Tip: I use naming, isolation, and noise-filtering as strategies to keep the coder’s intention at my fingertips. (I’m actually jonesing to write some geeky material in this series, but I’ve got one more of these pesky abstract philosophy things before I can get there.) First, a silly line from a silly movie, Airplane, which
Refactoring Pro-Tip: Naming, Isolation, and Noise-Filtering Read More »
Refactoring Pro-Tip: The triggering events for refactoring vary, but the reason we refactor at all is the same each time, regardless of occasion: we refactor to enable change. The most obvious and direct occasion for a refactoring is this: I want to add new functionality and preserve old functionality, and it will be easier to
Refactoring Pro-Tip: Refactor to Enable Change Read More »
Refactoring Pro-Tip: Terrible code is not a good excuse to be mean, because terrible code is not well-correlated with having been written by terrible people. Look, y’all, it’s me, here. I love a good rant as much as the next Old Testament prophet, surely you know this. But . . . but . . .
Refactoring Pro-Tip: Terrible Code Doesn’t Mean Terrible People Read More »
I’ve made mention here and there of "the whole geek". I’d like to take a little time and lay out the idea. (There’s a video coming, too, expect it to be strange.) In our conversations about geek culture, I’ve tried to make my sense of its thinness as clear as I can. One of the
Bring The Whole Geek! Read More »
Refactoring Pro-Tip: "Easiest Nearest Owwie First". When facing especially weak code, it’s easy to feel daunted; there just seems so much wrong with it. To get my mojo on, I find the simplest infelicity to fix, I fix it. Then I do it again. Everyone encounters code from time to time that she does not
Refactoring Pro-Tip: Easiest Nearest Owwie First Read More »
The geek trades suffer from an extreme paucity of culture, and a great many of the issues we see are the direct result of that cultural thinness. Culture is the air we breathe. Though we’re often quite unaware of it, it surrounds us, it shapes what we see & think & feel, and it is
Culture Starch: Thick and Thin Redux Read More »
