The finer interval that you measure the smaller the percentage will be:
Level1: I spend 4 days out of five coding (80%) Level2: I spend 4 hours out of 8 on those days (40%) Level3: I spend 2 hours out of those 4, bathroom breaks, code sketching, extended thinking time (20%) Level4: I spend 1 hour out of those 2, reading notes as you type, interruptions, "fatigue" pauses (10%) Level5: I spend 20 mins of that hour, pauses between keypresses, etc.. (3%)
So it's either 80% or 3% depending on your zoom level.
"I’ve decided that from now on, I should be measuring the quality of my life by the ratio of the amount of time spent programming to the amount of time sitting in meetings."
Also, a lot of my code is experimental, or adding more logging to diagnose the problem - does it count if I erase half of the code I write at the end of the day?
The best day of any programming career comes when you successfully refactor a massive monolith of a function into a well designed set of classes with predictable interaction, and can tell people you wrote negative seven hundred lines of code.
I'm not happy about it. Meetings and decision making takes most of the time.
In theory that is ok, but in reality those meetings and decisions are actually very slow. I'm expert in my field and I know most of my decisions are the correct and best ones, however I have to explain it to others, and usually they come to the same conclusion as me - but it takes a week for that process.
I would like if at least 50% of the time was actual coding or setup or w/e kind of "actual work", because discussions don't make me feel like I'm progressing.
I am actually annoyed when I need to use Java because it triples my typing time compared to Python.
If we agree with Wittgenstein that "The limits of my language mean the limits of my world", language choice profoundly affected the time he spent thinking about his solution, not just the time he spent inputting it.
Still, all activities above are strictly technical.
So, is your question really about whether we have as much time for technical activities (as opposed to bureaucracy, marketing, managing, selling...) as we'd like to? Or is your question about how our time devoted to strictly technical things is organized?
FWIW, I recommend RHickey's "Hammock-driven development" to think of it more..
I suspect a lot of the numbers in the poll are inflated. Even a data entry specialist would have a hard time spending 7:30 out of 8:00 hours a day typing.
For me it's 1%.
I spend very little of my day writing code. Yet it's the sole reason I'm employable. I do spend a majority of my workday working on design, development and implementation (code)... this does include meetings, emails and written documentation.
Management may like to call you a coder(or worse, a resource) but don't be fooled, you solve problems first and foremost. Sometimes solving the problem doesn't require any code at all.
Without measurements this data does not mean anything.
This question has actually been on my mind for a while now. I'm usually sitting at work trying to figure something out or scrolling through my code looking for where something went wrong. I definitely don't have as much experience as a lot of the coders here, but I'm rarely ever typing.
I need to think about the flow of the program/function, and what the essential pieces are. When I know what I want, I start typing it out, and it usually only takes me 2-3 minutes to type out what I'd been thinking about. Usually, I'll have spent far longer than 30 minutes thinking about how I want to structure and attack the problem at hand.
It really depends on if you are coming up w/ something new, or working on trying to get something up, you have already done ( think web app w/ 50 reports all w/ json datasets visualized by javascript ).
...