Programming in MetaCyber is divided into highly specific disciplines, the most prominent of which are detailed below.
Interaction with low-level machine interfaces, hardware configurations, and embedded systems. While basic configuration is done via wizards, deep programming is usually coded in E or E+, with high-end interface hardware requiring WSO or PFRC.
The logic, capabilities, and graphics algorithms of recreational game engines. Most modern games are written in W12 or Pix-It (or SW for simple PDA titles), often relying on E or E+ components to handle resource-heavy critical tasks.
Software designed to administer enterprise tasks, automate workflows, manage data schemas, and track transactional activity. Typically written in E+, W12, or Freestyle (FS), though many older or budget applications still run on VD3.
A conceptual subgroup covering specialized knowledge of malicious payloads, viruses, and data sniffers. Malware can be written in any language, but E and E+ are the most common since they are ideal for executing OS-level attacks.
Cutting-edge, self-improving software capable of proactive decision-making (AI). There is no standard language for heuristics. In the current MetaCyber timeline, this discipline is largely theoretical and has limited practical mainstream application.
The dynamic exploitation (or defense) of software vulnerabilities, including techniques used to disguise or recognize illicit activity.
The analysis, design, and administration of databases and database components. In the modern era, this is almost exclusively partnered with the LDS and LQS languages.
Programming or circumventing high-end computerized locks. Circumventing an ELD requires physical access to an interface port and is resolved as a Tricky Task (or harder, depending on the lock's rating). ELDs are usually coded in WSO, stripped-down Enoch, or a PFRC variant.
The development of immersive VR environments for the NET. To design specific functional VR content (e.g., a virtual corporate office), this must be combined with the relevant secondary subgroup (e.g., Business Software).
Guarded corporate standards and bespoke tech serving as a security deterrent against outside programmers. Each specific proprietary technology is a separate discipline.