Dunno, I feel the 0.1x-thing is often a function of obstacles in the way of productivity.
At my last job, I was part of a crack team of senior consultants spent months building a CRUD service that basically did nothing but passing data from incoming requests to another API, and then doing the same with the responses. Because the service was distributed, this was asynchronous, and state was persisted in a byzantine state machine. By God were all the buzzword dev-ops checkmarks green. The entire team spent most days navigating a maze of elaborate OpenAPI specs, trying to make sense of nebulous kubernetes failure states, and debugging spontaneously self-breaking Jenkins pipelines that took a full hour to run each time regardless of fail or success. Hours were spent documenting the work, multiple daily standups, updating Jiras with elaborate definitions of done, time reporting in multiple tracking systems. It could take a full week of this stuff to bring a trivial code change into production. That was at most 0.1x development. I spent a lot of time browsing the internet because I literally couldn't affect the speed of the work, I was always waiting for some process somewhere to decide to finish so I could repeat the cycle.
Note: Many of these things are necessary sometimes in larger projects. This was not a large project, but it was run as though it was, leading to a development workload that was almost entirely process overhead.
In my spare time, I developed an internet search engine, and quite literally was 100x more productive than I was in my dayjob because I had none of that bullshit in the way.
At my last job, I was part of a crack team of senior consultants spent months building a CRUD service that basically did nothing but passing data from incoming requests to another API, and then doing the same with the responses. Because the service was distributed, this was asynchronous, and state was persisted in a byzantine state machine. By God were all the buzzword dev-ops checkmarks green. The entire team spent most days navigating a maze of elaborate OpenAPI specs, trying to make sense of nebulous kubernetes failure states, and debugging spontaneously self-breaking Jenkins pipelines that took a full hour to run each time regardless of fail or success. Hours were spent documenting the work, multiple daily standups, updating Jiras with elaborate definitions of done, time reporting in multiple tracking systems. It could take a full week of this stuff to bring a trivial code change into production. That was at most 0.1x development. I spent a lot of time browsing the internet because I literally couldn't affect the speed of the work, I was always waiting for some process somewhere to decide to finish so I could repeat the cycle.
Note: Many of these things are necessary sometimes in larger projects. This was not a large project, but it was run as though it was, leading to a development workload that was almost entirely process overhead.
In my spare time, I developed an internet search engine, and quite literally was 100x more productive than I was in my dayjob because I had none of that bullshit in the way.