I'm more of a software guy than fiddly with hardware -- I can run a network or install a new hard drive, but I'd rather be writing code, and let the hardware take care of itself. So I'm not an obvious candidate to be playing with 3D printers at this stage in their evolution, when they're so finicky and require so much calibration, troubleshooting, and modification. And unlike many in the community, I would be very eager for a plug-and-play, just-plain-works 3D printer so I could spend my time in design software inventing things to print, instead of playing with M3 screws and cable ties.
So why am I in this? Well, first of all, I can't wait for those plug-and-play 3D printers, I want to play now, and want it enough to get out of my comfort zone. And to help, in a tiny, single-voice-in-the-crowd way, to shape where it'll go. Not my first time doing that -- I was one of the contributors who shaped the most popular home automation software in the industry, for instance, though my contributions are only known to a handful of people these days. Second of all, I'm hoping that, by sitting on the outer edge of the envelope of how much tinkering savvy you need to do this, I can help widen that envelope. I can figure out what the people better at this than me are talking about, then translate that out for the people a little less hardware-savvy than me. Which is exactly why I'm on this wiki -- to write directions that widen the target audience to include those who still know what pliers or a hex wrench is, but maybe don't know what a Bowden or a JST is yet. (Maybe someone will come along later who can expand the frontier even farther for those who don't know what pliers are, though I think 3D printers are going to have to get a lot smarter before we can push the frontier that far.)
Because of this goal, it's vitally important for me to get input from everyone else. If I'm at the edge, I need the people who know more than me to correct me, teach me, be patient with me, and blaze trails that I can follow behind, widening and making a bit safer. And I need the people who were scared off by the jargon and tech savvy requirements to look at my stuff and tell me where it fails to go far enough to make things both understandable and approachable for them. So whatever you've seen I wrote, please, please, please tell me how to make it better.
Here's what I've contributed so far: