Goals and Grit

Hello All, I wanted to shake things up a little bit and talk about a book I have been working my way through and goals. So its officially January, and a lot of us are looking at the great new year like a blank canvas, waiting to be painted. I have to be honest, I’ve always been a fan of New Years, not the holiday or New Years Eve, although everyone loves a good party night. But every year I enjoy the act of self-reflection and planning that goes into the new year, and the chance to grow and improve.

But the one thing I hate about this process is during the self-reflection, admitting where you came up short. Where did you stumble or fail, what went wrong? Now if I’m being honest I’m a DevOps guy and as a result am big on admitting failure. But if we look at this from a DevOps perspective, teams grow when they fail fast, and on some level this yearly retrospective ritual flies in the face of that.

Lately I’ve been reading a great book call Grit: The Power of Passion and Perseverance by Angela Duckworth. And it really is an amazing book that will change the way you look as success on the whole. Really it promotes this concept that success is not built on talent, but rather on the determination and passion of the person.

In the beginning of the book she calls out West Point. West Point has one of the most rigorous recruiting processes in history, and they only take the best and brightest into their program. But despite that, they were seeing a very high drop out rate, and couldn’t figure out why. The short version is because the people who are most talented are rarely tested, and if you’ve never had to overcome obstacles before, then you are likely to back down when faced with your first wall.

The book also gives an interesting take on goal planning that I had never done before, and its one that to me makes a lot of sense, and I’m giving it a try this year. So I will have to update the blog here with the results. But the one method she talks about was discussed by Warren Buffet, arguably one of the most successful business men of our time. In the book, he describes a planning process he does, which is to write down 25 goals, 25 things you’d like to accomplish this year. This sounds like a lot, but if you start writing goals, you’ll find its not hard. I hit 30 without breaking a sweat. And then pick from that list the top 5, and put those in the “MUST DO” category.

And take the rest…and put them in the “NOT UNDER ANY CIRCUMSTANCES” category. The idea is this, your time is your most valuable resource, and multi-tasking is an illusion. So you should focus your attention on these 5, and the other 20 are a distraction. The focus being that being successful isn’t about saying “Yes”, its about saying “No”.

For me this resonates, as if I pour all my attention and time into 5 specific goals, I am way more likely to accomplish them with greater impact. And this also works well with another planning approach that I’ve leveraged before, which is described by Steven Covey’s 7 Habits of Highly Effective People.

In his book, he describes the idea that if you think of your day as a bucket, and I tell you to fit big rocks, little rocks, and sand into the bucket. What is the most logical way to fill it? Big Rocks, then little, then Sand, and if we are being honest we should approach our goals the same way. But most times we don’t, we avoid the big tasks, and small tasks, and fill our day with emails first.

So he recommends breaking things into the following matrix (called the Eisenhower Decision Matrix):

Important / Urgent Important / Not Urgent
Not important / Urgent Not Important / Not Urgent

In this matrix, the idea is that “Important” means that it lines up with your goals, which I would argue are the five goals provided above. From there we can look at what’s urgent and aligns to our goals as where our time should be spent.

  • Q1 of the above box, is for things that are urgent and related to your goals, like deadlines, crisis, opportunities that are time sensitive.
  • Q2 of the above are items that don’t have a pressing deadline but focus on your goal, this should be next on your priority list.
  • Q3 are items that require immediate attention but don’t move us forward. Which should try to minimize these tasks as much as possible. Things like phone calls, emails, etc.
  • Q4 are items which aren’t urgent or important and are basically time wasters, eliminate at all costs.

So leveraging the above matrix, makes it very easy to keep our focus where it should be on our 5 goals, and avoiding the distractions that undermine our success.

Getting Started

So I thought I would start this new direction for the blog with a post about a topic I get asked about a lot.

“I want to get started in programming, how do I do that?”

And this is a great question, and one that makes a lot of sense to me as the lines between technology and business are blurring.  And more and more people are interacting with developers in their daily life as part of their current jobs, and its leading to people’s eyes being opened to the opportunities in this place.

