Skip to main content

Improve your command line demos with three simple changes ...


Years ago, at Siebel, I would always set up bookmarks and open multiple browser tabs to make the demo flow smoothly. I never wasted time navigating through screens if I could avoid it. I would also change the default font type and size for any demo I gave. This made the text easier to read on a big screen when the viewer was several feet away. I often had people ask why my version of Siebel looked different - better infact, It told me that, while a font change is subtle - it can make enough of a difference in the demo and the perception of the product overall.

Today, I see a lot of demonstrations carried out from the command line. The same principles can be applied to command line demos - but sadly rarely employed. How many times have you watched a demo where the developer is typing 'cd ../..' when navigating around or you find yourself struggling to read the text in the console window? At one recent demo the developer wasted so much time trying to mess about with his screen resolution that he never completed the demo.

These changes are so simple and only take a few minutes to implement and will improve the quality of your demo and your productivity in general. You could say it's obvious but if you are a developer and just starting to give demos - it's probably not something you have given much consideration but is just as important as having your code work ...

These instructions apply to the Mac - but can be implemented on any OS.

1: Add alias commands to your .bash_profile

1. Open up Terminal. At the prompt enter

nano ~/.bash_profile


2. Paste the following Alias commands into the file.


alias ..='cd ..'
alias ...='cd ../..'
alias ls='ls -aFhlG'
alias ll='ls -l'
alias md='mkdir' $1
alias rd='rmdir' $1
alias cls='clear'
alias kl='kill -9'
alias reload='source ~/'
alias myip='dig +short myip.opendns.com @resolver1.opendns.com'
alias tree="find . -print | sed -e 's;[^/]*/;|____;g;s;____|; |;g'"



3. Save the file by typing CTRL X, Yes then enter.
4. Force terminal to reload the file by entering

source ~/.bash_profile

Now try out the aliases from the command line. For example type '..' to move up a directory or 'myip' to find out what your external IP address is. I've provided just a short list but you can add your own.

2: Update your Command line font

There are more readable fonts you can use for the command line. Go to https://fonts.google.com/ to find free fonts you can download and install. My preference is Adobe's open sourced Source Code Pro located here. It's been designed as a readable font for coding, for example there's no ambiguity between 'O' and '0'.



Download and unzip the font file. Install the font by double clicking the font file and then clicking the 'Install font' button on the font manager. Once you have installed the font you can use it in Terminal by doing the following:

Open Terminal. Click on Preferences ...




Select an existing Profile. Under Font click Change and then select your font from the picklist.



Depending on the font style you may need to change the font spacing (for source code pro I just use 1 for character and line spacing).


3: Create a new Terminal Profile for Demos

This is the easiest change of all. I don't understand why people don't do this more often. Yes you can enter Command + when you are in Terminal to increase the font size - but how many times have you seen the presenter forget, only for someone to mention midway through the demo that they can't read the text, which then throws the presenter off their flow? Do this instead. It's much simpler.

With the Terminal Preferences window still open, create a new Terminal Profile by clicking the '+' at the bottom of the screen.




Alternatively you can clone the Profile you modified earlier reusing your preferred font.





Call the Profile 'Demo'. Then click 'Change' to adjust the font size. Increase the font size to 18 or larger. Now when you are about to start the demo open a new Terminal window or tab and select your new profile.




When you start your demo - everyone can read the text without any issues.


As I mentioned, it's not hard and takes only a few minutes to set up. You'd be surprised how a little bit of preparation can have a big impact on the final result.



Popular posts from this blog

How to get the BBC iPlayer running when you live outside of the UK

(subtext: Get the World's most famous detective on your favourite browser)

The new series of Sherlock has started on the BBC. If you live outside of the UK and you are too impatient to wait for your local TV content provider to host it for you - then fear not !! These simple instructions will get you up and running. In addition to the iPlayer you can access most of the other UK TV channels using the same method. Note: you can use the same method to access content in other countries - such as Hulu in the U.S.

How it works:  In simple terms, the BBC iPlayer, like other players, perform a check to determine whether your internet access is originating from the UK.  So the trick is to ensure that your access to the BBC website will originate from the UK.



First you are going to use a free piece of open source software that was designed to keep your internet access anonymous. You will add a setting that will ensure that the software makes use of servers in the UK whenever making requests…

Create an Alexa Skill for your Amazon Alexa or Echo Dot

So you've bought an Alexa Dot and you want to create your own voice app - but you are wondering how difficult is it to build, how do you build the app and how much will it cost to run?  If you have basic programming skills then building the application is really easy. If you have written a function or script in Microsoft Excel or Google Sheets - then you can build an Alexa voice app. I'm providing all the basic stuff you need to get started ...

Note: This post is not intended to give you an exhaustive guide to building a skill. Instead it aims to give you the overview to get up and running quickly. Amazon provides a build-it-yourself walkthrough (here), samples (here) and a free course on Udemy (here).  I recommend starting with the free course then following the walkthrough.

How much does it cost ? It costs nothing to build and run a simple Alexa app. $0 / £0 / €0.  Zero.  Furthermore the app is hosted on Amazon's cloud, it's secure, load balanced and managed for you …

Use a Beacon to check in guests and share Emergency info

I had to put together a simple demo that uses a beacon to check in a visitor and share Emergency information, such as Fire Exits in the building, with the user .
(Note: this isn't the best way to check in a guest - but this was the request).

Most beacon demos require some native coding - but this approach favours configuration over coding so that you can get a concept working quickly before spending time on a native app.

What you will need
1. A Google account
2. A Beacon - I used a beacon from Bluecats (https://bluecats.com/)
3. Any iOs device (OS 8+) or Android Device with Google Chrome installed

How it works
You will set up the Beacon set up to emit a static URL using the Eddystone protocol.
The URL will navigate the user to a Google Web Form. You can use any URL (your own website if you want) but it must be using HTTPS.

Any device with BLE support, with an appropriate receiving app, will pick up the URL.  But therein lies the problem ! Most guests will not have the native app and…