SkillsROS, Robotics, Lisp, Java, Python
Joined devRant on 3/18/2019
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Me: Hey, can we schedule a weekly meeting at <day, hh:mm>? I can give you an update on my work and we discuss upcoming problems?
Superviser (assigned especially to me): Yeah sure, come over, I'm free at that time.
Said day he comes 1h late, missing the appointment. Talking later that day to schedule another meeting for the upcoming week, he confirms.
Appointed day he's not there again, working from home. This has happend a few times now. They expect me to update our shared calendar or at least write a mail if I'm not available. He doesn't.
Could you fucking not?2
Make your code available for your team members, please.
So we're working on this robotics project using ROS, a framework that enables multiple nodes in a network exchange their functionality among each other through tcp connections. Each node can be implemented and executed on your own machine, and tested with dummy inputs, but in collaboration they make a robot do fancy stuff.
The knowledgebase needs data from the image processing unit, providing this data to others with semantic context to high level planning, which uses this semantic data for decision making and calling the robot manipulation node with meaningful input, to navigate the robot's components in the environment. We use a dedicated machine, which pulls the corresponding repositories and is always kept configured correctly, to run each node, such that everybody has access to each other's work when needed.
So far so good. We tried to convince the manipulation guy (let's call him John) to run his code on our central machine, not a week, but since the first day, 5 months ago. Our cluster classification has been unavailable for 2 months, but my collegue fixed that. We still can't run the whole project without John's computer. If his machine blows up we're fucked.
Each milestone feels like a big-bang-test, fixing issues in interfaces last-minute. We see the whole demo just moments before our supervisors arrive at the door.
I just hope he doesn't get hit by a truck.2