Pass it on

I've been writing this blog for a few months now.  While it hasn't gotten quite the following I'd hoped, it seems a few people view it.  Thank you. 

While this blog will contain principals on computer programming, it will primarily cover important principals on business in general.  Things like accountability, integrity, trust, honesty, leadership, team-building and integrity.  Yes I said integrity twice.  It's important in everything we do.  I define integrity as simply doing what you say. 

So if you like this blog, tell a friend.  Share it with your colleagues.  Also, I'd love to hear back from you.  Send me your feedback or comment on a post.  After all... you're why I write my blog.

In closing, read my recommended reading books.  I truly believe these books will change your professional career and outlook on life in general.  They're quick reads, and I promise you'll read it again and again.  Click on the affiliate links to get these books today!

Thanks for following this blog!

~ Anthony

Anxiety

Anxiety.  What is Anxiety?  Wikipedia defines it as: "Anxiety is an unpleasant state of inner turmoil, often accompanied by nervous behavior, such as pacing back and forth... It is the subjectively unpleasant feelings of dread over something unlikely to happen..."

While that definition is accurate, it doesn't really 'feel' right.  It's just a definition.  Try this definition on for size.  Seth Godin, in his adult-picture-book 'V is for Vulnerable', says that "Anxiety is experiencing failure in advance."  From a professional standpoint, I think that is dead-on.  Anxiety over something, whether an upcoming talk or a new project, is just us internalizing an outcome we see in a situation before it happens.  And a majority of the time, that outcome is the worst-case-scenario. 

While imagining worst-case-scenarios is not healthy, I do think that Anxiety is a good indicator that you're on the right track.  That you're doing something right.  That you're moving forward!  You just need to see it as that and NOT dwell on any perceived negative outcomes.  We're much harder on ourselves than any person or situation will be.  So take a deep breath.... and forward you go!

Loved the book.... now what?

Often times we turn to books to solve a problem or to learn more about a subject.  Then, if the book engages us, we get inspired.  We get hungry for more knowledge and eager to progress to the next step.  Read the next book.  Read books recommended by the one we just read.  Read read read... absorb all we can.  But when do we stop and actually apply what we've read. 

The next time you read a book, I would recommend the following tactic:

1. Don't read the book all in one sitting.  Read a chapter or two at a time.  Then stop and allow yourself time to absorb what you've just read. 
2. Apply principals you've learned immediately.  Try them out.  Often times books build you up to more complex topics as you go along.  Having a good grasp of earlier topics will help you better understand the book going forward.  Otherwise you may burn out and only make it through a few chapters before losing interest.
3. When you finish the book, if it's not too long, reread it.  You'll almost always find something that you missed the first time around.
4. The next step after reading the book is NOTHING.  There is no other books to read or steps to take that you haven't read in that book.  Start applying what you've learned right away and don't wait for more information to become available.  You've read the book.  Now apply what you've learned.
5. Lastly, if it's a good book, share your thoughts with a friend or colleague.  Recommend the book and sit down with them after to discuss it.  It's always nice to get a fresh perspective on a book.

Now, I'm going to apply step 5 and recommend some books to you.  They're not computer programming books, but I promise you they are applicable for all walks of life.  Click on the recommended reading books listed on the right.  QBQ and Who Moved My Cheese should be on EVERYONES library.  If you don't have these books, get them today.  Read them and share them with others! 

Save the date!

As a professional, our time is often consumed by tasks and people that we don't plan for.  So when we 'want' to work on something or give a talk-presentation, we often find that we just don't have the time.  Our days come and go, and all we're left with is a soft 'maybe'  Maybe next month I can work on that project.  Maybe next week I can sit down and chat with my coworker.  Maybe after this project I can give a talk on what new things I've learned.  Maybe?  Maybe! 

It's time we all tell our time what we're doing and stop wondering where it went.  The next time you want to give a talk, start a project or just get some 'me-time' to setup some goals, set a date.  Set a date far enough in the future to prepare and strategize, but not too far out where we know we're stalling.

And when that date is set, don't miss it!

Work on your strengths, not your weaknesses

We're told throughout our years in school to spend extra time and work on the areas that need improvement.  But is that really sound advice?  Does an artist who is gifted really need to work on their algebra?  Does a programmer really need to spend time having a better understanding on the affects of music in society?  Of course not.  Now I'm not saying these areas aren't important... they are.  To some people. 

Each person is unique and has a unique set of interests and talents.  Why are we not spending more time honing in those skills and making them better?  Why do we bother making something mediocre less mediocre?  Why not make something good great!

If you're a programmer that loves working in the front-end UI but dreads writing complex database queries or obscure APIs, then just do front-end UI stuff and get better at that.  Don't spend time crafting something you're not good at or don't like when you could be getting better at something you do like.

"Well I have to do SOME database work" you might say.  Probably, yes.  But how much is up to you.  Each of us in our roles at work have a certain freedom to craft our profession how we see fit.  If you don't like writing in TSQL, speak up!  If your job requires you to spend 90% of your day in something you don't want to do, then you are what is known as "being on the wrong seat in the bus".  Maybe you're even on the wrong "bus".  Take time each week to change something about your job, no matter how little, to craft your profession to what you want it to be.  For example, if I want to only do front-end work, then a good plan for me would be to study a topic and give a talk on it.  Speak to leaders and other developers about what you've learned and show that your passionate about it.  Pretty soon you'll be know around the office as the go-to guy for everything frontend. 

The happiest people in their professions don't have magical, perfect jobs.  They have jobs that they have spent time cultivating and creating.  What are you doing to create your perfect job???