The Bran Test: 8 Things You Should Know About Your Next Employer

Why I'm writing this post

Recently I signed up for John Sonmez's free blogging course.  I thought it was great.  John had lots of good tips for anyone looking to start or grow their blog.  As a part of the course, John gave us some homework.  Our latest assignment had two parts:

1. Write a blog post about John's course...check! 
2. Find a post on SimpleProgrammer.com and comment on it...check!  

That being said, what follows is my response to John's post entitled "The Joel Test For Programmers".

 

What is the Joel Test?

The Joel Test is a set of criteria Joel Spolsky defined to rate the quality of software development teams.  Inspired by the Joel Test, John came up with his own test to rate the quality of software developers.  Both tests got me thinking about the criteria I use to evaluate whether or not a new employment opportunity is right for me.  As a result, here are eight things I think you should know about your next employer:   

#1) How do they make money?

Remember, you're investing your time and energy into this organization, and for most of us, our livelihood is directly tied to how good the organization is at making money.  Take the time to find out how they make money and make sure it's something you're comfortable with.

#2) What would you be working on?

Assuming everything works out, what would you be working on? Is it something that interests you? Is it something you personally see value in? Are you excited to have your name associated with it? Remember what my former boss use to say, "When you love what you do, you'll never work a day in your life." 

#3) Do you like the boss?

Speaking of bosses, what would you think if the person interviewing you got to tell you what to do for 40+ hours a week? Do you like them? Do you trust them? Do they seem pretty reasonable? Are they willing to consider alternative points of view? Are they a micro-manager? Does their management style align with how you like to be managed? Remember, people quit their boss, not their job.   

#4) Do you like the team?

Usually you work with more people than just your boss.  What do you think of the rest of the team? Are they nice? Do they seem to know what they're doing? Is it all for one and one for all? Can you trust them to have your back?  Remember, chances are you'll spend more waking time with your team than your family.

#5) Are they using current technology?  

Being a software developer, I really love technology.  And not just technology for technology's sake.  I really believe that technology has the potential to completely change lives (and organizations) for the better.  And usually current technology is better.  That's part of the reason it's current.  It's an improvement over something that's outdated.  It let's you work more efficiently.  It's more expressive.  You can do more with it.  I want any organization I'm a part of to be as successful and as efficient as possible and usually that means using the best tools they can afford.      

#6) Are they using current project management techniques?

I'm a huge fan of the Agile project management methodology, and not just  because Agile is somewhat of an IT buzzword.  I really believe in the principles outlined in the Agile Manifesto.  For developing new products and services, Agile can't be beat.  Again, I want any organization I'm a part of to be as successful as possible, and part of that means managing projects in a way that helps facilitate successful outcomes, fueled by close collaboration with customers.  Outcomes where the customer gets what they want, not what they thought they wanted when the project began.       

#7) Is there opportunity for growth?

If everything works out, what opportunities would be available to you? Is there an opportunity for financial gain? To learn something new? For career growth? For personal development? To be creative? To mentor others? To help someone in need? To really make a difference? Sometimes it's worth making a change for a really great opportunity.  Carpe diem, and make the most of it!    

#8) Have you counted the cost?

Speaking of opportunity, what's the opportunity cost associated with making this move? What are you giving up to take this position? Work-life balance? Security? Money? Comfort? A short commute? Free time? In order to make a good decision, carefully consider both the benefits and the cost.

"For which of you, desiring to build a tower, does not first sit down and count the cost, whether he has enough to complete it? Otherwise, when he has laid a foundation and is not able to finish, all who see it begin to mock him, saying, ‘This man began to build and was not able to finish.’ Or what king, going out to encounter another king in war, will not sit down first and deliberate whether he is able with ten thousand to meet him who comes against him with twenty thousand? And if not, while the other is yet a great way off, he sends a delegation and asks for terms of peace."  

- Luke 14:28-32

I decided to make the move

This topic has been very near and dear to my heart recently as I decided to make a career move myself.  Anytime I've decided to make a move like this, the hardest thing for me was saying goodbye to my coworkers.  I am proud to have been a part of one of the best teams I ever had the pleasure of working with.  I'm hoping very much that we can all stay in touch and continue to learn from each other (and have fun!).  I wish them all the very best of luck.    

That's my test, what's yours? 

Thanks for checking out this post! Anything I missed? Agree? Disagree? Leave a comment below to continue the discussion.  Thanks again and have a great day!     

 

The must see product demo of the year, staring YOU!

Why I'm writing this post...

Most of my last post was about the birth of my son and the crazy antics that ensued as a result of sleep deprivation.  I did however manage to sneak in a shameless plug for SiteMailCMS.com, a light weight content management system I developed that allows non technical folks to update their own website just by sending an email.  Oh no, not another shameless plug! 

CUT!

