There seems to be a convergence of largely orthogonal skill sets here, which may create confusion about what the most useful components of a 10x are.
For example - I see optimization abstraction as a core skill, searching for the best performance given the least amount of resources (whether developmental or computational) and what seems to be a familiar pattern.
Tooling agility may be another, i.e., how quickly can one re-create a cookiecutter build environment with observability, tests and release signing given a blank slate.
Package creation might also be a thing, though it is an example of optimization abstraction.
Troubleshooting skill sets follow from experience and understanding, and, frankly, some creatures are better than others in this regard.
Lines of code (LoC) used to be a measure, two decades ago; these days, compactness, certitude and conciseness may be the golden ticket.
For example - I see optimization abstraction as a core skill, searching for the best performance given the least amount of resources (whether developmental or computational) and what seems to be a familiar pattern.
Tooling agility may be another, i.e., how quickly can one re-create a cookiecutter build environment with observability, tests and release signing given a blank slate.
Package creation might also be a thing, though it is an example of optimization abstraction.
Troubleshooting skill sets follow from experience and understanding, and, frankly, some creatures are better than others in this regard.
Lines of code (LoC) used to be a measure, two decades ago; these days, compactness, certitude and conciseness may be the golden ticket.