Tag Archives: DRY

Code Smells

At times it can be a challenge to figure out what’s wrong with an application or component. It’s just a nagging feeling in the back of your mind that something isn’t quite right.

For me, that’s a code smell.

Here are a few that I try to keep an eye out for and avoid at all costs in my development efforts.

  • Rigidity
  • Fragility
  • Immobility
  • Viscosity
  • Needless Complexity
  • Needless Repetition
  • Opacity

I strive for SOLID and DRY. Anything that violates those principles needs to be reviewed. Single-responsibility principle and Liskov substitution principle are biggies for me. Do one thing and do it really well. Wrap everything in an interface. Implementation details should always be hidden behind that interface.

Slow down!

This week has been a killer in some ways.

I went into the office on Monday.  I walked into a project in crisis.  The features were there but the performance wasn’t.  The BAs screwed up by not pushing the users to do a full mock-cycle.  When the forecasting cycle rolled around last week, some of our users opened the app then closed it without doing any work in the tool.   Users complained that the pivot grids were too slow to update after an edit.  Performance in production was crap.

“Umm…  Why did we hear about this issue over a month ago at UAT or during last-months mock-cycle?”  Heads are starting to roll on that side of the fence.

Where am I going with this? Continue reading Slow down!