i monitor my work using a plugin and usually get 2-5 hours of code a day... and i have to do all kinds of communication work as well (JIRA, investigation, prepping QA test cases, documenting PRs)
i looked back and was getting 1k lines merged every 2 weeks on average. nothing crazy I know but theres much more then just coding to my job, thats just reality.
Days/weeks where i dont get a certain amount of code done i feel like actual garbage (like the last 2-3 weeks actually). So i try hard to make sure im moving the ball forward daily. The biggest obstacle to this for me is poor planning upstream, missing/bad requirements, missing APIs that are presumed finished, etc.
That seems pretty productive for an IC. If you are spending half of your time writing code, that's pretty good. You seem to be driven and a self starter, which is why you feel like garbage when you don't hit deadlines that you've set for yourself. It's a good way to keep yourself motivated, but try to keep things in the right perspective.
> The biggest obstacle to this for me is poor planning upstream, missing/bad requirements, missing APIs that are presumed finished, etc.
This is the best reason to go into management or take on role where you spend more time on this part of the process. If you do go into management, I recommend positioning yourself as a player/coach.
1k lines per week sounds like quite a lot. I'm a dev whose role is mainly supporting legacy systems and sometimes I write probably ~50 lines in a week and feel incredibly productive due to the issues I've resolved.
50 lines on a legacy system is much harder to write than the equivalent just jamming out new stuff. Also it's hard to compare lines cause it's not a language agnostic measure.
i looked back and was getting 1k lines merged every 2 weeks on average. nothing crazy I know but theres much more then just coding to my job, thats just reality.
Days/weeks where i dont get a certain amount of code done i feel like actual garbage (like the last 2-3 weeks actually). So i try hard to make sure im moving the ball forward daily. The biggest obstacle to this for me is poor planning upstream, missing/bad requirements, missing APIs that are presumed finished, etc.