Acknowledgement

Trying to get a price quote from a vendor. It has been two full weeks. The first week plus was confusion within their organization who should be working on it. See, back in April they reclassified our account, so we got a different representative, which is fine. But four months later, they should not be repeatedly trying to have the old one work on the quote. Only when the old one realized that we were not his client did it get shifted to the correct person.

However, three days since then I just realized that I have not seen anything from our representative that he is in indeed aware of the quote, confirming what is supposed to be in the quote, or providing the estimated time it should take to provide us a quote.

Hopefully, I am not a narcissist, but this lack of acknowledgment made me nervous the request had been overlooked. After yet another poke of the vendor, we did finally get a quote. Overall, it was two weeks, one hour, 28 minutes later after the initial request. I hate to nag, but I also hate to allow the request to be overlooked. The acknowledgment lets me know the fulfiller knows about it and it not being done is due to something else.

Why you need a pre-performance routine

As he moves toward the OR, McLaughlin is running through a precise series of thoughts and visualizations, which he calls the Five Ps. First is a Pause: He tries to forget what’s happened earlier in the day and focus only on the present. Next, he thinks deeply about the Patient. “This is a seventy-three-year-old man, and we need him to come out of this pain-free and able to walk more easily,” he says to himself. He reviews his Plan, mentally rehearsing the surgery step-by-step. Then he offers some Positive thoughts: “You were put on this Earth to do this operation,” he says. Finally, as he steps toward the table, he says a quick Prayer. “It’s very ritualistic, and I’m very focused,” he says.

Back when I had to do Friday night maintenance work as a GeorgiaVIEW database administrator, I had something like this. I would do the Pause to quiet my mind to become fully present. Then I would think about the systems involved. Then I would mentally step through the plan for the maintenance.

 

Automatic For the People

This program and I are at odds over what “automatically” means. It says that the dataset is updated automatically, which is fine. Except they produce new data multiple times a day at the most frequent and every couple days at the least. The agent software is supposed to update every day. My dataset was 202 days old, so something was obviously wrong.

I decided to give it a kick in the teeth by doing a manual update. Just annoyed at it informing me that I don’t need to do this because it does it automatically. Obviously I did because it was not actually automatically doing it.

Now it is telling me that I need to reboot and giving me a 20 day countdown until it does.

Stealing the T

The Georgia Institute of Technology has a tradition of stealing the letter T. I first ran across this in a local news media story where the letter T was stolen from signage. The main tradition is stealing the T from Tech Tower which has “TECH” on each of the four sides. (They return it during halftime of the homecoming American football game.)

It occurred to me that it would be especially hilarious for some GT alumni to steal the Ts in Trump Tower in Manhattan. It would become Rump Ower.

“Job Title”

No one knows what is a Technology Strategist. So, a while back, I changed my title on LinkedIn to Systems Architect and Engineer.

The side advantage to this is I can tell the source of where people have gotten my information. If they were looking at my Curriculum Vitae, then they would see Technology Strategist. If they got it from a conference I attended, then they would get the same.

The past several cold calls have all been the job title from LinkedIn. So, I decided to change the one on the CV to Application Infrastructure Architect. Now, all three have different titles. All three are fair.

Post Conference Spam

Sadly information technology conferences give our email addresses and phone numbers to the vendors who attended. That results in me getting an uptick of spam especially in the weeks after it. It is easy to tell the spam from the conference because the vendors mention the name of the conference. All the conferences do it. It is just one of those things from going to them.

One recent gem: “Sorry we missed you.” Actually, I intentionally did not visit the vendor area. I have no budget authority,  so I am pretty much wasting their time. Last year I did with an old boss and ironically used my familiarity with Desire2Learn to get him a moose doll for his son. (He’d already gotten one for his daughters but felt bad about getting a third. Family stability is more important than some extra spam.)

Technically spam is “unsolicited usually commercial e-mail sent to a large number of addresses.” This is commercial email. The number of addresses is modest so not large. But, I think where it gets interesting is whether or not it is solicited. One could make the argument that the conferences solicit the email addresses of attendees as an enticement for the vendors to attend. The quality of the vendors entices attendees. (I’m pretty sure people who care enough at all are a small proportion.)

It is tempting to ask the conference if it is possible to have the vendors mark categories of products they sell and attendees to mark what categories they are interested in hearing. Unfortunately, I would expect 93% of attendees to mark nothing as their interests to avoid getting spammed. Maybe a mitigation is say if you mark nothing, then we send you everything. (So pick your poison.)

 

#FirstSevenJobs

There is a Twitter thing running around where people post their first seven jobs. I do not think mine would fit in a tweet, so I put it here. This title should show up there as a hashtag and be my contribution.