Sorry! This isn't supposed to be a post about my favorite hobby project, really! The only reason I mention it is because at the end of my last post, I thanked John Somnez from SimpleProgrammer.com for spending some time brainstorming various marketing strategies with me.  One of the things we discussed was creating a product demonstration video, which I did, so I thought I'd share my experience with anyone else who might be thinking of doing the same.  

TAKE TWO! 

What is a product demonstration video? 

In a nutshell, a product demonstration video is a short video that let's potential customers see how awesome your product is by letting them see it in action.  This isn't a training video, so don't feel obligated to show every single detail of how to setup and use your product.  Cut to the chase and show your potential customers the "magic".  They'll be plenty of time later to show them how the magic works, but first you have to show them how cool the trick is.   

What's the difference between a product demonstration video and an explainer video?

I think of it like show and tell from elementary school. The product demonstration video is the "show" and the explainer video is the "tell".  Like peanut butter and jelly, the two often go together, but they are separate and distinct.   

For example, you can check out the explainer video I made for SiteMailCMS.com here (by the way, I highly recommend PowToon for creating professional looking explainer videos).  The video briefly describes the product and the problem it solves, but you don't really get to see the product itself in action, which is why I created this product demonstration video.  Part of the video describes the product and the problem it solves, but most of the video is devoted to showing how it solves that problem.   

What is the goal of a product demonstration video? 

To turn potential customers into actual customers.  You want anyone who sees the video to be like MIND = BLOWN and to feel like they'd almost be stealing from you if they only paid the asking price because your product is THAT good.

What do I need to get started?

If you're on a shoestring budget like me, your best bet is to go the do-it-yourself route.  To create a product demonstration video, you'll need:

1. Recording software: I used Camtasia because some of my coworkers used it and I wanted to give it a try.  It's pretty reasonably price and they offer a free trial. 
2. A decent microphone: My laptop's built in mic just didn't cut it, so I sprung for the G230 Stereo Gaming Headset by Logitech. 

Great, now I'm ready to get started! Or so I thought...

Now that I had the required software and hardware, I thought I was going to simply press record and create a captivating product demonstration video.  Not so much.  My first attempt was awful.  I didn't really know what I wanted to show or how.  I wasn't quite sure what to say.  There was too much dead air while I tried to figure out my next move.  Too many "um's". I was missing a key ingredient...

...I needed a script!

At this point I started asking myself questions: Ok, think Brandon! What do you want to show? How easy it is to update your site using SiteMailCMS.com.  Ok, how are you going to show that? Hmm...I guess I need an example website.  Maybe I can show how to update the online menu for a fictitious restaurant? The answers to those questions became the basis for my script.  Now all I needed to do was sandwich the meat of my script with two additional pieces: the introduction and the conclusion.     

The [very] brief introduction consisted of:

1. A friendly greeting
2. Stating the problem that my product solves
3. A quick overview of how my product solves said problem

Basically, I wanted to let folks know what my video was all about.  Hopefully I'd captured their interest and they'd want to keep watching.  What I came up with was "Hello Internet! Today I'd like to show you how quick and easy it is to update your website just by sending an email, using SiteMailCMS.com.  Let's give it a shot..."

The [very] brief conclusion consisted of:

1. Reiterating the problem that my product solves
2. Reiterating how my product is the PERFECT solution to said problem
3. A call to action
4. Thanking the viewer for their time and wishing them well

This is where I wanted to drive home the point I'd been making during the product demonstration video.  My product is awesome.  It's the perfect solution to a problem you're having.  Please buy my product.  Thank you for your time, and have a great day.  Here's what I came up with: "Updating your website is as simple as sending an email, no technical expertise required.  I think the best thing about SiteMailCMS.com is that it puts you back in control of your website, no more having to PAY and WAIT for someone else to update your site.  To learn more, visit SiteMailCMS.com.  Thank you for your time and have a great day!"

Later on I was able to use the script as the description for my product demonstration video on YouTube as a kind of closed captioning and to improve search engine ranking.

Now I was REALLY ready to get started!

With that in mind, here are a few tips for creating the actual product demonstration video itself.

The video, the whole video and nothing but the video

At first, I tried to record the video and the narration together.  This proved to be more difficult than I originally anticipated as I was trying to focus on two things at the same time.  I found it was much easier to record the video and the narration separately.  I decided to record the video first, trying to leave the appropriate amount of time for narration by reciting the script to myself with my mic muted.  That way I could just focus on the video, without having to worry about the narration.

I also found that it was best to record the entire video in one sitting.  When I tried to record the video in sections and then assemble those sections later, I could see how the video had been stitched together.  For example, the mouse wasn't always in the exact same place between each shot.  That drove me nuts, and I didn't want it to be a distraction.  Recording the whole video in one sitting resulted in a more fluid, natural demonstration.     

Also, I found that it was easier to record almost the entire screen and then zoom in and out as needed during editing.

