Hey friends! Today, I sent Sebastian a talk that's made me rethink my development style and I realized I should open it up to a wider audience:
https://www.youtube.com/watch?v=f84n5oFoZBc Note: it's development-centric, but not development-specific. The presenter provides an explicit problem solving strategy to take when solving hard problems and provides some important questions to ask – e.g. what are the facts surrounding the problem? What are the constraints? What don't you know yet? Even if you disagree with the approach of the presenter, I think it's beneficial to have an explicit problem-solving strategy. In this or another talk, the presenter mentions that he feels many bugs come from having a poor-conception of the problem. After applying an explicit strategy to problem solving, it's been insightful to have a better concept of what I'm building before I start trying to build it and (granted, it's still with a small sample size) I feel it's produced better code with fewer bugs. Here are some notes on the talk [1] but it's unclear how helpful they are without watching the video. Personally, I've copied this document, simplified it, and have been adapting it for what approach what works for me. Enjoy! - Mike (:mcomella) [1]: http://willchen.me/hammock-driven-development
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
