Hey Dave, I'll contact you offline to ask you some questions about this. There's some questions that I have about your setup that you probably don't want to post to a public blog :-)

• 1 week ago

Nice post. I saw all the #motrinmoms tweets, but I didn't get the full sense of what was going on. I think it also goes to show that what's funny in the brainstorming room doesn't always cut it in the public.

• 2 weeks ago

I like CodeIgniter for this reason as well. Doing any kind of consumer facing web apps need a strong presentation layer with the ability to tweak and update features quickly. My experience with Wicket is that it's really full featured on the back end side, but when you get to the presentation layer, the built in components can be cumbersome to extend (see my wicket dojo post http://www.electromute.com/posts/2008/06/wicket-d...). You end up just wanting to not use the built in components. Sounds like .NET may have similar issues, but my friend Sass (see above) is a .NET expert and can comment on that.

• 2 weeks ago

Hey Caroline, this is a great post and thanks for the shout out! I actually do have a Master's degree in Women's Studies, but as you know I write code, so you wouldn't guess it. I think the point is that knowing someone that can draw on a wide area of expertise and experience is also an indicator that they can listen and synthesize new information about you in order to help coach.

• 2 weeks ago

Jonathan, thanks so much for stopping by! Yes, good suggestion on using Models. That is the beauty of Wicket. Here's a link to Wicket in Action: http://wicketinaction.com/

• 5 weeks ago