LOPSA Internal Concern: Membership Numbers

This is the first entry in a series of topical discussions on LOPSA’s shortcomings, as I perceive them, and how I think that we should be addressing them. Most of the text is taken from my candidate statement (PDF warning). Throughout its existence, LOPSA has seen a steady increase in its membership count. The last…

Continue reading

Persistent history in Powershell

One of the wonderful things about the bash shell on *nix systems is that history persists between sessions so you can easily reuse commands.  Unfortunately, this is not built into powershell on windows, but you can get close to it by putting this into your profile.ps1 which is read each time you start up powershell….

Continue reading

Why I think CISPA Should Fail

So, there’s a TON of stuff going around online about CISPA – the Cyber Intelligence Sharing and Protection Act. There’s a great, if long, thread on Reddit, but if you want something shorter, the EFF has a FAQ, and there’s a Myth vs Fact PDF on House.gov. The overall purpose of this legislation is actually…

Continue reading

Technical Resume Writing tips

I've recently read up on resume writing with an eye how I can improve my resume and job prospects.  My main takeaways were: For maximum impact, tailor the resume to the position you are applying for. Keep the resume to one or two pages long – no more! Provide a compact summary of professional experience…

Continue reading

Making standalone network diagrams with nwdiag

nwdiag generates a network-diagram image file from a .diag text file logically describing the network http://blockdiag.com/en/nwdiag/ nwdiag is intended to generate network diagrams that are embedded in larger documents; not for generation of standalone documents.  Therefore there is no provision for adding document metadata, such as Name, Author, Date. However, you can add an infobox (a…

Continue reading

Mentoring and pay-it-forward culture.

I'm now in the position of being one of the senior administrators for my employer's software in their managed software as a service division, and on a team that has seen a great deal of growth in the past year. This has meant I had to undertake mentoring of the junior admins.   I've learned…

Continue reading

Jesse Trucks Resigns from Board of Directors

 

To everyone:
Below is the email I sent to the LOPSA Board of Directors yesterday. I want everyone to know I am planning on leaving the board in a few days, and that I will still be involved with LOPSA.
Thank you,
Jesse

Philip et al.,

I am officially resigning my seat on the LOPSA Board of Directors effective at midnight at the end of March 31, 2013.
My life and other obligations require that I no longer have enough energy and time to devote to my work on the Board. However, I will most certainly remain an active and engaged LOPSA Founding Member working with various programs and committees, as well as continuing my work with LOPSA East Tennessee and my never-ending evangelism about how awesome LOPSA is and can be in the future.
I have worked hard over the last eight years to help make LOPSA great, and I hope to continue that work in other capacities far into the future. Through LOPSA, I have worked with amazing people in many countries who have all worked hard since our formation to make real the existence of a professional association for system administrators, and I know there will be countless more working tirelessly to make LOPSA better every day.
The work for the Board of Directors is never easy, always hard, and constantly rewarding. I thank all of you for your past, present, and future service to this great organization.
The elections are now upon us, and there is, as always, much work to be done. I look forward to the stirring debates and lively discussions of election season.
With great admiration and respect, thank you,
Jesse Trucks


Jesse Trucks, GCUX
jtrucks@lopsa.org
Director
http://lopsa.org

 

Continue reading

My First Year on the Board

     In January I assumed the Secretary duties from Jesse Trucks, which has pushed me over the promised 5 hours per week involvement. Most of that was learning how to do Wiki text and also transcribe our meeting minutes from recordings. (Learning MediaWiki was a plus since at $WORK I had started using that for…

Continue reading