Skip to main content

At SCNA: Part 4

This is the last post in a multi-part series about the Software Craftsmanship North America conference in Chicago.

Combinator-based design in functional programming: Michael Feathers

I'll be honest - I didn't really pick up a central theme on this one.  It was interesting and I took some ideas from it, but I can't really summarize it well..

My take-aways:
  • We have a settled idea of OO, but not yet one of functional programming - the "best practices" are still evolving.
  • Haskell is a good functional language to learn with - it forces you to be functional.
  • Duplicating objects at runtime is no longer evil.  Duplicating code still is.
  • OO increases encapsulation and understandability.  Functional increases immutability and reduces the number of moving parts.

Panel Discussion: Bob Martin, Michael Feathers, Chad Fowler and Enrique Comba Riepenhausen

This was my favorite session of the conference.  Instead of my interpretation of what the presenter was trying to say, here are my favorite quotes from the session, grouped by theme.

On the image we project as developers 
"We are not a bunch of twinkie-eating guys who don't are about their customers.  We are professionals.  That perception is what has to change."
 - Bob Martin

"Programming shouldn't be a 'lifestyle choice', particularly when you reinforce negative 'nerd' stereotypes."
 - Chad Fowler

On the "craftsmanship" movement
"We don't have to evangelize.  What we're doing is enough.  It does not have to include all developers."
 - Chad Fowler

"...but we should welcome everyone who wants to come."
 - Enrique Comba Riepenhausen

On practicing software development
"Coding is relaxing.  When I wake up in the middle of the night and sit down to code, it's refreshing."
 - Michael Feathers

"...I try to practice four hours per day.  Doing that is refreshing."
 - Enrique Comba Riepenhausen

"I don't do anything I have to do after 5:00 PM.  Only things I want to do."
 - Bob Martin

Wrap-up: Corey Haines

In a lot of ways, this conference is Corey's baby.  He is (as far as I know) the driving force behind the "craftsmanship movement".   (Credit where credit is due: Uncle Bob Martin's cohorts were the organizers of the event, and they did a great job.)

Corey's talk  can be summed up by his own words: "What will allow us to take over the world?"

My take-aways:
  • Happiness is what sets craftsman apart from non-craftsman.  if you're not happy, figure out why not & change that.
  • "Division and negativity are what will keeps us from total world domination."
  • Stay positive about yourself, your work and your craft.  Above all, stop bitching about other developers and our customers.  More civility is needed, and we can all contribute to that!

 Great stuff.  I can't wait for next year.
Post a Comment

Popular posts from this blog

Agile Performance Management: Why Performance Reviews Suck

Many thanks to Mary Poppendieck, who wrote about this topic in 2004, and proposed a comprehensive solution.  She is the inspiration for much of my thinking on this subject.  She is also a better writer than I am a cartoonist.

Performance reviews suck.  I don't know of anyone who goes into their appraisal without some trepidation.  Your boss is guaranteed spring some surprise criticism on you that is ill-informed or misses the point as you see it.  It's a real challenge not to get defensive about that.

The only thing that makes your own performance review suck less is having to give them.  As a manager, I have dished out quite a few, and some of them went pretty badly.  (To the people at my first management job: Thanks for helping me learn how to get better at them.  Your sacrifice was not in vain.)  Since then, receiving one isn't nearly as gut-wrenching, if only because I try to make it easier for the guy on the other side of the desk.  I've been there, and I know how …

Windows 10 Driver Issue with Falcon / Z-77 Keyboard

Windows 10 has an issue with this mechanical keyboard (which works great, BTW).  It's a Chinese-made keyboard (aren't they all?), but it doesn't have much English-language support.

I captured a few screen shots of how to fix it in case someone else has the same problem.  (I got the instructions off of Tom's Hardware, but it doesn't have screen shots & isn't clear on some of the details.)

First, open up Device Manager and select the controller under USB controllers (not under keyboards).

Next, choose "update driver" from the Drivers tab.
Then choose the "browse" option (search doesn't find anything).
Then select "Let me pick from available drivers on my computer."
Finally, switch it from the ND device (which is the wrong one) to the generic USB compatible one (which works fine on my machine).

You might want to clip these instructions into your favorite notes software because:

You need to do this for each USB port you plug in…

Do. Not. Optimize.

You've probably heard this quote before:
Premature optimization is the root of all evil.
 - Tony Hoare
Speculative optimization is always wasted time.  In the absence of an actual performance problem, you're just burning time that could be better spent on refactoring your code to make it clearer.  This is exacerbated because performance-optimized code is usually harder to read than code which hasn't received such treatment.

Here is what you're doing when you optimize:
Adding code that now must be maintained.Obfuscating the existing code.Spending time writing code that doesn't add value. But what's that you say?  You have the experience and know-how to decide when optimization is needed?  Maybe, but probably not.   The people at Sun and Oracle may or may not be smarter than  you or me, but they certainly know more about optimizing Java bytecode than we do.

For example, some people think that having a large number of classes is slower than the alternative.  This …