10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
From Good to Great Developer
Presented by
Chris Hedgate
on
Oct 16, 2009
Length 00:39:56
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
Chris Hedgate makes a difference between a good and a great developer. The former writes code quickly, knows how to solve problems, but his code tends to be hard to maintain on the long run. The good developer keeps an eye on the future trying to make sure the code evolves cleanly. Hedgate advices on how to move from good to great.
Bio
Chris Hedgate coaches software development teams, sometimes working as coach, using retrospectives to help teams improve their dynamics and collaboration, and other times he works as a player-coach, working along with a team while also mentoring the team members.
About the conference
Jfokus is the largest annual conference for everyone who works with Java in Sweden. At Jfokus you will have an unique opportunity to keep yourself updated with the latest development of the Java platform through numerous interesting sessions. Jfokus gather rock-star speakers, both from Sweden and internationally. The focus is system development with Java and surrounding techniques like dynamic languages and agile methodologies. Jfokus is the best way for you to get the latest trends and buzz about Java from people who live and breathe technology on a daily basis.
Chris Hedgate makes a difference between a good and a great developer. The former writes code quickly, knows how to solve problems, but his code tends to be hard to maintain on the long run. The good developer keeps an eye on the future trying to make sure the code evolves cleanly. Hedgate advices on how to move from good to great.
Bio
Chris Hedgate coaches software development teams, sometimes working as coach, using retrospectives to help teams improve their dynamics and collaboration, and other times he works as a player-coach, working along with a team while also mentoring the team members.
About the conference
Jfokus is the largest annual conference for everyone who works with Java in Sweden. At Jfokus you will have an unique opportunity to keep yourself updated with the latest development of the Java platform through numerous interesting sessions. Jfokus gather rock-star speakers, both from Sweden and internationally. The focus is system development with Java and surrounding techniques like dynamic languages and agile methodologies. Jfokus is the best way for you to get the latest trends and buzz about Java from people who live and breathe technology on a daily basis.
RelatedVendorContent
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
Case Study: IBM's Agile Transformation
18 agile and lean practices for effective software development governance
Related Sponsor
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
- This article is part of a featured topic series on Agile Techniques and also Agile
- See more Agile Techniques content at: http://www.infoq.com/agile_techniques
- See more Agile content at: http://www.infoq.com/agile
- Other recent content items in this topic
pics
by
Kevin Wong
Posted
'bout the presentation
by
Fabio Pupo
Posted
would like to have seen...
by
Jason Little
Posted
Re: would like to have seen...
by
Fabio Pupo
Posted
"Copy, Paste, Modify" is not always bad
by
Oliver Doepner
Posted
Good presentation
by
Steven Zhang
Posted
Re: Good presentation
by
Steven Zhang
Posted
I love InfoQ but...
by
Shady Mostafa
Posted
-
Anybody work with female developers that look like the ones shown in those pics? I'd be smiling too.
Good presentation. But people care about code or they don't. In my experience you can't compel them to care. Just fire them. -
Very good, great! it's simple, clean, has focus. All developer and team guy should see that.
-
Would have been great to see the live coding, the code shown in the preso material was jumbled and not readable. Otherwise this was a great insight!
-
Jason .. I got the presentation on his blog:
www.hedgate.net/talks/from-good-to-great-develo...
There are the resources, the presentation and the code available! -
The presenter is suggesting is that constantly refactoring your code to reduce/avoid duplication helps to make it easier to maintain.
But sometimes the opposite can be true: "Copy, paste and modify" allows code to grow organically in the (different) directions that its uses might require (in the future).
Trying to force code sharing between several pieces of functionality can introduce several problems:
- Fixing a bug for one use can break another use
- Code has to be more complex to serve various uses
- More indirection makes code harder to understand
- Ongoing Refactoring can easily introduce bugs
I guess the interesting challenge is to know when several code pieces "have to do exactly the same thing" and therefore should share the code (in a common method or class) - as opposed to code pieces that look similar but should be kept separate and allowed to grow in different directions. -
I like this presentation, simple and straightforward. I've been trying to write the clean code improve the design, but I am frustrated with my colleagues and my manager, they don't understand the importance of the clean code. This presentation give me a solution: first inspire them.
I also like the concept of 4-stage learning model. With another 3-stage model called shu-ha-ri which is introduced by Alistar CockBurn and a 5-stage dreyfus model which is introduced by Andy Hunt, right now I have a more deeper understanding for the learning models. -
I posted my full comments in my blog:
code-dojo.blogspot.com/2009/10/from-good-to-gre... -
Guys, what's the point of having such a great session when I can't see the code.. Through out Chris's demos I'm imagining what the code looks like & even imagining his changes..
Why not focus the cam on the screen/presentation when he does the demos?
8 comments
Watch Thread Reply