Most of the time I love tech support. We do important work for people ranging from other support professionals to lay people who are not comfortable with their computer or anything new. Sometimes this involves some truly odd requests or comments.
Some of this week’s gems include:
Fun with LDAP connection strings. I learned a lot about them and AD best practices this week. Here were the sources I used this week.
The end result (which I am sure everyone but me knew) is that you can completely drop the organizational units (OUs) from your string. Especially important if you have a complex Active Directory forest(s).
Some people think that version x.x.6 is more recent than x.x.28. I pretty much had to dig through my email for the actual release dates.
That anti-virus software can and will completely slow down a computer.
Not really news, but seeing the software you support load in chunks is weird. In related news, at least this specific anti-virus didn’t quarantine the executable when printing.
Lastly, I was offered a tip for tech support. That was also a bit odd. I made some comment about ethics in games journalism and politely said no thank you.
Fortunately, there is a viable solution that will hopefully minimize this issue in the future. I just wish for the sakes of the people affected that this solution had presented itself when this was being initiated so many years ago.
Last semester I took an introduction to logic circuits with Dr. Jeff Ashley. Dr. Ashley was engaging and excited about his subject matter, all things that make being a student an easier experience. However, as a non-traditional student, one of the things he said (repeatedly too) was very important to me.
He reiterated during the semester that you need to do a little bit every day or so in order to learn the material, keep skills sharp, and fine tune your understanding. In his end of the semester email he suggested specific things that students could do in order to be successful in the semesters and years ahead.
The first time I went to college, I was attempting a biochemistry, Japanese studies double major. Each summer I worked in the college library system, and while it paid the bills and was work I loved, it was also a sign that I was short changing myself. By being risk averse I did not treat my summer as an opportunity to continue learning. The summer between my sophomore and junior years most of the students went to Japan. It showed, and it was built into the teachers’ expectations of the students. Myself and the other student who didn’t make the trip did not compare favorably to our peers.
I find the fall semester the easier semester, because I now use that summer break to refine skills on Codecademy, pre-study for fall courses on Coursera, or try something new.
What makes this most interesting to me is that it is a practice used by top professionals in the open source tech industry. In this Dice article, around 4500 people were surveyed about what makes open source interesting and how they maintain and improve their skills. The types of things they are doing closely match the model of incremental learning championed by Dr. Ashley and enforced in the college learning model.
So, learn something new today. It is a pathway to excitement, job growth (for job-related learning), stability, and happiness.
I have been through a number of different, mostly lower level, computer programming classes. At this point through school I have done C++ and Java, which if I was more skilled or had the degree or had defined job experience (at least one of the three) could result in a decent job that kept my husband in bacon and me in chocolate.
At the University of Kentucky, they start new students in Python. Now, I was grandfathered out of taking that class because, well, Java. Nothing wrong with that. So, instead I took the Python course in Codecademy. Now, I’m under no illusion that using Codecademy is going to net me a job involving creative problem solving with computer programming. It does, however, allow me to become familiar with different types of programming languages, different database tools, and different programming tools (yeah, I’m looking at you Git).
All told, last year I completed 11 skills. Not too bad for an aging 40-something, full time worker, part time student, parent, volunteer, what have you.
It’s a great tool, and like doing the crossword puzzle on Sundays, it helps keep my brain sharp. Sadly, I don’t get to use most of what I’ve learned on a daily basis. Other than going in and working towards a new skill (Ruby at almost 50% completion), what do other people suggest for making programming more a part of daily life when it isn’t part of your work life?
Curiosity killed the cat, but satisfaction brought him back.
I like to think of myself as intellectually curious though like many things it is dependent on a number of different circumstances. Sometimes the factors are obvious. When I am tired, any curiosity is replaced with a deep desire to crawl into bed.
Sometimes the factors are not as obvious.
In my previous life, I worked in a law library. I felt consistently valued and I was regularly asked to do new tasks. If someone indicated that they wanted to add a new element to a web form, I would just read the code and try it before going to the vendor and asking for a customization. It was faster than asking an overworked tech to look into something for us. I became pretty good at looking at the bones of something and modifying it to do additional work.
Curiosity about any one aspect of my job made all of the others better. In transitioning to tech, that is one aspect of my job that I am glad I can retain. Engaging and learning during the work day provides joy and reward that go past just the money necessary to live outside of the work force.
However, in every job environment there are some common issues that can destroy creativity and curiosity.
Poor morale. When workplace morale goes down, productivity is one of the first things that suffers. In my last position, the entire office was told that we would not necessarily have jobs in 6 months and an entire team was let go that day. You could see people stop caring about making good choices for the team and the company, and with that came a lot of poor decisions all around.
Micromanaging. One of my first managers spent a lot of time checking on what I was working and directing how I should complete tasks. This was fine as I was learning the systems, but became more of a problem as I worked in the department over time. My best managers have been those who assign projects and check in every week to see if we were on target combined with those managers who were accessible for additional conversation between meetings.
“That is how we’ve always done it.” Nothing stifles creativity and problem solving as much as being told that it isn’t wanted. Going through process improvement was a great opportunity to showcase alternatives and work through on paper whether or not a new process would improve productivity.
Productivity is not curiosity, but it is often a byproduct of curiosity. I used this opportunity to create a matrix of services, allowing anyone in the department to see what services we had, how much they cost (and how they were billed), how to request or create a login, and some of the more common troubleshooting solutions. But this never would have succeeded under the status quo even though it provided ample benefits when I went on maternity leave.
Some interesting articles on curiosity and the workplace environment:
A short haiku for the work enabled on today, this blackest of Fridays in November.
Black Friday is here
No call or ticket in queue
Yesterday was a time to be thankful, or if you are like me and love to cook, a time to overdo it so you are exhausted all afternoon and into the next day. It is hard to be thankful when you are in the midst of everything, and you feel pulled apart by all of the obligations real and imaginary in your life.
So, now that all of the hullabaloo is over, I am thankful.
Today I am thankful that I have a job that will allow me to buy thoughtful gifts for my friends and family.
Today I am thankful that I am healthy, and that my complaints are a simple result of no time.
I am thankful for sweatshirts, scarves, and hats for when I am too cold.
I am thankful that I have not needed to experience the horrors of war, either as a refugee fleeing from conflict or as a fighter.
I am thankful that the oven didn’t break, and that the fridge is full of food for weeks to come.
I am thankful that my husband doesn’t like cranberry sauce, so I won’t have to share.