Something like 6-8 hours on weekdays, and like 4 on weekends. I count coding as having the editor open and I'm either actively writing/reading code, or researching something that will help me write code.
I used to be closer to 2 hours/day, early in my career, and it definitely held me back. I was told that meetings and talking to people counted as work, which is true - but they don't make me a better programmer. The act of just writing code constantly has made me advance tremendously in the last couple of years.
5 comments
[ 2.9 ms ] story [ 22.3 ms ] threadIf I get a project in mind, I can easily spend 8 hours or so in coding. Got to get 'In the Zone'.
However I refuse to pull all-nighters like in my 30s and 40s. OMG! It's daylight already! I've got to get changed for work! (I started in my 30s)
Most days, I don't do any coding. Futzing with stuff? That's a different matter.
I used to be closer to 2 hours/day, early in my career, and it definitely held me back. I was told that meetings and talking to people counted as work, which is true - but they don't make me a better programmer. The act of just writing code constantly has made me advance tremendously in the last couple of years.