As defined in the ExeNovel:
- Regular first class capitation includes, at the user's discretion, developer entitlement. F class users may prefer to remain non-developers to only see what is appropriate to their premium service level and eliminate developer oriented distraction. They may enable/disable it at will. Developer status does not imply that the user is a trained IT professional but does imply that she will use the system in development capacity, e.g. to generate apps or code, modify system elements within their purview.
- DevOps is a distinct level of privilege and entitlement from Developer status which requires either a billable account or supply of account keys at supported 3rd party vendors and does assume at least the ability to take responsibility for IT decision making in concert with DCP as a more than casual user and some level of technical knowledge. Like developer status, it is a matter of enabling when you have F class entitlement but additionally a billable account is required as unlike simple Developer status, DevOps users are not limited to F class resource entitlement. They can be billed for resources provided from Core DS inventory or use their own accounts with supported vendors.
KEE DevOps implies an ability to work with the BOOTKEE and later the mature KEE elements. It is a sharp break and cliff for how this system views the user. Less than KEE DevOps implies the user is a normal one that it is the job of the system to provide any needed expertise to use it. KEE DevOps or greater implies a user with self authoring capabilities and ability to engineer any element of systems outside of DCP, which by design remains a black box.
- Operators are O class users, those who are operating domain spaces as networks autonomous from but optionally cooperating with Core DS. They will normally run the FRED nodes and use DCP and MCP to support their namespace but might not participate in the social network or use it but with a different node type than the geonode. Independent operators of geonodes may do so in any of these three roles, with differing degrees of ability to diverge from the common network base.
| Shop Culture Sidebar
"The Professional Dilettante"
This is a somewhat snotty term I use to refer to an observed cultural pattern in the IT industry over the time I participated in it as a wage worker. This is a transient population especially insofar as
actual doing is concerned as a result of well known burnout and generational churn specific to this industry. It is to be contrasted with a "vocation" and a lifetime commitment to the doing of IT systems work. This latter
is the norm in academic computing, but the first is effectively enforced as a norm in industry.
"The Shop"
This is the locus of IT production in society up until the LLM age. It could be an academic dept or a capitalist firm or non profit development group, but not a non-IT group or an individual worker.
In dialectical terms this is the group fused in praxis.
In the ExeNovel the role of the shop is fulfilled by the triple agency (JD, PM, and WC) and the DCP/MCP Operating System. It is thus an automation that puts the shop at the service of Popular Groups with no intermediary between it and them but the novel Auteur.
DCP/MCP in the shopPopular Groups can be shops. They may function at whatever technical level they land between what is said to the left about F class users and a BOOTKEE Knowledge Engineering DevOps user.
At the Node and Cell level DCP/MCP is just linux so shops should be able to readily adapt their linux based workloads to it.
|
