Who: Currently I'm a consultant supporting 11 local sites, coordinating with 3 others who support 80 sites total. I have access to the Radiant KB, 3rd tier support, RSIMS, and work with both enterprise and stand alone systems. I know very little about aloha as a whole because it's only 1 of 6 hats I wear, but I know as much as our reseller, who is good (East Bay Cash Register) and most techs I've met.
I started with a strong tech background. For Aloha, I have been extensively self-trained, trained by senior in-house techs, worked closely with integrators, and, apparently, am a certified aloha reseller (tech) after a two day (2.5?) class with a Radiant trainer. And been to a user conference.
PRELUDE - PREREQUISITES
The most important thing, by far, is a strong background in (windows) tech. The following presumes you are good at networking and windows OS at a bare minimum. Professional-good, not enthusiast-good.
HIGHLY RECOMNMENDED
Have a lab with a server, a couple (2, not just 1) touch screens and 1 thermal printer.
ALOHA CERTIFICATION
Worthless(why at end of this write-up)
SELF TRAINING
Valuable but very "expensive" (your time, downtime, poor purchasing decisions, re-re-re-refixing issues etc.)
HYBRID SELF-TRAINING
BEST CHOICE. Working closely with resellers makes self-training much better. For example, make sure only you (the tech) access the reseller's support-center, you sit between them and store managers. Be on-site when they do any work (watching the server if they're working remotely). Make friends, give them free stuff, hang out at their office. Ask lots of questions. Call support for things that aren't really, exactly, support issues.
Do ALL the menus, EDC configs, etc. yourself. Fix problems your managers want fixed but are relatively idiotic. Figure out things that are real problems and fix them before people know they exist. Fix about 50 different really weird, never-will-be-seen-again problems under impossibly high pressure and with 0 $ budget. If you can't do that, have a lab, break stuff in really weird ways and then fix it. Levitate your x-wing out of the swamp and you are a master.
RTFM. Especially the older PCI compliance specs. Those were a solid, basic, very good set of recommendations. The current one is *insane* and way, way over engineered (imho).
USER CONFERENCE
VERY GOOD if you have a high level of knowledge. You meet the heads of support and development for large restaurant chains, not as presenters, but as attendees. You get access to radiant product mangers and other very, very high level folks. One-on-one access. And the actual sessions are great, if a bit sales-pitch, only a bit. And even the vendor booths are very educational.
ALOHA RESELLER/TECH CERTIFICATION IS SILLY
The training, which certified us as reseller-support, able to access aloha internal support systems, speak directly to 3rd tier support, etc., really just read us the aloha technical documentation. Seriously. Like a book on tape. It had few real world examples, 0 hands-on, and, ended with a reasonably easy test . No framed diploma
DISCLAIMER: all the above is IMHO. It's long because I didn't have time to write something shorter. I sincerely hope it is somewhat helpful.
Oh, I think I agree with Coors, mostly. I do know he is a very solid tech. I just wish there was a practical alternative to Aloha. I've considered making one, but, I just don't care enough

.