“You have to put keywords in your resume because everything is digital now. So you need to make sure you show up in searches for the jobs that you want. You may only have 80% of the skills needed which is usually ok but you need to lie about the other 20% just so a recruiter will talk to you.”
– Anonymous Hiring Manager, Private Correspondence, November 2014
Imagine a world where this is actually true, where every employee lies in order to get the job, or at least, most of them do. This leads to the worst kind of imposter syndrome, one where people are afraid of being found out, not because of a lack of self-confidence, but because they can’t do the job and are faking it.
I expect three things would happen in this kind of world: Delegation, Deflection, and Destruction. Sadly, I’ve seen them all, all too often.
Let me explain.
If you don’t know how to do it, that might be okay — you just need to find someone else that does. As awkward as this sounds, it is exactly how upper-level business functions: The senior executives set vision, middle executives declare tactics, managers break that down into tasks, and the person at the bottom actually does the work.
In some cultures, getting someone else to do the work is a sign of leadership.
In a world where everyone is doing this, there will be one poor loser at the bottom keeping the lights on while everyone else is busy managing or architecting or analysis-ing. It’s sad.
Most companies are not this extreme, but I have worked with a contractor or two that did not understand the difference between compiling the code and executing it. How did anything get done?
He had a buddy.
If you can’t do the work and can’t delegate, then next best thing to is find someone else to blame. The project isn’t your fault, after all: It was the vendor who couldn’t deliver their part. Perhaps the analysis was too vague or the DBAs couldn’t configure the system. You can blame anyone involved — just don’t admit that you can’t figure out how to do your part. Maybe, if you blame and stall long enough, you can find someone else to do the work!.
Again, the world isn’t really this dark, but I did work on a major project for a large telecommunications company you’ve heard of, and the permanent employee who was “supervising” us couldn’t get Microsoft Visual Studio installed on their machine. In a two month period. They asked us to do it for them. Really. (It was little more complex than usual: Windows 8 was in preview, we were building apps for the windows store pre-launch, there were VM’s involved … but no, it wasn’t that hard.)
Sometimes, competent people make a ruckus about how everyone else is incompetent. If that is true, the bad news is the competent person is vastly outnumbered, and the incompetent have something to lose. The result is an activity known as workplace mobbing. Psychcentral describes workplace mobbing as a reverse-bullying where a bully enlists co-workers in a campaign of “psychological terror” against victims who are typically “competent, educated, resilient, outspoken, challenge the status quo, are more attractive or empathic and tend to be women, aged 32 to 55.”
Reading that list again, I notice these are virtues. The competent person is good and experienced. They likely gained that experience outside of current company, recognizing shenanigans and incompetence for what they are. The person goes one step further and acts on this knowledge – putting the fakers at risk. So the fakers destroy them.
Undistracted by little things like work or the pursuit of excellence, the fakers have plenty of time to plan and organize the destruction.
If any of what I wrote above feels a bit to close for comfort, that’s likely because it is a little bit too true. The anonymous example above is real, taken from a hiring manager from a real message board, talking about real work.
The “imagined world” is not quite real, but it is a little too realistic for comfort.
Here’s the big news.
This is about us. All of us.
It’s easy enough to criticize those horrible people that lie on their resume. As long as those are other people, we can feel smug, secure, even superior. But we’ve all done some things wrong. If you haven’t ever lied, there is always the misrepresentation – saying a truth in such a way that it gives the wrong impression.
The further you climb, the more the temptation to misrepresent, to be bigger than life, to get someone else to do the work. Meanwhile the system rewards the lying.
We can’t change the system, but we can change how we behave. Take the hit for doing the right thing. Be the manager that rewards the right behavior. Protect the team from silliness. Hire for ability to learn, dedication, and integrity.
For fifteen years, my friends and family told me that if I hated the system so much, I should start my own company.
In 2011, I took Excelon Development full-time, and we ain’t starving.
What have you done to make the world a better place lately?
What are you doing today? And tomorrow?
Admittedly, the title is a bit misleading. Time is a constant. We cannot really “make time”. We can’t bank it, we can’t borrow it, we can’t really even “manage it”, contrary to popular belief. There is only one thing we can do with time, and that is use it. Each one of us gets the same twenty-four hours as everyone else, and each of us has to make choices as to how we will use that time.
Additionally, we have another limited resource, and that is attention. We like to think that we can effectively multi-task, or that we can accomplish many things at the same time. For myself, the more critically I look at the way I work and the goals that I can accomplish, I have given up on this idea. Sure, I can read email and listen to music at the same time, but that’s not the multi-tasking I am referring to. When I need to be working on something that requires focus and attention, I do much better when I can partition the work I need to do, and want to do, in discrete chunks of time. Even here, it can be difficult to give the proper attention to multiple areas that need it. Also, there is the very real problems of getting stuck on a problem, and having to deal with a challenge that, for lack of better words, is just tedious.
Whenever I talk to companies or recruiters at local meetups, there is usually a common theme. They are looking for tech people, but good talent is really hard to find. Conversations like this are usually followed up with a description of some sort of very senior job for not so senior pay or a very hard to come by skill set.
Forbes online did a piece on why more people don’t go into programming. I’m not sure I agree with all or even most of the reasons mentioned, but when reading the laundry list it would be easy to come away with the impression that software jobs, particularly programming, is something no one really wants. High barriers to entry, high levels of ambiguity, and constant high pressure make the job sound really undesirable.
The premise of this problem is probably questionable, lets take a look at why.
The yearly performance review is either a boring formality where you’re checking boxes and signing on dotted lines, or a dreaded hour of what feels like ridicule from a superior. The economic climate of the past 5 or 10 years has lead even good performers to be told “You’ve done a great job, but sorry, we have no money for raises this year.” This creates a system where employees game the system by leaving to get that raise every few years.
Exit interviews are a place where you discover why your employees are leaving, because either they have not felt free enough to discuss their points of dissatisfaction or because when they did no one listened.
Both of these very common activities are a sign of disfunction in the way people are being managed.
So, what is the alternative?
I’d like to say a few things about waste. No, not the obvious kinds of “waste”, too much youtube or twitter or a lunch that was a bit too long — sometimes those are really opportunities for the unconscious mind to work.
Instead I am talking about the things that have the form of work, that look like we are doing something, but don’t actually move us forward. Aristotle might call this work that is accidental, not essential.
For example, I own a small technology company. The essence of our work is finding new business, executing on that business, and doing the things that make people want to work with us. It’s that third category that is dangerous.
I could spend a day — frankly, I could spend a week – goofing around with our website. Looking at promotional items, like pens and calendars. Retooling and reordering business cards, or trying to tweak the website to be just so. All of those things might be good, but do they generate leads? If the answer is no, they are waste — but a sort of sweet waste. Tooling around the website is easy. It doesn’t involve rejection or failure. Working on the website is a seductive time waster.
It’s the same thing in the job hunt. Working on the resume, going to career counselors, paying for a resume touch-up service, a Linkedin touch-up service, reading a “tips for interviews” book – those things are fine, but the essence of getting hired is to find potential employers, arrange interviews, and execute on them.
The main thing, as they say, is to keep the main thing the main thing. Continued »
A new tech industry phrase, The Internet of Things, has been floating around the web for a few months now. The Internet of things is a loose term people are using to describe any number of devices that may or may not currently live in your house. It’s all so vague. Last week, I found myself reading the phrase yet again with no clue about what was actually meant.
I work in an open office at my day gig. After seeing that phrase for the hundredth time, I asked “Has anyone heard of the Internet of Things. Can you please explain to me what that means?” After chuckles and light ribbing for asking questions like their grandparents would ask, I got a few vague answers of “I think it’s a little like this” or “Its kinda like when you have blabla”.
Yeah, still pretty vague.
So, lets explore what The Internet of Things really is.
Just two weeks ago, I was in Portland, Oregon, with my family of five, about to pick up a rental car from Hertz. It was 9:00PM Pacific, about midnight back home; the rental area was nice and empty …
It was still nice and empty forty-five minutes later when we received our vehicle.
It turns out the computer system was down from 1:00AM that morning until 3:00PM that afternoon. During that time, people still returned (and checked out) automobiles, and the technical staff lost them.
That’s right, they lost cars — knowing the car is on the lot, in one of a few hundred places, but not exactly where.
Then things get weird.
“Collaborative tools” is a large bucket. Wikis, multi-edit documents, shared spaces, asynchronous editing, chat tools, video conferencing, terminal multiplexing, and a variety of other options can all be considered “collaborative tools”. The goal is to encourage people to actively work on things together, to make changes in real time, or where asynchronous edits can be versioned so that no information is lost. Below are some of my favorite ways to use collaboration tools, and what you can use to get similar results.
Developing and maintaining a pipeline of work, existing clients, and potential clients has been one of the more tricky aspects of doing freelance work so far. When I was starting out, all I had was a vision of how I wanted my career to progress. Unfortunately, that vision didn’t come with actual work built into it. Over time, my pipeline of work has improved a bit and I’ve of course learned a few lessons.
Harvard Business Review has data suggesting that freelance workers are getting up to 84% of their work from word of mouth, not advertising or recruiters or freelance sites.
The way HBR dissected the data is pretty specific of course, they classify based on number of hours worked and then again by age, but the study matches well with my experience.
Lets take a closer look at what is happening.
Agile has fostered a fair bit of change in how software development happens. Change in what people value, how people work together, and changes in openness and and candor. For a long time, software was a black box, or close to it at least. A business feeds in some sort of information about the problem they are trying to solve in the form of requirements, and maybe six months later they get something. That something may or may not have solved the problem. If the problem wasn’t solved, the cycle begins anew.