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.
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.
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.
Good presentation. But people care about code or they don't. In my experience you can't compel them to care. Just fire them.
'bout the presentation
would like to have seen...
Re: would like to have seen...
There are the resources, the presentation and the code available!
"Copy, Paste, Modify" is not always bad
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 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.
Re: Good presentation