I am a long time UNIX system administrator and open source advocate. In recent years my primary focus as been on Linux & FreeBSD systems administration, networking, telecom, and SAN/storage management. I love building infrastructure, tying systems together, creating processes, and bringing people together in support of their technical efforts.
When I can, I try to contribute back to the open source projects either with patches, or by helping others in technical support forums.
Authored Comments
Pretty cool little exploration of test coverage!
I suspect from your detail that you have been disciplined in certain things for a long time. If only all software projects were driven by TDD or at least defensive programming.
I was drawn here from the coverage subject and QA perspective. Being involved in some large code base projects, I was curious to see how you got over 50% coverage, not to mention 100%!
I appreciated your comments on having 100% coverage be obtainable in reasonable time ... however for very large projects with significant technical debt (less discipline), I suspect there's a tipping point where seeking such quality is either impossible or otherwise deemed unworthy of the effort.
But thanks for this, I think we need more articles here about QA efforts.
Hmm, I'll think about it ... see what I can do. I tried a little work in this area some time ago, I ended up doing a lot of config & manual work directly on my Pi, and then using another computer to pull the image off for use on other SD cards. But I don't recall that was straightforward. What many of the distros do with their images is a minimal partition install which is then automatically grown to fill the size of the provided SD card. One might have to start something like this using an existing image (like raspian) as compiling the ppc kernel and managing the boot loader are probably beyond what most people want to get involved with.
Thanks for the comment ... I'll think about if there is some way I could try this with and existing distro.