Mr. T is an avid gamer- there's quite honestly no other word for it. He also dabbles a bit with designing accessories such as clothing and armor for games like Team Fortress. He uses GIMP, Blender and a few other nice pieces of freeware that are quite commonly employed in the world of game design. He also uses terms like "procedurally generated" as part of his normal speech.
And this has exactly "what" to do with this blog?
Well, procedurally generated is generally a gaming term, but more specifically its a coding or programming term. If you're a gamer you're probably familiar with this term, but if you're not, consider a normal search on Google or Amazon. Let's say you're looking for a certain kind of cheese. Google and Amazon will both display results based upon your previous browsing history, other surfers' previous history AND general popularity. When I typed "c" into my browser, "complex" was the 1st Google result, and Amazon returned nothing. "ch" in the browser gave me "chicagotribune" while Amazon returned "charcoal". To get "cheese" out of Google, I had to type "cheese" + space); Amazon only needed "chee" to get me to cheese.
I told you all of that to tell you this: I have two drafts that I want to publish, but both of them are once again on the backburner- this time because of an observation I had whilst surfing contact suggestions on LinkedIn. Hence, it is not uncommon for my blog's subject matter to be procedurally generated after a fashion.
As in a previous post from July of 2016, I'd like to talk a bit about professional deportment. Last time I addressed email addresses specifically, but also addressed data quality. Today I'd like to get more personal and address your LinkedIn profile with some brutal honesty which I hope will help your online presence look a bit (well, a metric ***ton) better: it's your mug.
*I'm not sure about other parts of the world, but in American English, your "mug" is a colloquialism that can mean your portrait (as in, your mugshot- the photo the police take of you when you are apprehended). And, once again, it does not imply in any way that you've ever run afoul of the law- it's just a casual way of saying "your picture"- or selfie.
Apologies- for once- to my American audience: this blog is read in over fifty countries, of which the vast majority do not speak English as their 1st language, and many have to be transliterated. Trust me, as someone who has been formally exposed to over half a dozen languages: idioms and colloquialisms do NOT translate gracefully or accurately!
So, there I was on LinkedIn. I had received an invitation to connect with someone in my field, and I accepted it. Once I did this, LinkedIn offered a slate of its own recommendations, procedurally generated by my existing network, career field, and who knows what else!
As I am IRL decidedly NOT a social butterfly, I welcome the LinkedIn suggestions and peruse them. Here's where it gets real and if you've skimmed down wondering when the wall of words would end, swallow your beverage and START READING NOW.
Gentle readers, I've had tons of sales training, and yet (for a number of unrelated reasons) I stink at sales. One thing I remember, though, that was common to all of this sales training, is this: we buy from folks like us, or ones that we like. I do not like generic silhouettes, nor will I connect with them. After all (and this is true) I am terrible with names. If I cannot connect a name with a face, I cannot make a connection. If Nikola Tesla, H.G.Wells, Steve Jobs and Sir Richard Branson had all sent me LinkedIn connection requests multiple times, and all they had for an avi was the default silhouette, I would decline them every time. Lesson 1 is: put up a real picture.
There's a caveat here, though: occasionally, a portrait may be TMI. There may be very good legal or safety reasons for omitting a portrait. In this case, you'll need to be creative if you desire a social media presence of any sort, but please... avoid the default silhouette!
Lesson 2: Your picture should be you. Unless you have some real issues as noted in the caveat following Lesson 1, put your picture here.
Lesson 3: Your picture should somehow communicate your personality, your passion, or your profession. For professional men, I don't think you can ever go wrong with a suit... or something that infers that you came to the office in a suit, but by 10 in the morning the jacket and tie were gone and the sleeves were rolled up. If you're C-level, you have license to go either way. For professional women, I'm sorry, I have little advice because the three-piece suit is not standard women's attire... I think. OTOH, if you're a working professional in a specialized field, wear the eye protection or hardhat or hearing protection or operate a specialized piece of equipment. My picture is a bit silly- but prized. Although its not a great picture, it was taken by a coworker with my camera, it really reflects my personality, and I like it.
Lesson 4: Your picture should not be an afterthought. You've invested time into creating your LinkedIn profile- why use cheap wallpaper? See lesson 3 regarding my picture. But... the idea here is about pictures that probably should not be used in a LinkedIn profile. So, don't reuse badly cropped photos of ANYTHING. Don't use prom photos (yes, I've seen 'em), wedding photos (ditto), graduation/seminar photos (uh-huh), photos with bad flash, poorly lit studio shots that obviously show you're seated in front of a pretty backdrop, obvious bad selfies, photos with your complexion/skin tone unfavorably illuminated. Ladies especially: attire or photo angle that emphasizes a particular feature (noses, etc) or sexualizes your portrait. When in doubt, have a disinterested (honest) third party check it out.
"But," you might say, "it's only LinkedIn."
According to a recent report, LinkedIn has 467 million members. Only China and India are more "populous". The whole world is looking at your mug, my friend.
As always, I am hochspeyer, blogging data analysis and management so you don't have to.
The ongoing saga of one man's quest to build and maintain the FORTY-TWO of databases, where FORTY-TWO== the answer to Life, the Universe and Everything, of course!
Showing posts with label Team Fortress. Show all posts
Showing posts with label Team Fortress. Show all posts
Sunday, February 12, 2017
Saturday, February 16, 2013
Is it Steamy in here?
Much excitement is
occurring in the Secret Underground Lair. On Valentine’s Day, 2013, Valve
Software released Steam for Linux. According to the Steampowered website,
“Valve- creators of best-selling game franchises (such as Counter-Strike and
Team Fortress) and leading technologies (such as Steam and Source), today
announced the release of its Steam for Linux client”. Our son was virtually
beside himself, waxing long and eloquent on the virtues and possibilities for
this new iteration of Steam. This, of course, is genius, as an oft heard
complaint about Linux is that there are very few high quality mainstream games
available. This could be a game-changer.
Oh, and could he install
Steam on my workstation.
In actuality, the request
was neither unanticipated nor unwelcome. I had been planning to run Linux on
that box for some time; in fact, it has had Linux installed on it several times
over the past few years as I’d dabble with a new distro every so often, but
always felt a need to keep it more permanently configured as a Windows machine
because of the need or desire to run certain pieces of software. That excuse is
no longer valid as I have a Win7 box sitting right next to an XP box. I guess
its Ubuntu or bust now. This is going to be about a one day project, as all
three PCs and the monitor need to be rearranged. My son will also need to get a
working familiarity with Ubuntu, as has never used it before. He already has
the OS on a USB stick, and that’s how he plans to install it. I don’t think
he’s aware, however, that he can run Ubuntu without installing it.
Back in database land, I
made a decision to fix a few things. First, one of the tables got renamed to
more accurately reflect its contents. Second, and much more significantly, I
fixed the Time table: I got rid of all of the extraneous characters, and cut it
down from 43,200 pieces of data to 3,600! This makes me exceedingly happy. I
still have a major fix to do which I had alluded to in an earlier post- I need
to create a “titles” table. I think it might even be worthwhile to eliminate
the “Songs” table altogether and merge that data into the proposed “titles”
table.
As far as speeds and feeds
go, only two major changes to report today: the shrinking by over 90% in the
Time table, and 170 song titles were added.
Subscribe to:
Posts (Atom)