Skip to content

Developers CV: GitLab or LinkedIn?

Dear Reader,

Every since “Social Coding” became a thing and GitLab and that other social coding site opened up, developers around the world have been asking “GitLab or LinkedIn for my CV/Resume?”

I now present you with the definitive answer to this question.


Github, or your favorite social coding site is absolutely necessary for a developer. You have to have a profile and you have to have some public examples of your code that potential employers can look at.

Hiring managers look at your work and look for things like

  • Advanced concepts (depending on the level of job you are applying for)
  • Coding style
  • Style consistency
  • Application of Best Practices

They may also pick out one or two bits of code to discuss with you in the interview.

  • Why did you code it this way?
  • What were the requirements of the project?
  • Did it cause you any unintended consequences?

Your answers help them understand how you code. Your entire social coding repo will help them understand you are a developer.

There is more to you than your ability to code, though. Your social coding profile can’t show everything. That’s why you also need a traditional resume/CV.

Your LinkedIn profile shows things that your social coding profile cannot. Things like:

  • Career Progression
  • Time at each job
  • Range of companies you’ve worked for.
  • Extra curricular activities (e.g. hobbies)

All of these are just as important as your social programming profile.

Show potential employers that you are a well rounded software developer by making sure you have both a social coding profile and a LinkedIn profile. Help them discover this by cross-linking them.

Until next time,
I <3 |<


p.s. yes, it has occurred to me that Microsoft owns both LinkedIn and that other social coding platform.  Kinda scares me a little.

Get a life!

Dear Reader,

A while back I wrote I love writing code! in which I talked about the fact that am not ashamed of the fact that I love writing code. Software development is my passion and I am blessed enough to be able to do it for a living. The other side of that coin is I am not my code. I am must more than a professional code monkey.

These days I

  • Attend my church
  • Date my wife
  • Mentor my kids
  • Help build the PHP community by speaking at conferences and user groups
  • Shoot my pistols
  • Scuba Dive and help others learn to Scuba Dive
  • …and much more

I am a much more rounded person than just a software developer, and that’s a good thing. Yes, my passion is still writing code and yes, there are nights when I’m up at midnight still tweaking that last little feature. (I’m getting old, it used to be 2 AM) But I do so much more.

It is OK to be passionate about software development but you will be doing yourself a favor if you cultivate an interest that is away from your keyboard. Not only will you put yourself in a different environment, you will work with people that do not have a computer-centric point of view. This reason alone makes it worth the effort. You will be amazed at how different the real world is once you get out of your tech bubble.

Get out from behind the computer and beyond the keyboard; get out there and get a life!

Until next time,
I <3 |<

There IS a right way

Dear Reader,

  1. Fins in FIRST
  2. BCD next with the jacket open
  3. Place your regulator in the jacket and then close the jacket over it.
  4. Wet suit goes on top
  5. Zip it up

I was taught this mantra by one of the greatest dive instructors I know, Donna A. of, and I run through it about once a month with fresh new minds learning how to scuba dive. See, there is a right way to pack a wet bag, this way.

At the lunch break, I am always happy to discuss the why with the students, but during class, the why is because I said so. I’ve got 350+ dives. I have made every non-fatal mistake that a diver can make. Additionally, there are thousands of divers all over the world that have tried every new idea you think you have for how to pack a wet bag and guess what, we all have standardized on this way because it is the best way. That is why we teach it as the right way.

For the past few years in tech, the prevailing attitude is “everyone should learn to code”. (that’s a whine for a different day) I believe that everyone interested should learn to code, but if you are going to learn, accept that there are right ways to do things and wrong ways to do things. In scuba diving, doing things the wrong way usually has pretty immediate and sometimes disastrous results. In software development, your ‘new way’ might work well for years. But doing things the wrong way will  eventually lead to a failure.

Please, on your own personal project, experiment all you want. Do things any way you want as long as you are the only person who will ever have to use or maintain the code. If there are other developers involved though, do things the right way. Do things the standard way, follow the community standards for the code you ware writing. If we all do this, everyone wins.

Until next time,
I <3 |<


p.s. We pack a wet bag that way to protect the regulator and console.  That is the most sensitive and usually the most expensive piece of dive gear. Fins are sturdy and cheap, they go on on bottom to protect everything from drops. Wet suits are soft and spongy. If something gets dropped on your bag, the wet suit helps absorb the blow. There is a reason we call it the right way.

Mistakes were made

Dear Reader,

At the end of March, 2019, I was let go from  a job that honestly, I thought would be the last company I worked for. (that’s a different whine) Most of you probably don’t know – not for any failing on your part but because you’ve got your own crap to deal with – is that I went into an emotional tail spin.

I did not, as I proclaimed loudly on Twitter, “crawl into a bottle of rum for the weekend”. I drink a lot less than I pretend to. :) I did not go into a deep bout of depression. But being fired as a developer shook me to my core. For whatever reason, the company walked away from me and my skills. I was let go from a company where I was doing the one thing I knew I could do well. It’s hard not to take that personally.

I handled this badly. I shut down emotionally. I withdrew from my community of friends. Honestly, I was ashamed, and I did not want to talk to anyone until I could hold my head up high again and proclaim “I AM A DEVELOPER”.

My community, my tribe, my peers, my friends, whatever you want to call them, are there to support me, not judge me. If they are secretly judging me then they really aren’t my friends to begin with.

I’m not out of the woods yet but I am better than where I was. I am now to the point where I can at least talk honestly about my journey. I am better because I didn’t shut everyone out. A few of my friends, continued to reach out, continued to talk to me, and continued to support me, even when I didn’t want them to. That and the continued love and support of the lovely and talented Kathy.

Yes, mistakes were made, but thankfully, I have enough people that love me enough to overlook that mistakes. Those people pulled my out of my hole when all I really wanted was to wallow in it.

To each of you – and you know who you are – thank you.

Until next time,
I <3 |<

I earned my rope!

Dear Reader,

A picture of a short length of nylon rope

That is MY rope. I EARNED my rope.  As part of my PADI Dive Master Certification (yes, the same training that almost kicked my butt) I had to learn to tie several knots and to successfully tie them underwater. My instructor handed each of us a piece of rope as he cut it off of a much longer piece. When asked, he replied that he gives every student a piece of HIS rope so they can learn.

In tech, we don’t celebrate individual’s wins as much as we should. When I was running a team, at every quarterly team lunch, I would hand out custom made badges that were modeled after the old Texas Ranger badges. Texas Rangers motto is (or used to be) “One problem, one Ranger”, so when one of my developers tackled a problem and completed it, they earned their badge. This wasn’t a participation award, you had to earn it.

Managers, take time to celebrate an individual’s wins. Even if they give it the “Aw shucks, it was a team effort” they need to see that you recognized their efforts and appreciate it.

Let your developers earn THEIR rope.

Until next time,
I <3 |<