Tim Bradshaw writes: > On 20 Nov 2007, at 17:09, Nicolas Williams wrote: > > > > I don't agree with these statements. Clearly one ought to have some > > folks with sysadmin experience on an OS development team, but not > > everyone on such a team needs sysadmin experience. Nor is it the case > > that if you've not had sysadmin experience then you cannot comment on > > SMF. To begin with, such demands are not practical. > > Yes. I should have said something like: people who make > architectural decisions should have (significant, recent) SA > experience (and even this is not right). I certainly did not mean to > imply that people without SA experience cannot comment on anything, > and I'm sorry if what I wrote read that way. All I was really doing > was expressing my own view (as someone who is currently an SA but has > been a developer and may be again) that lack of input from people > with serious SA experience leads to bad design and bad prioritisation > of features in OSs.
I'm with you on that. I'd go further and say that having experience with other operating systems and with third party software packages is _crucial_ for getting things right. If you don't, then everything turns into an ivory tower exercise, and the results are often completely baffling for users -- even if they have some highly evolved inner logic. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
