Reading this makes me realise on my team I'm the automation guru. That's my culture through and through. The rest of my team's culture is the opposite. I always want us to play a little more defense, so that we can over time get a lot more done. They always push back that "we're too busy to do it". Yet I continue to automate and things continue to improve. Sucks because we could be significantly more effective if it were the team culture.
I sort of feel it's the inverse. The last place I worked was heavily into automation and they had the one manager who always cautioned about relying on too much automation. I think that was a healthier dynamic tbh.
Too much vs. not enough are just different sets of problems.
Too much = you risk no one on the team being able to troubleshoot when things go wrong because no one has ever had to run through the process themselves before so no one understands it.
Too little = a non-trivial percentage of your bandwidth is eaten up by trivial things you keep doing over and over again that are in the vain of servicing requests rather than solving problems.
In practice I find I'd rather have the first problem and I can think of solutions to it's problems that I'm happy enough with.
Sure, it's ok, but she's compromising on the best resource for advancing her programming ability: her team.
I learned a lot from my coworkers that I couldn't have learned at school or internet. The author of the comment looked like she is passionate for programming, so I think she could be much happier with coworkers who she can look up to and learn from.
