I just wanted to say thank you. As I was reading this, I cringed at the thought of even coding in an environment like this. I would like to think of myself as an extremely productive programmer, I got lots of stuff done. Lots of things built. I code in sessions, 4+ hour blocks of focus. I at least get one good session done a day, sometimes I can do a few if I feel inspired. Some of my best sessions have been at 3AM after telling the computer to go fuck itself and banging my keyboard.
This code system (in article) for someone like me is hell - but I like to build stuff. I hate fixing bugs, etc. But in "maintenance mode" or "bug fixing mode" a system like this is kind of necessary.
"The simplest and probably most widespread metric used to measure developers is how many pull requests they’re merging."
I suppose it's good practice to "backup my work" at the end of the day - I mostly don't though. If I need to fine. But I mainly push to a repo when I want to demo live, or working with a dev and we need to share. Big teams with lots of moving pieces, pushing repos each day is necessary I suppose? Or is this just bad codebase architecture? ...Small teams are more effective IMHO on smaller "modular" codebases/microservices/components/modules...etc.
This code system (in article) for someone like me is hell - but I like to build stuff. I hate fixing bugs, etc. But in "maintenance mode" or "bug fixing mode" a system like this is kind of necessary.
"The simplest and probably most widespread metric used to measure developers is how many pull requests they’re merging."
I suppose it's good practice to "backup my work" at the end of the day - I mostly don't though. If I need to fine. But I mainly push to a repo when I want to demo live, or working with a dev and we need to share. Big teams with lots of moving pieces, pushing repos each day is necessary I suppose? Or is this just bad codebase architecture? ...Small teams are more effective IMHO on smaller "modular" codebases/microservices/components/modules...etc.
reply