https://rarehistoricalphotos.com/life-before-autocad-1950-19...
How much of (our, as in, programmers') work is the "writing code" part, vs. all of the other stuff? Build consensus, gather feedback, communicate ideas, resolve ambiguities, make non-zero progress in the absence of clear direction, etc.
A standardized way of working is sometimes better because if I have to work with someone- then it helps to be able to work on the same thing together. Tools like Visual Studio, Microsoft Office, even Netbeans or Eclipse allow us to converge on a highly productive but standardize working environment that we can work from.
If I'm running off a highly customized setup, and my partner is also doing the same thing - then I am only functional at my own workstation and nowhere else.
You may have standard vim bindings mostly to manipulate text.
But there are bindings in other IDEs to find next definition/declaration of the function under the cursor, debugging, refactoring, and so on. Within the same IDE, you will find most people don't customize those. At least, in my experience, anyways.
In my experience, For a junior/entry level, 80%+
For a (actual, not just title) Sr. dev? Typically <= 20-25%.
10–20 lines of code per day means the “writing code” part is about 2 minutes out of an 8-hour day, if you only count the code that ends up being delivered. maybe 10× that including unit tests, drafts that get replaced, duplicate code that gets refactored away, test code to see what a library will do, etc.
but ai can obviously handle a lot of that stuff too