What kind of “contract engineering” roles could emerge from current Bitcoin Script primitives?

External question — Bitcoin Stack Exchange Author: Aaron Zhang Original post: https://bitcoin.stackexchange.com/questions/130627 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. I’ve been testing simple opcode combinations — CHECKSIG, CSFS, IK+CSFS....trying to get a feel for what each one actually binds. It feels like the challenge is less about expressiveness, and more about choosing the right kind of binding. I’m wondering: Do developers see this as its own discipline — not Ethereum-style contracts, but something like designing Bitcoin’s contracts within constraints? Does that map to a distinct kind of engineering role over time? Or is this still just considered script work?