My next question is normally “Why?” and at first that usually takes people back, but this is an important thing to ask yourself.  I ask this because to be honest, switching fields and taking on something like becoming a developer isn’t an easy journey, and if your motives aren’t clear than your going to set yourself up for failure.  I generally think it’s smart to ask if this is a worthwhile investment of your time.  Because as much as I love this industry, it can be quite brutal at times.

Don’t get me wrong, I’m not making these statements as some grand arbiter who decides if you are worthy of becoming an almighty developer.  I make these statements because the simple truth is that to work as a developer and achieve success you need to be willing to accept the reality, which is less Minority Report and steve jobs, and more the craziness of Silicon Valley.

I would tell you to ask the following questions:

  • Do you like continual education?  Are you willing to read about this stuff in your spare time?
  • Do you like to tinker with things?
  • Do you have “Grit”?

For the final question, specifically I’m referring to the fantastic book by Angela Duckworth, that describes Grit as basically being the intersection of Passion and Perseverance, and that it is the most important part of any equation where someone is hoping for success.  And I would argue, even more so true for developers.

If you look online at the “successful developers” they all have one thing in common…they live for this stuff.  And spend a lot of time doing it, and finding new ways to challenge themselves and push boundaries.  They are constantly looking for ways to change their mindset to find new opportunities and directions.  I don’t claim to be a famous developer, but I can tell you that I’m proud of where I’ve gone in my career and I genuinely love what I do, and much like those “famous developers”, my wife describes me as a “well documented nerd”.

So now the important question is, did I lose you?  If not, I think this is a rewarding career option that can take you in some interesting directions, but you need to know that it will be a slow burn.  This is not something where you will be writing award winning apps by Monday if you start on Friday.

Below are some links to help you out, feel free to reach out with questions, I’ve tried to provide a lot of training material and some notes about each link:

Visual Studio 2017 Community Edition – This is the primary IDE (integrated developer environment) for all things in the Micr0soft stack. And the community edition is free, which is even better.

https://www.visualstudio.com/downloads/

When you go to install it, its going to ask you to customize the install, by selecting different packages and what not.

Great start: C# fundamentals for Absolute Beginners:

https://mva.microsoft.com/en-US/training-courses/16169?l=Lvld4EQIC_2706218949

For training materials I would recommend the following:

Microsoft Virtual Academy – https://mva.microsoft.com/

This is a great site for a lot of training content Microsoft generates to help. I would point you to the absolute beginner classes as well as the learning paths. They also do a good job of categorizing training (100 level, 200 level etc)

C# Courses:

https://mva.microsoft.com/training-topics/c-app-development#!jobf=Developer&lang=1033

Visual Studio Training:

https://mva.microsoft.com/product-training/visual-studio-courses#!jobf=Developer&lang=1033

Getting started with Visual Studio 2017

https://mva.microsoft.com/en-US/training-courses/getting-started-with-visual-studio-2017-17798?l=9oIw0FD6D_3611787171

Learning Paths:

https://mva.microsoft.com/LearningPaths.aspx

Channel 9 – https://channel9.msdn.com/

Great site for general videos, and is updated all the time.

I recommend web as a good place to start, the .net web platform is called ASP.NET and uses HTML, C#, and some javascript to work. (C# and Javascript syntax are pretty close)

https://www.asp.net/get-started

https://www.asp.net/mvc/overview/getting-started

This is probably a good start.

How to punch up your resume?

So I thought given the new direction with this blog, I would focus my attention on some of the questions I get a lot.  And one of the  biggest questions I get asked frequently is “My resume is terrible, how do I make it better?”

To be perfectly honest, most people undervalue their resume, and think of it like some kind of checkbox.  I love hearing people say “I’m not worried, once I go in for the interview the resume is meaningless.”  To which my response is HOW DO YOU THINK YOU GET THE INTERVIEW!

