Roles

Troubleshooter

Expert at Extensive Troubleshooting - I learned basic electronics and had programming classes in high school. Experience designing boards and performing chip level repairs, working on firmware, writing software, performing system level configurations and troubleshooting problems with TCP/IP over VPN firewalls provided me with a top notch ability to figure out where the problem is.

Technical Writer

Expert for over 20 years. I have always been a stickler for documenting notes on tech support calls: what revision, configuration details, error messages, diagnostics steps taken. I always convert these to troubleshooting guides, procedures, manuals and training PowerPoint's.

Programmer

Skilled - 8 years

• Springfield High School - COBOL
• Austin Community College - FORTRAN and 6502
• Datapoint - 8080 code where I wrote memory diagnostics
• KMW - Andrew - Coax protocol converters: 186 - 3780 BSC used the Zilog Z80
• HASP and 3770 SNA/SDLC protocol converters used the zilog Z80, too
• The 8311 Bus and Tag Channel Interface used an AMD 8X305 RISC (Reduced Instruction Set Processor).
• The mainframes used JCL
• Xerox printers were PCL
• On my own I learned HTML, XHTML and CSS for the neighborhood website. There were over 200 pages.
• I have worked on bits and pieces of Javascript on my website, too.

Manager

Skilled - 8 years

• My first experience with management was in the military as the squad leader in charge of barracks cleanup with about 40 soldiers.
• I ran a small restaurant for 18 months with 8 employees.
• I took a 3-month Interactive Management Training course at Andrew.
• I become the Technical Support Manager at NLynx and held that position for 6 years when the company was acquired by Ringdale.

Technical Support Liaison

Expert over 25 years. Through all of the years, I performed tech support. With my hardware, firmware, and system level experience, I can troubleshoot anything. I have the patience to work with people who sometimes do not. I always write the call up to make the next call go faster. I know how to wrap a problem up to report it to the development team. I invented the EAR (Engineering Action Request). This is the procedure where you analyze the cost benefits of fixing a bug that you put in an EAR.