Jason Gorman's blog: Agile Software Process Improvement
Jason Gorman's blog: Agile Software Process Improvement
Website:
Description:
Jason Gorman's insights
Last update:
1 year 26 weeks ago
Codemanship's Code Smell Of The Week - Lazy Classes Part II
Submitted by jason@parlezuml.com (Jason Gorman) on Fri, 30/07/2010 - 14:13.Jason Gorman quickly illustrates how to apply the Collapse Heirarchy refactoring to eliminate a lazy subclass
Codemanship's Code Smell Of The Week - Lazy Classes (Part I)
Submitted by jason@parlezuml.com (Jason Gorman) on Thu, 29/07/2010 - 11:47.Lazy classes add little value for the maintanance burden they incur. In this example, Jason Gorman illustrates how to safely inline a lazy class into its containing class.
Register For Software Craftsmanship 2010
Submitted by jason@parlezuml.com (Jason Gorman) on Tue, 20/07/2010 - 20:48.Finally! You took your time, Jason!
Yes, Software Craftsmanship 2010 is open for business. You can register with your credit/debit card online for the jolly reasonable price of 85 quid. And, even better, all the profits from registration are going directly to help Bletchley Park.
We're also accepting submissions for...
Yes, Software Craftsmanship 2010 is open for business. You can register with your credit/debit card online for the jolly reasonable price of 85 quid. And, even better, all the profits from registration are going directly to help Bletchley Park.
We're also accepting submissions for...
Codemanship's Code Smell Of The Week - Inappropriate Intimacy
Submitted by jason@parlezuml.com (Jason Gorman) on Mon, 19/07/2010 - 12:25.When two classes exhibit an unhealthy fascination with each other's bits, we call the Inappropriate Intimacy. It's essentially bi-directional feature envy. In this video, Jason Gorman demonstrates hot to change a bi-directional relationship into a uni-directional relationship and eliminate the feature envy on both sides.
Codemanship's Code Smell Of The Week - Switch Statements
Submitted by jason@parlezuml.com (Jason Gorman) on Fri, 16/07/2010 - 15:21.Switch statements are bad from an OO design standpoint. Not only because they're basically big nested IF statements, but because they have a tendency to grow. A refactored switch statement would exploit polymorphism, which is the OO way to make decisions about how to do specific "stuff" at run time.
Jason Gorman demonstrates how he refactors a simple switch statement into a polymorphic OO solution (like the Strategy Pattern).
Part I
Jason Gorman demonstrates how he refactors a simple switch statement into a polymorphic OO solution (like the Strategy Pattern).
Part I
Amazing Value Offer Ends Tomorrow - £2,400-worth of Software Craftsmanship Training For Under £400
Submitted by jason@parlezuml.com (Jason Gorman) on Thu, 15/07/2010 - 15:03.Just a quick reminder about the amazing deal I'm offering - never to be repated - which ends this weekend with the final TDD master class of the summer.
Book a place on the TDD and Refactoring master classes, and your place on the OO design workshop on August 21-22 will be absolutely FREE.
Each course normally costs £799, so you'll make a saving of £2000 if you book all on all three before midnight tomorrow.
Not only that, but next weekend's...
Book a place on the TDD and Refactoring master classes, and your place on the OO design workshop on August 21-22 will be absolutely FREE.
Each course normally costs £799, so you'll make a saving of £2000 if you book all on all three before midnight tomorrow.
Not only that, but next weekend's...
Codemanship's Code Smell Of The Week - Data Clumps
Submitted by jason@parlezuml.com (Jason Gorman) on Thu, 15/07/2010 - 14:49.When we see fields that always seem to be used together (e.g., passed together as mathod parameters, or used together in methods), this gives a strong indication that these fields really belong in their own class.
Jason Gorman (yes, that's me) illustrates how to refactor a data clump by extracting a class containing those fields and then moving the behaviour that accesses them into the new class.
Jason Gorman (yes, that's me) illustrates how to refactor a data clump by extracting a class containing those fields and then moving the behaviour that accesses them into the new class.
The Customer Holds The Key To The City of Agile
Submitted by jason@parlezuml.com (Jason Gorman) on Wed, 14/07/2010 - 21:24.We all gripe and moan about how hard it is to get our customers to "go Agile" and play their role effectively. And it's an important role. Indeed, the customer is the key to Agile.
We have a hard sell on our hands changing the customer's mindset to embrace Agile values. But when it's the other way around - which, of course, it very rarely is - the customer doesn't have to do much to pretty much force teams to be Agile.
For example, if I was...
We have a hard sell on our hands changing the customer's mindset to embrace Agile values. But when it's the other way around - which, of course, it very rarely is - the customer doesn't have to do much to pretty much force teams to be Agile.
For example, if I was...