There’s an old adage, that the you never get a second chance to make a first impression, and when applying for jobs, the resume is your first impression.  When I worked for a prior company, part of my job was interviewing new talent and determining if they were a good fit to move the organization forward.  As such, I literally conducted over 100 interviews in a 8 month a period.  I can say I’ve seen a lot of things, and this blog post is really based around the tips that would apply to help get your resume noticed and get you in the interview.

  1. DO NOT stick to one page:  In college they will tell you that your resume must be limited to one page.  That is not realistic for a technical position, because in these positions we are looking for the skills you have.  Don’t go crazy but a good three page resume is a lot better than Times New Roman, size 8 compressed onto a page.  The human eye needs white space more than anything.
  2. Keep it up to date:  This is jumping a little further ahead, but make sure it is 100% current.  I’ve read resumes of people and nothing turns the interviewer off more than to bring you in and here, “Here’s the stuff that I’ve been working on”.
  3. Describe the projects:  Even better than a list of skills is a project description, and acknowledging that you can’t give up all details.  But things like, “Project XYZ was a mobile app built with Xamarin with a Cosmos DB database back end, and I was the lead developer of the mobile side.” tells me a lot about what your skills are.
  4. Be clear about your role:  It helps if you tell me what you did on the project, and be clear about the responsibility not the titles.  I’ll give an example, my first job I was responsible for building software for managing test centers and grading certification exams with the state, but being the state my job title was “LAN Technican”, no even close.  So I found that you should try to change your title, just list what you did on the project.  It gives a clearer picture of what your skills are.
  5. Put in personal projects:  I used to tell people “I can teach someone to code the way I want, but I can’t teach passion”.  So if you’ve contributed to GitHub projects, put it in there, if you have apps in the app store, put them in there.  Talk to me about what you with, that shows perseverance and drive, which I can’t teach.  If you blog list that, if you work with user groups, put that.  I once had a candidate show “my son and I built a cloud enabled race car with a raspberry pi and a cell phone”, that’s fantastic information.  But make sure you limit it to what you’ve done.
  6. Be Honest about how much you’ve worked with something:  It’s a great idea to quantify your technical skills, you can use a 1-10 scale, or some other measure, on my resume I use a 1-5 scale.  This allows them to get a good assessment of your skills and saves everyone time.  And to be honest this is another one where you show “I’m learning Xamarin on my own” is huge.  Expect that during the technical interview you are going to be grilled on all these, and if you aren’t honest, that’s a guaranteed out (next post we talk about the technical interview).

 

Welcome to Mack Bytes

Hello all, consider this the inaugural post of the new Mack Bytes blog.  Welcome!  I’ve chosen to sort of rebrand this blog, and sort of relaunch it for a couple of reasons.  The first and foremost of which is that the other blog has sort of faded.

To be honest I started that blob it feels like a life-time ago, and it was started with the intention of creating a blog to provide articles that were intended to be “how-to” guides, and other targeted posts strictly only on software development.  And there’s nothing wrong with that, but if I’m being honest, I had trouble continually updating it, and it felt like every post started with “Let me start by apologizing for the lack of updates”.  And that’s not a good place to be.  I also feel like my life has changed actually quite a bit recently, and I sort of wanted to refocus my efforts.  So over the past year I’ve been doing a lot of thinking, and planning.  And this has all been geared around life goals and direction.  And I really wanted to relaunch this blog with the intention of being more than it was before.  Don’t get me wrong I’m a big nerd at heart, so there will always be the technical posts, but this newly branded blog is more about changing to being a general blog to help people as I figure this stuff out for myself.

In essence, I’m inviting you all on my journey.  So I’ve found myself at the tender age of 35, and realized that the journey that got me to where I am is very different from the plan when I graduated college, and I’m looking forward to where I can go next.  But really for me to do that, a lot of factors have to be considered.  And a lot will likely happen along the way.  I will be using this blog as a platform to help people and share insights.  And I will also be leveraging other social media platforms as a way of driving those messages.  So if you like what you see here, please pass it along to someone else, if you don’t please talk to me.  I’d love to start a dialog exchange if you disagree with my thoughts, actions, or beliefs.  Dialog is the best way to really grow, and challenging dialog has a way of making you re-examine your beliefs and actions.

So here we go, the first post of the new blog, looking forward to more.