Skip to main content

Are You and Expert?

If you have been in the software development field for any length of time you've had to wear many different types of hats.  There the DB, API creation, Web design, Web code/JS, remoting / streaming, UI, Requirements, Architect, Help system, Error handling, Customer service and a zillion other types of hats that are required for a typical project in our field.

I enjoy all of these different roles that I've needed to perform, however it does not make me an expert in them all.  I'm good in most of them, expert even in a number of them, but I know where my strength and weakness lay.  I must still learn from others.

In my youth I wanted to be an expert in everything.  Learn something new then I would quickly become an expert.  Well, not so fast, wanting and being are not the same and I needed to learn that.

I first needed to become an expert at myself and that took time.  I needed to understand what I knew, what I did not know and when it's helpful for me to provide comments and opportunity to learn.

I have found (and this is just my opinion) youth wants to be involved.  It's fair, when we are young the world is our oyster and our own self knowledge may be overstated but our enthusiasm is not.  Later in a career the perspective may be reversed.  Our knowledge may be greater but we now know how much more there is too learn and, this is very important, when we should provide input on what we do know.

I'll give some examples that you may have seen before :

- If you are in a meeting where everyone has strong viewpoints and wants (demands?) to be heard, you may want to take a look around the room.  Is everyone in the room an expert on the topic?  What is the age group represented in the room?  Is the discussion calm or anxious?  I've been in so many meetings of this type early in my career that it's a wonder how anything got decided.

- If you are in a meeting where there is a calm flow of thoughts and ideas between a few of the participants with a smattering of "stupid" questions that re-focus or re-base the topic at hand then you may be meeting nirvana.  The primary discussion is between the topic experts with the "stupid" questions coming from the non-topic experts working to learn more.  The "stupid" questions are not stupid at all, but are an active part of the questioning that is used to attach the current topic thread to a foundation where others can provide valid input.  It's a learning process in action and a path to becoming an expert (after your 10,000 hours, more or less).

Asking what I call "stupid" questions can seem like exposing your lack of knowledge, and it does, but it also exposes the current topic thread of not being based on reality or facts.  It can add a breather to the flow to provide a quick re-evaluation of the issue and validation that it's on the correct path.  You may be surprised at the path change that can occur after the question.

The becoming an expert in yourself is for 1) knowing what you are and are not an expert in and 2) when you can provide valuable input in a discussion and learn from others.  Without this knowledge you risk thinking you are an expert when you are not.

The risk of thinking you are an expert can be detrimental to yourself, your career and to projects that you are involved with.  You can fool yourself into believing almost anything, but you can not fool others involved in the project or your customers.


Comments

Popular posts from this blog

Still Life

 Life is never still, at least I don't think you would want it to be.  That's why so many of us (i.e., retired care free people) travel.  Keep seeing new things and places.   Well the Hurricane so far inland was a new thing and one I would have rather forgone but life is what happens.  Life keeps moving. Except a still life is forever and captures a slice of time frozen in a painting.  This is from a wooden bowl of pears onboard our ship during dinner one nice.  Again, just thought it looked nice. Enjoy.

A Trip Abroad

 Just back from our trip abroad as Asheville continues to recover from the hurricane.  This trip has been planned for a long time and we almost didn't make it because our dog sitting business will be closed for a while. But make it we did and now we are back. We love Amsterdam.  What a fun place to visit.  So many things to too and do there.  The weather was not the best but it did not have an impact on our visit.  Just bundle up. Got some quick painting in while on the boat (i.e., Viking) as we moved from port to port.  This painting is of a garden at a heritage site of windmills.  I thought it looked nice. Nice time on the trip to de-stress from what was happing back home.  We were fine back home but not everything is well with many others.

A Process

Once in a while I take photos of a work in progress.  This is for me as well as others as the work moves from stage to stage.  And it is done in stages with defined processes for each step.  On this walkway overpass up in Spruce Pine, I've done both an ink / marker and an Ink / Wash on the same piece. This is the finished watercolor of the work.  To start the process I did an ink drawing of it and then took a tracing from that.  It's the tracing where I did another ink drawing but this time on watercolor paper. Tracings of a work is done with standard tracing paper.  I get mine from CheapJoes.com and use the 8x10 size as that covers most of my needs.  The tracing is done with a 0.3 ink pen (Winsor & Newton Fineliner).  Once I have the tracing I can then use it for other paper or to do another work of the same subject. The tracing is just a start as I still need to get it transferred onto other paper.  For that you need a very bright light...