Everyone Must Learn to Code

When I was 9 years old, my father brought a Commodore Vic 20 computer home for Christmas.  It came with 3k memory.  It had a keyboard, a tape drive and it connected to a TV.  I still remember sitting in my pyjamas and turning it on.  As a child with nobody to tell me how I should or shouldn’t program, my first attempt was a paragraph in english describing a game.  I was surprised when I reached the end, hit the return key and: “Syntax Error”.

The Vic 20 came with 2 books “Learn to Program BASIC I” and “Learn to Program BASIC II”.  I went through these books by the end of January.  It was more fun writing my own games than playing the ones that came with the computer.

I learnt maths because I needed binary to create sprite graphics.  I learnt quadratic equations to solve for collisions in games.  I learnt basic physics to create realistic missile flight.  Maths in school was easy because I had already learnt it to serve my computer programming hobby.

Computer Programming saved me from boring school lessons

I never paid too much attention at school.  It was generally boring.  I spent a lot of time daydreaming.  I would think through which of Superman’s superpowers would be most useful to escape the boredom of school.  It was always a toss up between flying and laser eyes.

I was lucky.  The traditional school environment was built for my style of learning.  Exams tend to bring out my best performances. I was never good at the sustained effort.  I am best in the hurried sprint to deadlines.

I used to read a lot.  I had read the entire SciFi section of my local library before I was 10.  I would take out my full quota of 6 books and read them in a week.  I had whole collections of Dungeons and Dragons books.  I loved Frank Herbert’s “Dune” (all 7 or 8 books).  I loved Tolkien (LOTR, Hobbit).

Reading is great, but it is not an activity that allows the development of mastery.  You can’t get “better” at reading after a certain point.  You might be able to get a bit faster, but you don’t develop beyond basic reading in any significant way.

I loved sports, but was always a bit small so got pushed off the ball in football or relegated to wing when playing rugby.  My younger brother was superb at any game with a ball, and there is nothing more painful to an older boy than being beaten by a younger boy in sport – even more painful when it is a brother…  and the gap is 5 years.

Computer programming was my first world of mastery.

Computing is taught poorly in schools.  We need a change in the role of computing and style of learning supported by computers in schools.

The Failure of Computing as taught in our Schools

Most school systems teach children how to use Microsoft Office.  They teach students to be users of computers, not creators with computers.

A computer is not a car.  We need people to know what is under the hood as well as knowing what the pedals do.

Programming computers is a wonderful environment for children to explore, test, trial, experiment, hypothesize, fail, succeed…

Programming taught me Important skills.

Any programming language is essentially the same.  Java, PHP, C++, Basic, Python, Lisp…  even Fortran, Cobol or Assembly code.  Master one, you will quickly learn any other.

It teaches you to be clear.  It teaches you how to trace and remove errors.  It teaches you how to test.  It teaches you how to think about systematically solving problems – not one-offs, but full systematic reproducible solutions.

As you grow you learn about building code that scales.  Efficient use of memory. Efficient looping.

As you collaborate you learn to write code that can be easily understood by others.  One half is good commenting, but the other half is using the clearest code to achieve the given outcome.

You learn how to isolate specific parts of the code to test for correct function.

You learn how to describe solutions to other people.

You learn how difficult it is to predict human behaviour.  You learn that human beings will tend to do the unexpected.  You learn that if it can go wrong, it will go wrong.

Everyone must learn to code

I do truly believe that I learnt more in my own self-guided programming of computers than in any classroom.  The social stuff I learnt in the playground and through sports.

What were the teachers doing?

Keeping me off the streets.

Advertisements

10 Commandments for Business Development from Goldman Sachs

John Whitehead, co-head of Goldman Sachs in the 1970s, wrote the following 10 commandments that guided their business development efforts:

  1. Don’t waste your time going after business you don’t really want.
  2. The boss usually decides— not the assistant treasurer. Do you know the boss?
  3. It is just as easy to get a first-rate piece of business as a second-rate one.
  4. You never learn anything when you’re talking.
  5. The client’s objective is more important than yours.
  6. The respect of one person is worth more than an acquaintance with 100 people.
  7. When there’s business to be found, go out and get it!
  8. Important people like to deal with other important people. Are you one?
  9. There’s nothing worse than an unhappy client.
  10. If you get the business, it’s up to you to see that it’s well-handled.
Good list.  What do you think?

I came across this list thanks to Mark Graham’s post over at The Entrepreneurs’ Organisation blog.

Jim Collins on the Writing Process

My favourite business books include Jim Collin’s “Good to Great“.  It is easy to read, simple but clear about the hard decisions that differentiate the great companies from the mediocre.  His new book, “Great by Choice” is out now.  Jim Collins is renowned as someone who has intense discipline in his life.  I loved when I found this text he wrote about his own process of writing:

Jim Collins on the Writing Process 

Jim Collins

“When I first embarked on a career that required writing, I devoured dozens of books about the process of writing. I soon realized that each writer has weird tricks and idiosyncratic methods. Some wrote late at night, in the tranquil bubble of solitude created by a sleeping world, while others preferred first morning light. Some cranked out three pages a day, workmanlike, whereas others worked in extended bursts followed by catatonic exhaustion. Some preferred the monastic discipline of facing cinder-block walls, while others preferred soaring views.

I quickly learned that I had to discover my own methods. Most useful, I realized that I have different brains at different times of day. In the morning, I have a creative brain; in the evening, I have a critical brain. If I try to edit in the morning, I’m too creative, and if I try to create in the evening, I’m too critical. So, I go at writing like a two piston machine: create in the morning, edit in the evening, create in the morning, edit in the evening…

Yet all writers seem to agree on one point: writing well is desperately difficult, and it never gets easier. It’s like running: if you push your limits, you can become a faster runner, but you will always suffer. In nonfiction, writing is thinking; if I can’t make the words work, that means I don’t know yet what I think. Sometimes after toiling in a quagmire for dozens (or hundreds) of hours I throw the whole effort into the wastebasket and start with a blank page. When I sheepishly shared this wastebasket strategy with the great management writer Peter Drucker, he made me feel much better when he exclaimed, “Ah, that is immense progress!”

The final months of completing Great by Choice required seven days a week effort, with numerous all-nighters. I had naively hoped after writing Good to Great that perhaps I had learned enough about writing that this work might not require descending deep into the dark cave of despair. Alas, the cave of darkness is the only path to producing the best work; there is no easy path, no shorter path, no path of less suffering. Winston Churchill once said that writing a book goes through five phases. In phase one, it is a novelty or a toy; by phase five, it is a tyrant ruling your life, and just as you are about to be reconciled to your servitude, you kill the monster and fling him to the public. And so, exiting the caving blinking in the sunlight, we’ve killed the monster and hereby fling. We love this book, and have great passion about sharing it with the world—making all the suffering worthwhile.”

My reflections

  • Writing is work.  You have to push through.  Every day.  It doesn’t get easier.
  • I am a different person at different times of the day.  I must use this better.  I start days slowly. I am inspired at midnight through to 3am.
  • Sometimes throwing everything out is progress.  It is not a step backwards.

What do you think?  Do you write?  What daily disciplines do you have?