Breakpoints12:55 with Craig Dennis
Let's take on our first issue. We'll use some powerful breakpoint tricks to get through things.
Sample Email about tests
Things are going good, and we are cruising through the issues you have filed for us. We're getting in there and learning how things are working. I am really enjoying your FlashCard app, I'm certain your students will love it.
We did uncover a slight snag in the plans. A common development practice is to write code that actually verifies that the application is working the way that it was intended. This practice is called testing. Unfortunately the developers writing your initial prototype opted not to follow this process.
The good news is that we can fix this and start employing the testing practice moving forward. The bad news is that it will take additional time, and I do realize you are on a tight budget. My colleague and I are very fond of testing, and employ it on every project we create. We do this because it helps make sure that any change we make did not break any other part of the application. Every feature we write will be thoroughly tested and that allows other developers to understand how your requests are supposed to be working. Seeing as you don't have a specific team of Quality Assurance people, there are bound to be possible issues not yet reported.
We have already spent some more time than we would normally need to if we had tests in place. In the future, it will for sure speed up development. However, setting up tests is indeed an upfront investment, and is completely your call.
I estimate we can get your application tested in 2 days, and again like I said I understand your tight budget, I'd just like to make sure your application is healthy and you have the ability to rapidly iterate on your awesome project.
Let me know your thoughts. Happy to discuss it more!
PS. There's a great motion example on Treehouse around the 3 minute mark ;)
You need to sign up for Treehouse in order to download course files.Sign up