by “My name is Kent Brodie. I’m a sysadmin.” (The scene: the location is a kind of dingy classroom in a building that was once a school. In one of the rooms, there is a circle of chairs, all occupied by other sysadmins. They’re wearing mostly jeans and t-shirts. Together [but not quite], they respond in unison “Hi Kent….”)
OK, time to get serious: While this really isn’t an AA meeting, the above tongue-in-cheek example reflects a little of what LOPSA is like at this stage: a bunch of sysadmins gathered together, and supporting each other. But, at least in my opinion, the circle is too small – and the word needs to get out even more as to who and what LOPSA is, and does. LOPSA is a unique organization – it’s the only organization for system administrators of its kind. At its core, LOPSA is indeed a perfect place for sysadmins to “support each other”. But, LOPSA needs to grow, and be SO much more.
I’d like to think that I’m the kind of person who can help do that. I think both the idea and mission of LOPSA is pretty cool. When you strongly believe in something, that’s when you’re in a position to help whatever it is you’re supporting get to the next level.
LOPSA still is, in my opinion, a kind of grass-roots organization. I want to do whatever I can to making LOPSA more. More what? More ‘real’ perhaps. More known. Respected. To be honest, I’m not exactly sure about the rest yet – (that’s where you step in. you as a member tell someone like me, a board member, what you want. I then do what I can to assist). I know in my head I have some ideas. Helping to create a professionally-recognized certification program is a key item on my list. A lot of REALLY good sysadmins don’t have ‘certifications’, because none of those apply, or are maybe too specialized in one particular technology. LOPSA name recognition is also high on what I’d like us to accomplish as I’ve already hinted.
The only thing is, I’m not a board member, at least not yet. Here’s my three biggest reasons why I think I am deserving of your vote:
- I’m an experienced sysadmin. I’ve been at it for over a quarter of a century now, and I like to think that I’m well versed in the things that can make a sysadmin successful at their job. I would like to bring some of these skills into the organization itself, and make LOPSA more successful than it has been to date. I work in the .EDU space – which I believe is a nice complement to the several existing board members today with commercial backgrounds.
- I believe I’m very good at communication, and I am ALWAYS available for the greater community that I support. Whether I’m the sysadmin and users are trying to reach me, or I’m a board member and general membership people are trying to ask me something. Send me an email? Same day reply, if not sooner. IRC? I hang out in #lopsa pretty much every working day. Sometimes I help answer questions asked by someone with a problem I’m familiar with, sometimes I ask questions about something I’m fighting with at work, and finally sometimes I just like hanging out with my peers online. There’s just as much non-technical discussion as technical in the #lopsa channel, it’s a great forum to join if you haven’t done so yet.
- Finally, I’m here because I was asked to be. Somewhere within the circles of LOPSA, my name popped up as a person worth pursuing for membership in the board. To me, that’s an honor, and I’m excited.
I could bore you with all sorts of technical and political buzzwords to help get me elected– but I’m not like that. I’m just a guy who really believes in LOPSA, and I want to keep it going, six-million-dollar-man style (“better, stronger… faster”).
Is the above a good candidate statement? I don’t know. I hope so. What I DO know is that if you want to learn more about me, you are encouraged to drop me a line.
- #lopsa irc channel: kcb
- email: brodie at mcw.edu
Thanks for listening. (in the dingy classroom, Kent sits down. The person next to him stands up and starts speaking… “Hi. I’m….” [fade out to black])