I try to be a team player....
Mar. 3rd, 2015 11:07 pmThe new job is working out OK, I guess. But it could be better. The project is to write a file-based source control system to manage remote servers. Puppet is package-based, and doesn't give us the necessary granularity to manage items on a file level.
This past week, I've been trying to learn how to write plugins for yum. Yum stands for "yellowdog updater, modified", and is the installation package manager for RedHat, Fedora, and CentOS. It's completely new to me. Plugins are writen in Python, which I've worked with before. But I have no familiarity with the modules I need to import.
My tech lead gives me partial information, and expects me to figure it out on my own. That may be how he learns things, but I need more hand-holding and spoon-feeding than that. The tried-and-true method of RTFM doesn't work for me; most of the documentation is written from the point of view of someone who understands how it works. Man pages are a reference, not a tutorial. And if I look at the code, which often doesn't contain any commentis, it doesn't make sense to me.
Deep down, I know he's not out to mislead me or send me on wild goose chases or snipe hunts, but it certainly feels that way at times. So why am I projecting or superimposing my past experiences onto him? Because it's what I know. ( And I'm reminded of several bad experiences I've had while being on teams. )
This past week, I've been trying to learn how to write plugins for yum. Yum stands for "yellowdog updater, modified", and is the installation package manager for RedHat, Fedora, and CentOS. It's completely new to me. Plugins are writen in Python, which I've worked with before. But I have no familiarity with the modules I need to import.
My tech lead gives me partial information, and expects me to figure it out on my own. That may be how he learns things, but I need more hand-holding and spoon-feeding than that. The tried-and-true method of RTFM doesn't work for me; most of the documentation is written from the point of view of someone who understands how it works. Man pages are a reference, not a tutorial. And if I look at the code, which often doesn't contain any commentis, it doesn't make sense to me.
Deep down, I know he's not out to mislead me or send me on wild goose chases or snipe hunts, but it certainly feels that way at times. So why am I projecting or superimposing my past experiences onto him? Because it's what I know. ( And I'm reminded of several bad experiences I've had while being on teams. )