A day with only one issue was considered a good one! Now we probably only see a couple issues a month. When it was just me as the only QC person in production, I remember production issue response would eat up most of my day. Whatever build is held up, is probably going to go out of stock in the next few hours, and so it's very important that we get up and programming immediately!īack in the day (2008-ish), this was an hourly occurrence. It's usually pretty time sensitive, because we run such a lean ship down in production. If production sees any issues at all, they call us up, and we try and solve the issue at that moment. This not only includes the test jigs that we design, but also includes making sure that their windows desktop machines are working and have up to date (or hacked and working) drivers for all our testing needs. One of our responsibilities is to design, build, document, and maintain the testing equipment for production. My team and I are known as Quality Control here at SparkFun. We are careful with our equipment, but after programming tens of thousands of ICs, you have to expect some wonkiness both in the hardware and the software. Overall, the MKII programmers have done quite well, considering how long and how much we've used them. Share on Twitter Share on Facebook Pin It Pain Points w/ the AVR ISP MKII

Avrisp mkii drivers