For some reason, I've been obsessed with Behavio(u)r Driven Development for the last few months. I've only been doing TDD for a little over a year, and I am totally loving what it's done for my design, so why would I look for something else? It's NOT something else. Dave Astels says, "Behavior Driven Development is what you are doing already if you are doing Test Driven Development very well." BDD is how we're supposed to be doing Test Driven Development. The problems that people end up having with ......
QUICK THOUGHT: The engineering practices in Extreme Programming (Like TDD, Pair Programming, etc) can lead you to improving your code. But it won't do it for you. TDD will point out design flaws, but it won't GIVE you good design skills. If you write lousy code, you'll find it very hard to maintain practicing XP, but XP won't MAKE your code better. You still have to do it. You STILL have to read books, write code and share with other developers.
KAIZEN!
~Lee
Life is sometimes sweeter than we realize. Sometimes we just forget to see it. We complain about work, bills, co-workers and spouses and sometimes forget to look at how awesome our lives really are. I LOVE being a programmer. I've done a lot of different jobs and I didn't come to programming until my mid-to-late twenties, so I've experienced some really crappy jobs that paid even crappier. At my current job, I was given the freedom to choose how I would develop this new project, what language, what ......
Originally, I had used JP's method from this MSDN article for connecting the Views and Presenters. It works very well except it leads to a lot of very similar code. 1: public partial class _default : Page, IDefaultView 2: { 3: private DefaultPresenter _presenter; 4: protected override void OnInit(EventArgs e) 5: { 6: base.OnInit(e); 7: _presenter = new DefaultPresenter(this); 8: } 9: // other properties and methods for the IDefaultView interface 10: } Then I came across David Hayden's article on ......