So there's no need to focus on any specific tasks. What about models, frameworks, and methods?
An SA 1 should understand: 0. Structured Troubleshooting 1. The OSI Model 2. Kernel Security Rings 3. Von Neuman Architecture 4. Customer Service 5. Infrastructure: HVAC and Power An SA 2 should understand: 1. Basic statistical analysis (Mean, Median, Mode, etc) 2. Graph Theory 3. Compiler-Linker toolchain 4. State Machines 5. An Automation Programming Language etc. etc. On Thu, Jul 4, 2013 at 2:09 AM, Josh Smift <[email protected]> wrote: > CQ> Accounting, legal advice, marketing, development, and janitorial > CQ> services all touch upon what we do. > > ...and at a startup or other small organization, if there isn't a > dedicated person doing those things, there's a decent chance the sysadmin > might end up doing one or more of them. (And that may not work out so > well... But it happens.) > > -Josh ([email protected]) > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- Joseph A Kern [email protected]
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
