90% of work as a developer is not development,
it's guesswork and communication, trying to make sense of requirements and third-party software documentation or filling in the blanks if both are missing.

75% is as low as I can get.

That sounds like justification for the term software engineer.

@electrineer yes, but in practice no one really cares to make a distinction between software engineering and software development.

Just a thought, but if 90% of the work you are doing is not development, can you coin the term as a developer?

maybe I should call myself nondeveloper

meetings and Jira discipline eat most of the bandwidth

Plus, code once (or maybe twice) and debug till the customer leaves

Yeah, just the other week I was asked to vote on an approach for building some kind of video feature

Which 3rd party provider would easiest to work with based off glancing at vague docs or demo websites

When I asked how the videos would even be selected (Some CMS? Automated feeds?) they had no idea

...But at the same time I can't complain cause I always say they should "involve devs earlier in the process" to prevent insane decisions which are technically unfeasible