tag:blogger.com,1999:blog-590774712948906419.post5883797865688286165..comments2023-10-27T00:32:39.200-07:00Comments on Pete Miron: Follow your debugging process, stupid. In 10 easy steps.pete mironhttp://www.blogger.com/profile/10573198508233227961noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-590774712948906419.post-27319888732334564532010-06-03T08:01:27.763-07:002010-06-03T08:01:27.763-07:00Totally agree on your points, I added them for com...Totally agree on your points, I added them for completeness. I don't have my system setup to upload a content db daily (which I'll do now), we have continuous integration for automating the unit testing and we're working on getting continuous deploy (already have for 2 services) on all of our systems. that way, 6-10 happen automatically on check-in. My initial goal is 20 minutes for full testing. Deploy to prod in < 30 minutes.<br /><br />Maybe I'll do a future post on automating testing and deploy.pete mironhttps://www.blogger.com/profile/10573198508233227961noreply@blogger.comtag:blogger.com,1999:blog-590774712948906419.post-56505781618990865102010-06-03T07:45:04.830-07:002010-06-03T07:45:04.830-07:00To me it's really all about Step 1...i mean, i...To me it's really all about Step 1...i mean, if you haven't entirely isolated the input (the output is usually how you know there is a defect), you're just looking for a needle in a haystack.<br /><br />If you really want to be efficient, steps 2,4, and 6-10 should be clocked regularly...if it takes you 10 minutes to see if a fix "worked", you're going to waste alot of time no matter how intelligently you approach the problem.ozzyhttps://www.blogger.com/profile/07353666467320898035noreply@blogger.com