What attributes do system programmers absolutely need? Which are nice to have? Are there kiss-of-death traits for system programmers? Attributes can be skills, instincts, knowledge, etc. What's critical, what works, what doesn't matter, what's best never shown or seen? Perhaps at least as important, which attributes are innate and which can be learned (or, when necessary, unlearned)? Do these vary across different systems supported/maintained/developed?
Thanks. As usual, please copy replies to me directly so they're not buried in list digests. -- Gabriel Goldberg, Computers and Publishing, Inc. [email protected] 3401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 LinkedIn: http://www.linkedin.com/in/gabegold Twitter: GabeG0 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
