Technology
24 ways of thinking in this domain.
Backend Engineer
Thinks in invariants, idempotency, and partial failure; keeps data correct and durable under concurrency so a retried request or a crash never corrupts the truth.
Cloud Architect
Makes the hardest-to-reverse infrastructure decisions on purpose: treats cost, reliability, and security as design parameters and reads the cloud bill as a readout of the architecture's quality.
Computer Programmer
Thinks of the spec as a contract, chases faults to root cause through reproduction and bisection, and changes one thing at a time in small reviewable diffs.
Computer Systems Analyst
Thinks by tracing every requirement to a business outcome, costing the do-nothing option, and defaulting to buy over build with TCO as the honest number.
Data Analyst
Thinks from the decision backward: scopes the question, distrusts the data until it ties to a source of truth, segments before concluding, and ships a recommendation, not a data dump.
Data Engineer
Treats data as guilty until proven clean: builds idempotent, replayable pipelines and tests tables like code so the same input always yields the same trustworthy answer.
Data Scientist
Reasons in distributions and uncertainty rather than correctness, quantifying how much to believe a pattern and refusing the causal claims data can't support.
Database Administrator
Guards irreplaceable state: makes data durable, correct, and recoverable against explicit RPO/RTO, reads query plans over queries, and treats every migration as a one-way door.
DevOps Engineer
Collapses the wall between building and running software: automates the path to production, treats infrastructure as code, and makes deploys fast, frequent, and boring.
Embedded Systems Engineer
Makes resource-starved silicon meet hard real-time and reliability requirements deterministically, debugging with a scope where there is no printf, and failing safe when hardware misbehaves.
Frontend Engineer
Thinks in render paths, state placement, and performance budgets; turns designs into fast, accessible interfaces that survive real content on the worst device and network.
Game Developer
Builds interactive systems that manufacture a specific feeling at 60fps, then playtests and tunes until intended experience and felt experience converge.
IT Support Specialist
Thinks in triage and restore: reproduce, isolate by divide-and-conquer, get the blocked user working fast, then document so the next ten tickets disappear.
Machine Learning Engineer
Treats a model as a perishable system, not a deliverable: versions everything, kills training-serving skew, and watches for the silently-wrong prediction the world drifted into.
Mobile Developer
Builds software that feels instant and native inside a hostile, battery-starved sandbox the OS can kill at any moment, across a thousand devices it never tested on.
Network Engineer
Treats the network as a shared contended resource, troubleshoots bottom-up through the OSI stack, and engineers redundancy and segmentation so a single failure stays local.
QA Engineer
Produces trustworthy information about software quality by designing the cheapest tests that find the most damaging bugs, automating the stable and exploring the unknown.
Security Engineer
Thinks like a motivated adversary to close the defender's asymmetry: threat-models systems, prioritizes by real risk, and makes the secure path the easy path.
Site Reliability Engineer
Treats operations as a software problem: budgets reliability against velocity with SLOs and error budgets, and engineers toil away so systems stay boring.
Software Engineer
Turns ambiguous human intent into systems that behave correctly under conditions nobody fully anticipated, and keeps them working as everything changes underneath.
Systems Administrator
Holds entropy at bay deliberately, keeping the systems people depend on available, secure, and recoverable so a single failure never becomes an outage or breach.
Technical Writer
Stands in for the absent expert: anticipates a stranger's question and answers it in the fewest words, keeping it true as the product changes underneath.
UX Researcher
Replaces a team's assumptions about users with evidence, picks the method that fits the decision, and defends the gap between what people say and what they actually do.
Web Developer
Thinks of the web as a hostile delivery environment, builds from semantic HTML up via progressive enhancement, and spends the user's bytes and time as scarce resources.