For uploading videos to YouTube, TechSmith recommends a resolution of 1280 x 720 HD.   

Adding the narration

Next I recorded the narration.  In contrast to recording the video, I found that it was easier to record the narration in sections, which corresponded to each scene of the video.  That way if I made a mistake, I didn't have to re-record the entire narration.  When I put all of the narration together, it seemed to flow nicely.  I really couldn't tell that the narration hadn't been recorded in one take.

I tried not to read the script directly, I had it almost entirely committed to memory.  I tried to speak slowly and clearly and put emphasis on certain key words or phrases so as to engage the listener.

One thing to keep in mind, the audio seemed louder when played from within Camtasia than when played from YouTube.

 

Adding the backing track            

I decided to add a backing track to the video for a couple of reasons.  First of all, I thought it sounded more professional.  If done right, a backing track helps keep the listener interested without distracting them.  Secondly, it helped hide some of the ambient noise I had inadvertently recorded when I had recorded the narration.  There are several places on the net to get high quality backing tracks.  I highly recommend audionautix.com.  They had several great free tracks to choose from.       

Putting it all together

The last step for me was editing.  This is where I made sure to align the video with the narration.  Some parts didn't quite fit, so I had to trim this, expand that, move this around, that sort of thing.  Here's the finished product.  In total, I'd say I spent about 3 hours for each minute of video produced. 

 

So in conclusion...

Thanks for checking out this post.  I think that's almost everything I know about creating your very own product demonstration video.  What do you think? Anything I missed? Thinking of creating your own video? I'd love to see it! Leave a comment below to continue the conversation. 




    

    

Silly chronicles of a sleep deprived daddy

My wife and I were so excited to met our first born son! 

There was nothing like meeting our son for the first time.  We love him so much.  Even though we only met him a few weeks ago, it's hard to imagine our lives without him.  Reflecting on the past few weeks, I realize what a crazy ride it's been!

For example, during the past few weeks, I:

Changed my son's diaper, only to realize that I left his dirty diaper under his clean diaper.  I finally noticed when I couldn't find his dirty diaper anywhere.  Then I thought to myself, "Oh no...I didn't...did I?" Oh yes, I did.


Started heating water for coffee, only to have my wife point out that I had the front burner on instead of the back burner.  There I go again, melting spatulas instead of making coffee, d'oh!

Be careful daddy!

Watched an inordinate amount of Star Trek The Next Generation during late night feedings.  I think the episode I like the best (maybe because I can personally identify with the plot) is Night Terrors.  Basically, the crew of the Enterprise start to go insane because no one can get any SLEEP!!!  Well, almost no one.  Commander Data and Counselor Troi were more or less unaffected.  Spoiler alert: I like the end of the episode because Commander Data orders Captain Picard to go to bed and get some rest.  I keep hoping that someone will do the same for me!

Learned a new euphemism for a pivotal and dramatic improvement: "Riker's Beard", taken from Star Trek - The Next Generation, which many fans considered wanting until Commander Riker grew a beard at the start of Season Two, after which the show was well-received for the rest of its run.  I think I can even use it in a sentence: "The development and subsequent release of the iPhone was a real Riker's Beard moment for Apple." 

I blame most of this wackiness on sleep deprivation.

So what does all this have to do with software development?

Hmm...I'm not exactly sure.  Maybe the take away is that:

1. We all make silly mistakes from time to time, it's OK, really!
2. Don't take yourself to seriously.
3. Life is much more than software development (or sleep!)  

<sermonette>On a much more philosophical note, the miracle of life, and the love my wife and I have for our son seem to be pretty strong evidence (at least to me) for both a creator and a Heavenly Father who loves us...I'd be happy to discuss this further with anyone who's interested! You may want to check out the Book of John and/or the Give Me An Answer website</sermonette>  

While we're talking about life (both as a software developer and in general)

I'd like to say thank you to John Sonmez of SimpleProgrammer.com for taking time out of his very busy schedule to talk with me for almost an hour last week about my newly developed, light weight content management system, SiteMailCMS.com.  While it's clear that John is a VERY busy guy, he took the time to listen to what I had to say and gave some excellent, well thought out advice on how to market SiteMailCMS.  I've been following John's blog for a while now.  His posts are exceptionally well written and cover a variety of topics ranging from his thoughts on Test Driven Development to How to Market Yourself as a Software Developer and everything in between.  He's got a new book out entitled "Soft Skills: The software developer's life manual".  His book is packed with all kinds of great advice on all sorts of topics that impact not only how you code, but potentially how you live, from finances to fitness.  If you get a chance, check it out and let me know what you think.  I'm sure you'll be impressed!  
 

 

So what do you think? 

Does sleep deprivation make you as zany as it made me? Does having a child make you think that there might be more to life than software development (and sleep!)? What do you think of "Soft Skills"? Leave a comment below to continue the conversation, I'd LOVE to hear from you!