If you count by employers, then I have had 1-3.

  1. University System of Georgia
    1. Valdosta State University
      1. Odum Library
      2. Information Technology
    2. Board  of Regents

Valdosta State is part of the USG. One perspective is I have only had one overall employer. VSU is just a bigger unit than say the library. One could say I have had three employer entities.

If you count by position codes, then I think the list is (not counting repeats in the same position):

  1. Student worker: Reference book shelver
  2. Casual laborer: Reference book shelver, Inter-Library Loan, Government Documents
  3. Student worker: Government Documents
  4. Casual laborer: Reference desk manager
  5. Student worker: Peer Reference desk
  6. Casual laborer: Webmaster Cooperative Education intern
  7. Casual laborer: Assistant Webmaster (CSSII)

Wow, those are all the crazy positions I held before become permanent staff. The next job in the list is the first permanent staff position. In total all seven were just over 5 years.

 

Integrate PeopleMap With Office

I work to integrate systems. So, when I learn about things, I guess my mind drifts into how would we use it. And then into how would tie together this with other things we have to make them better.

Used with permission from atmasphere

Last week news dropped about Microsoft (MSFT) buying LinkedIn (LNKD). The big deal people seem to be making of it is the Customer Relationship Manager (CRM) potential for Microsoft. Imagine in Outlook having a guide about whomever you are emailing. LinkedIn potentially could supply the data.

So Friday I also took a PeopleMap System communication training. (Leader-Task) The idea is that people have innate preferences for how they process information. Understanding their preferences and tailoring your communication to key off them will make one more effective working with them.

I guess the MSFT-LNKD deal was still on my brain because it seemed like what we really needed was a PeopleMap plug-in to Outlook which would remind us the type of the individuals we are emailing. My vision was since everyone was providing management with our types, that information would be populated into the directory service. Then a plug-in would use the email address of the recipient(s) to display that person’s type and perhaps advice on how to communicate with that type. No more wracking one’s brain for what is their type and how to deal with them.

Of course, I used Google to look to see if this already existed. It pointed me to PeopleMaps which is a service for exploring one’s social network to find connections to sales targets and get an introduction and avoid cold calls. Microsoft’s Social Connector would pull photos from Facebook for contacts.

Carbon-Copy Evangelist

Sometimes I feel preachy when advising people to carbon-copy (CC) emails. Lots of good email etiquette advises to avoid using “reply all” with emails. I think the matter is a bit more nuanced. Thinking of the perspective of a small team…

  1. The more eyes that see discussions about work decision history, rationale, and possibility the better. Also, anything I write is my perspective which other coworkers might disagree with or challenge. Including the group allows everyone to be on the same page and have the information necessary to do so. Unless the email is of a personal nature, any email about a project should include the group.
  2. I may be tied up with other things or even gone. Including the whole team makes them aware of what is going on such that one does not need to track down as many messages to bring others up to speed. They will have a general idea of what is going on and enough to get quickly up to speed.
  3. Supervisors see what employees are working on, what help they may need, or directions they are pursuing.
  4. Keeping conversations in one-on-one conversations can lead to situations where one unexpectedly goes too far down an unwanted path when other could have advised on a better one. Those outside the group like to email a specific individual directly about things. That individual CC’ing the group in replies ensured others are aware of what is asked or wanted.

Admittedly I do often brazenly initiate one-on-one side conversations from group ones. “My hypocrisy knows no bounds.” – Doc Holliday, Tombstone.

Learning Tech

I learned electronics as a kid by messing around with old radios that were easy to tamper with because they were designed to be fixed.

Lee Felsesnsteinin The Innovators: How a Group of Inventors, Hackers, Geniuses, and Geeks Created the Digital Revolution by Walter Isaacson

The story I tell about how I ended up working in information technology is about having a computer all my life as a child, breaking it, and most importantly knowing that I had to fix it before my parents found that I had. The typical takeaway is that I was intelligent, talented, etc. But, really that reveals the wrong assumption.

More correct takeaway is by this point in computer history, people designed computers to be fixed. The above quote suggests radios were initially custom built, which made them expensive to fix. To accomplish mass production, modular components make it easier to assemble but also as a side benefit easy to swap failed parts. Computers followed the same path but not only on the hardware side but the also software. Modularity to software is how we can patch, install new software, change settings, etc to fix issues.

Even today, I see people look appalled that smartphones can be successfully sold without an easy way for the owner to replace the battery or a microSD slot to add storage. We like to be able to fix our stuff. Maybe it is our Do-It-Yourself cultural biases at play.

Making things fixable lowers the bar to tinker with it. Tinkerability makes something more accessible to learn where, when, how, why it behaves the way it does. Those experiences in turn make a user self-taught into a power user and eventually into a computer administrator who really is just a power user given the keys to offlimits parts.