We are having another great meetup at the Volusion office tonight. Joe Reynolds out of North Houston is heading over to Austin to speak at the Volusion office about all the nifty new features of the latest C# offering. Joe Reynolds, a C# MVP, should be able to teach all sorts of great new things!
Come join us for pizza and drinks and a great conversation.
I am super excited to let you all know that we have been working hard behind the scenes to kick off user groups and workshops. As Developer Springboard has done in the past – we are not going to focus on one specific topic. Instead, we want to ensure that folks have access to anything that is deemed important. For that reason we will take a look at API best practices in one user group, and something more devops oriented in another user group. We might do something .NET/monolithic focused in one workshop, and something NODE/microservice oriented in another workshop.
The whole idea of these get togethers is to grow your developer tool box. Perhaps peak your interest in something new and exciting. Or to show you a new way to think about an old technology.
If all of this is just noise to you at the moment, come for the pizza, soda, and conversation!
Austin, TX 51Devs
You might be a great software developer already. But our goal is to make you better! We are building a community of developers eager to consume that next level bit of inform…
I have a never-expiring calendar reminder for myself to update my portfolio. Otherwise I just won’t do it.
Make Yourself Do It
But it is surprisingly hard to make yourself do it even with a calendar reminder constantly dinging you. And unfortunately you only ever realize that you needed to do it – and didn’t – when you need your resume to be up to date when you are ready (or worse: when you aren’t ready) to move to the next gig.
This added pressure means that you are now going to be under the gun to send out your resume in a not quite up to date form, or you will struggle to remember all the cool new things you have done in the past many months.
It won’t be your best showing. You won’t likely have all the detail you once had. And ultimately you are doing a disservice to yourself when thinking about this late in the game.
Use LinkedIn As Your Source of Truth
A long time ago I stopped maintaining a resume in document form.
Before there was a LinkedIn it made sense to constantly toil over the formatting of my resume. And it made since to keep a copy and several backups.
I needed a consistent place to go to for the source of truth for my work history as there wasn’t one clear winner on the internet for such things. Back then I would keep a digital resume on Monster and various other job boards. It was a real hassle to keep them all up to date.
But now a days it is easy to keep your information in LinkedIn. It is now my source of truth.
I try to go there at least once a month to enter at least one cool thing I did that month. It might be something simple like solving a customer’s problem. Or something more complex like learning a new thing in a pinch prior to a sales call or speaking engagement.
Similar to blogging, if you don’t pay attention to the every day details of your day job you will miss the really important parts that you can use later to sell yourself.
Additionally you are missing the opportunity of someone looking for that special talent that you just picked up. You may make good money doing a bang-up job with that 80% thing you do. You run up against some new fancy way of doing things. And that becomes your new norm.
But you never update your resume.
As far as recruiters and other hiring managers know you are only really good at that 80% thing. There is no mention of your new go-to-favorite skill – which is what they really need right now and can’t find anywhere.
This is a missed opportunity for you in a couple of ways. The recruiter won’t contact you to let you know that your new skill is in high demand. Which means you miss out on the possibility of shifting to a new gig. Or, if you really like your job, but want to earn more, you might miss the opportunity to bargain around your newly found skill. Either way, this is your loss in the here and now.
So what sorts of things might you keep track of on LinkedIn? When you have a job, you can use LinkedIn as a running log of interesting facts. When you don’t have a job you can scour through your profile and clean out the things that aren’t really relevant any more. Let’s look at what sorts of things are hand to keep track of:
Title and Responsibility Changes
There are a couple ways of tracking when your title changes and when your responsibility changes. The first is the easiest and doesn’t require much thought. Keep one entry per company you work at. Update the title. List the existing responsibilities.
This is a great way to keep a short resume. And it is a great way to not tell your hiring manager about your history. This is where the difference between a traditional resume and a CV/Portfolio come in. When I am in the hiring manager role I like to see where a person has been and all the things at a high level they have done while at a company.
If you were a developer, then a team lead, then the architect, then the engineering director – list those out. They are very different jobs. They will have very different responsibilities. And being able to show that you have done them all is important to many hiring managers. It shows you are experienced.
We have interns at my current company. One of which we have had back three separate times. For a person like this it is very important to distinctly show that you came back at three different times. And detail out what you did on each occasion. This paints a different picture than someone who just worked somewhere with no timeline. It doesn’t show that we liked you so much that we kept hiring your back.
Business Goals Achieved
Business people, hiring managers, etc. – they don’t generally care that you learned the latest version of HTML. What they do care is that because of your mastery of this new version of HTML you were able to up the sales conversion of your check out process because more customers are able to complete the check out process on their phone and tablets.
Geeks really care that you were able to write a mail sending tool in 100 lines of unreadable code. But business folks care that your tool took into account the bounce rate of certain domains and the rules around how you stay off of black lists so that your email penetration goes up 30% which effectively increased their over all penetration resulting in X number of new dollars for the month.
Now, don’t get me wrong. You need to swizzle this in a manner that you salt and pepper your business swizzle with some tech babble so that all audiences are made happy. If you just deliver the business numbers uber geeks may find your resume wanting. Add appropriate tech talk to sell that you know what you are talking about.
Use the Right Voice to Tell the Right Story
Equally important to what you did is how you tell the story. It is very off-putting to read about a guy that is singing the me-me-me-me-me-me-meeeee song! It is ok for you to say “I used tech X to achieve business Y” now and then. But equally important is how you enabled the team to achieve a goal. Or how you pulled bugs for a week to get to zero defects (sacrificed your enjoyment for the team). Tell a story of being a valuable team member.
If you are in a leadership role tell the story of how you are a shit-umbrella vs. a shit-funnel. Give concrete examples of how you help you team get stuff done.
I had a dad who built all sorts of things out of wood. That was his medium when not working on his day job. He built gazebos and greenhouses and decks. He also put things together without instructions.
He got places without asking for directions (before GPS). He would charge off into the woods in search of a stream to fish. He would get into his airplane, take off, get to where he was going, land. All of this was done effortlessly. He has always acted as though he knew how to do things. He was an expert at everything!
Two Kinds of Expert
As a dad myself I now know that from time to time he was either “winging it” or had toiled enough at a task way ahead of time to make the task now seem effortless. And much of his success in the now was based on previous successes and failures of past experiences. But ultimately he had told himself that he would figure it out. He had faith in himself to solider on and get through it. But from my point of view looking from the outside in he was an expert at everything he did. I was always amazed.
Over night success is achieved through years of hard work and practice.
To be honest I think there are really two forms of perceived expert in the world. There is the guy that is a deep dive technical genius in their world. They have seen everything. They have done everything. There is no stone unturned. They have forgotten more then you will ever learn. They can answer any question asked.
Then there is the person that isn’t afraid to say “I don’t know.”
They have seen some things. They have gotten their hands dirty from time to time. They have failed at least as much as they have succeeded. They know someone with the right answer, or they can produce the answer through searching and reading. They can eventually answer any question asked.
Different Types of Expert Produce Different Results
Now let’s talk about how valuable these two folks are to me, you, our industry, and our society.
The first person may eventually solve cancer. Or cure world hunger. Or resolve global warming. That would be valuable. But perhaps they learned game changing things along the way to solving one of these world issues – but didn’t actually solve anything? And they didn’t share any of their findings while on their journey. Then died. Their activities unrecorded. Their knowledge lost. Not very valuable.
Take the other person. They have been here and there but not everywhere. They have done some things. While learning they are also actively sharing their findings. Over time they amass a great deal of knowledge – almost comparable to the guy that knows everything.
Also, as they are putting who they are and where they are out in front of the world for all to see – they are continuously being pushed to be better. They correct any wrong assumptions they have made along the way. They are not working in a vacuum. Instead they get feedback every step of the way.
Perhaps they solve one of those world issues. Perhaps they don’t. Perhaps instead they contribute to someone else who can tackle the world issue. But in my mind the guy that is more valuable is the one that gave to the community without seeking anything in return. The person that contributed to the story potentially for someone else in their industry learn from.
Becoming An Expert
As a kid I was inspired by my father to tackle problems head on. Get shit done. No one could stop me but me.
As a result of that whatever I was interested in at the time, I was pushing in new ways. Learning all that I could. Never enough to be a truly deep technical expert to the experts of the world, but always enough to be more expert than the majority of the next guys.
One day a customer at Fry’s (while I worked as a technical representative for HP at Fry’s) showed me HTML. It was a very low bar but amazing. He opened notepad and just started hammering out some characters. With each iteration he would flip to a browser and show me a web page. Back to code. Back to a web page. He was building something out of nothing. How cool was that!? I have no idea if that guy was an expert or not, but to me he was the only person I knew that could type out all sorts of gibberish and make something structured and usable.
I have seen people that knew nothing about a topic quickly come up to speed on something and immediately grab the title of expert. Being an expert can at times be a context-oriented label. You can be an expert at something in your peer group. You can be an expert at something in your office. You can be an expert at something in the city you are in. Or you can be an expert at something in your industry. Those are all levels of expert.
Then you can further slice those definitions of expert by vertical slices in our world of technology. You may be an expert at building distributed systems using C# and NServiceBus on MSMQ. You are the expert in this space. However, in a room of Java programmers, you might be reduced to being an expert at the theory of distributed systems but a total n00b at the any of the technology tools they may use.
Apply this to any band of people. People live in groups. Programmers have peer groups, coworkers, city of residence, city where they work, regional groupings, industry groupings, industry sub-groupings, and global groupings.
And programmers have a huge variety of technical options across all of those people groupings. This means there is a very low bar for you to become an expert at certain things in certain circles. Being an expert at something, which will ultimately help you achieve your career goals, is mathematically accessible to anyone who is willing to put in the work.
All the so-called ‘secrets of success’ will not work unless you do.
So then how do you become expert enough in your area of interest? START!
There is no reason to not be thought of as an expert by someone in a meaningful way. There are so many sites on the internet dedicated to people posting their questions in a given subject matter. For programmers that site might be as simple as StackOverflow. Find a topic that you love, subscribe to the appropriate tag for your topic, and start answering questions. This will force you to do research. And you will quickly find that you are an expert to several people.
Another way is to start a blog. This may be seen as a bit more difficult as there is some technical know how required to set up a blog – even a free one hosted somewhere. Also, this usually requires some creativity on your part to keep coming up with topics to write about. And some research for each thing you want to write about so that you sound enough like an expert for people to want to read what you say.
But the key to either of these methods for becoming an expert is to do it with a regular cadence. Practice answering peoples questions. Or practice observing the world in ways that produce topics for you to write about. Ultimately both of these will force you to get better at doing what you do.
Another slightly more difficult thing to do is to write a small book. Pick a topic that is somewhat in your wheelhouse already. Then learn enough about that topic to get a high level of understanding about the topic to piece together a table of contents that is three to four levels deep.
Then start researching each of those topics enough to form thoughts on each of the topics. Publish this book in real-time as you add content to it. Give the first few rounds away for free to get feedback quickly. Evolve over time. The key here is that you will start as a new guy. And finish with a published book on the topic. And since you researched all the content in the book you are now an expert in two ways: 1) you likely know more than most because you went wide and deep on the topic and 2) you are now a published author which brings a certain level of professionalism.
The key here is pick something. Scratch a little more than the surface on your topic. Give back to the community. They will criticize you for your efforts. And you will learn by fire. And eventually pop out the other side as an expert in some circles.
The secret here that nobody will ever tell you, but I will. I have met a lot of industry experts. The only difference between them and you is that they did some work to get where they are. They actively chose to learn something vs. watching the latest TV series. They had a plan to be better than the next guy. And then they did it.
Follow through, commitment, dedication, stick to it and get shit done. In our world, this is the recipe to becoming expert enough in something.
Here is a whole site dedicated to being “Expert Enough”. You will find a similar theme being mentioned there.