Ros melodic in a strictly python 2.7 environment mixes horribly with a PyTorch based RL module... Time to work around with terminal calls from the latter
*sigh*

This is a condensed one (like a .bag file):
ROS kinetic > melodic - os, env, project upgrade

Yesterday I got to the point where all changes that customer support and backend asked for were set, and i could start rebuilding the old models from their very base with the changes and the new, disjoint data the company expansion brought.

So making the start of our main script and the first commit, only having that, had high importance... At least to me.

from rant import workflow

Tl;dr - I have a share of the product's backend, everyone expects it to work, no one cares how and i can spare with i, me, and myself getting there.

CTO: We need this solution, what do you need for data?
ME: Okay, thing0, thing1, thing2, preferably a ton of samples.
C: Here, also, there's a new full-timer who will help you. And you can do some sparing with.
M: Cool, i have several approaches to discuss.
*new full-timer attends fewer times than me as a part-timer*
*standup meetings talks about status, problems - yeah, whatever reactions*
*full-timer doesn't attend still, gets a "quick" (in case of consistently showing up) task to fix something in another backend part*
Me @ a standup lately: So, approach 4 worked, polishing it, but I soon-ish need to know a few things so I can finish up and fully integrate it.
CTO: Okay, when *full-timer* gets in so she's included.
*waiting for X days (x>8)*

Lurker here.
Just wanted to highlight the irony of specializing in human computer interaction and automation, while people avoid interaction at work.