[blablabla123]

I'm also working part-time, although I had a lot of full-time jobs with varying intensity. I noticed for me most time gets eaten by tasks that I'm either stuck on or that progress really slowly for various reasons. E.g. something I do all the time is too slow like the editor, the build/test cycles or finding the reason for an exception because there are no logs. Usually I always make myself time to also optimize these things and also communicate that in meetings. And when planning of tasks happens, I try to get involved, understand what kind of work that would mean and discuss that. (Estimation is undervalued I think) And of course get a deep as possible understanding of the core technologies, that makes work also more fluent in the long-term. This way you also have increased idle times between tickets/pull request and it's possible to put more time into such general optimizations.

At least that's my strategy. It's definitely not a career-booster but the results are good.