3 ms·
I did not downvote you, but I disagree with your premise. Systems administration is only part of the problem, and only in some cases. A non-inclusive list of ot
by mannykannot 11y ago
I did not downvote you, but I disagree with your premise. Systems administration is only part of the problem, and only in some cases. A non-inclusive list of other causes include failing to understand the intended purpose of a system and the environment it is to operate in, and losing control of the design.
- dijit 11y agoI would agree with what you said, but I would argue that the points you raised still fall into the realm of systems administration. Identifying scope and purpose, and it's impact and documenting the design are just some of the things an platform operations team is -supposed- to take care of.
- mannykannot 11y agoIf you expand the definition of systems administration to include everything, it doesn't get you any closer to a solution. The largest problems of development have nothing to do with administering anything (edit: for example, bad design often results from bad design decisions that are neither prevented nor fixed by seeing that the required documents have been written.) The idea that Winslow Taylor's principles can solve these problems is a fallacy - a commonly held one, but a fallacy nonetheless.