How to avoid time wasters when selling on eBay

I recently tried to sell my old MacBook on eBay, but the winning bidder had zero feedback and subsequently refused to pay. This was annoying, and it was only after this happened that I discovered eBay has some mechanisms to stop this kind of thing happening -- but they are disabled by default.

So, you really should enable these options if you want to prevent time wasters and scammers from bidding on your items. You can access the options, called "Buyer Requirements", by doing the following:

  • Login to eBay
  • Go to your Account Settings page
  • Click on Site Preferences in the left-hand menu
  • Under "Buyer requirements" click "Show" and then "Edit"

Here are the options I recommend:

  1. Block buyers who don't have a PayPal account.
  2. Block bidders and buyers who have 2 unpaid item(s) recorded on their accounts within 1 month(s)
  3. Block buyers whose primary delivery address is in a location I don't post to.
  4. Block buyers who have 4 breach of policy report(s) within 1 month(s)
  5. Block buyers who have a Feedback score of -1 or lower
  6. Block buyers who do not have a credit card on file. (Only apply this block to buyers who have a Feedback score of or lower.)
  7. Don't allow blocked buyers to contact me.

Buyer requirements recommended settings for eBay sellers

The Best Investments I’ve made in my Freelancing Business

Computer being delivered to Norwich City Council, 1957

At the beginning of the year, I vowed to invest resources in order to grow my freelancing business. Here is a list of the most successful in terms of return on investment.

“Recurring Revenue for Consultants” Bootcamp

Cost: $1,400

Hosted by Brennan Dunn and Patrick McKenzie, this contained around 6 hours of fabulous advice from two recognised experts in the field. I’ve wanted to diversify my income so that I was not so reliant on one-off client engagements. This bootcamp has helped to shape my product and service plans for the next year and inspired me to launch FreelanceDevLeads.

Link: Recurring Revenue for Consultants

CopyHackers “The Great Value Proposition Test”

Cost: $48.99

Any of the other CopyHackers books are worth owning, but I found this one particularly valuable. It helps you answer the question “how do you differentiate yourself from your competitors?”

Written in a clear, friendly style, it takes quite a dry subject and makes it compelling by focusing on real-life examples. It can be applied as much to products as it can to your own freelancing business.

Link: The Great Value Proposition Test e-book

FreeAgent

Cost: £150

FreeAgent makes accounting almost fun. At a general level, it has enabled me to keep an eye on my cash flow and make invoicing clients hassle-free.

Link: FreeAgent

Freelancer’s Weekly

Cost: Free

Great actionable advice from freelancing guru Brennan Dunn, someone who has been there and done it (and also written several books about it). More value-per-email than any other list that I'm subscribed to.

Link: Freelancer's Weekly

Virtual Assistant

Cost: £1,000

This year I’ve worked hard to document the different systems and processes within my business, so outsourcing some of these tasks was the next step. I use my VA for tasks such as research, lead generation and data entry.

PCG Membership

Cost: £120

Joining a professional organisation such as PCG is worthwhile to have support from other like-minded individuals. One of the perks of joining was a free consulting contract template. Considering the cost of lawyers, this was worth the price of membership alone.

Link: PCG

E-Myth Revisited

Cost: £6.67

This book really sold me on the idea of creating systems within my business to make it more valuable. If you take yourself out of the equation, your freelancing business is unlikely to be worth much unless you have some repeatable processes in place. (Oh, and try to ignore the cringe-worthy “Sarah’s Pies” anecdotes.)

Link: E-Myth Revisited on Amazon

I’d love to hear about your own successful investments. Add a comment below, or send me an e-mail.

Want to get freelancing tips from me? (no more than 1 e-mail a week, I promise!)


Making the leap to freelancing

Leap of faith by kodomut, from Flickr

Being my own boss was always a dream of mine, but it took two life-changing events for it to become a reality. Being made redundant from my job and the imminent birth of my first son meant I had a big decision to make. Should I look for another permanent position somewhere, or should I start out on my own?

“If you don't build your dream someone will hire you to help build theirs.” -- Tony A. Gaskins Jr.

I bit the bullet, and I have not looked back.

In this article, I’m going to highlight three of the most important aspects to consider when starting out as a freelance developer: setting goals, embracing the business mindset and finding work.

Motivation for going solo

For anyone considering going freelance, it’s important to set your own motivation and goals. When times are tough – and you will most certainly have downs as well as ups – these goals can help keep you on the right track. My priorities were:

  1. Maximising time spent with my family
  2. Be able to work remotely
  3. Work outside “normal” 9-5 hours
  4. Being able to cherry-pick projects of interest
  5. Having the ultimate decision in choosing technologies for projects

The word “freedom” could be applied to all of these. It’s the underlying motivation that drives me.

It was pretty clear from day one that just relying on my software development skills was not going to be enough to cut it out in the big wide world. I realised that I would need to juggle three quite different roles:

  1. Technician
  2. Marketer
  3. Salesperson

Getting into the business frame of mind can help you add marketing and sales skills to your repertoire.

You are a business as well as a freelancer

Keep in mind from the start that your are business rather than “just” a freelancer. Even if you are the only person involved, you are still a business and you should be running your freelancing operation as one. This means getting the balance between the three roles right. By just focusing on your craft, you’ll soon find your leads drying up.

A few books I can recommend to help you learn about these different roles:

  1. E-Myth Revisited (Michael E. Gerber, 1994)
  2. Winning Without Losing (Martin Bjergegaard and Jordan Milne, 2013)
  3. 4-Hour Work Week (Timothy Ferriss, 2011)
  4. Book Yourself Solid (Michael Port, 2011)

Finding work

I recently surveyed a few fellow freelancer’s about how they secured their first paying gig.

The two most common answers were a) going back to existing employers and b) referrals

Existing employers

Initially, this might seem a strange option -- why would you freelance for a company that you used to work for? Many reasons...

Companies are increasingly looking to take on freelancers, rather than permanent employees, for one-off projects. It's worth getting in touch with your existing employer(s) and seeing if there are any projects they would like to contract out. By approaching people you've worked with before, the level of trust is already there -- there is no need to prove yourself again. This also means it's less of a risk for the company you are approaching.

Referrals

Having a good reputation for what you do is essential. If you are good at your job, then people are likely to refer business onto you. For this to work you need to make sure that people know that you are freelancing, and actively seeking work. A simple Tweet to let people know your availability could be all that it takes for somebody to think "ah-ha, I know somebody that is looking for a web developer at the moment".

However, there are many other ways of getting work. Pick one and focus on it rather than spreading yourself too thinly. Any of these methods can be fruitful if you put the effort in.

  • Job Boards
  • Local networking events
  • Social sites such as LinkedIn

Summing up

A couple of years down the line, I am still working as a freelance developer and own my own software business. I can’t imagine ever going back to a daily 9-5 office job, and would recommend going solo to anyone. It’s allowed me to spend lots of time with my family, work with companies all around the world and even when I’ve been without work – which on occasion has lasted several weeks – something new and interesting has always turned up.

photo credit: Leap of faith by kodomut, from Flickr

Getting your first freelance development client

One of the most frequent questions I get from people after I have told them I'm a freelancer is how did you find work at the beginning?.

In the research for my book, I asked that very question to 50 other freelance developers and the results were interesting. Two particular methods stood as as the most popular options for getting initial clients.

Source of first freelancing client

Let's consider these two most popular options a little.

Existing employers

Initially, this might seem a strange option -- why would you freelance for a company that you used to work for? Many reasons...

Companies are increasingly looking to take on freelancers, rather than permanent employees, for one-off projects. It's worth getting in touch with your existing employer(s) and seeing if there are any projects they would like to farm out. By approaching people you've worked with before, you know the level of trust is already there -- there is no need to prove yourself again. This also means it's less risk for the company you are approaching.

Referrals

Having a good reputation at what you do is essential. If you are good at your job, then people are likely to refer business onto you. For this to work you need to make sure that people know that you are freelancing, and actively seeking work. A simple Tweet to let people know your availability could be all that it takes for somebody to think "ah-ha, I know somebody that is looking for a web developer at the moment".

Want to get more information on how to get freelance clients? My book goes into this in more detail, so sign up to be notified when it is available.

Don't Rest on Your Laurels

resting

I read a great article that describes the great life developers have right now, but raises a warning:

Don’t get too comfortable. Don’t get locked into a language. Don’t burn bridges for short term gain. Keep your tools sharp. Learn soft skills. Build an audience. Save some money. Network. Read.

There’s some excellent advice here, so let’s consider each point:

Don’t get too comfortable

Software development is a huge subject, and it’s a very fast-moving discipline. Web development is a great example of how you cannot afford to stagnate – for example, nobody is using table tags to build out sites any more, and for good reason.

Don’t get locked into a language

Whilst it’s great to master a language and/or a framework, try not to have tunnel vision: there are always alternative solutions so keep open minded about other languages.

Don’t burn bridges

This is especially pertinent when you are freelancing, but it also applies to permanent employees. Don’t tread on other’s toes, and try not to piss people off.

Keep your tools sharp

I wrote about this last time (see Know Thy Editor). The processes and tools that complement your software development are essential for your productivity.

Learn soft skills

Developing communication skills are critical to keep on top of your game. If you are working as part of a team, then you can practice this every day. Learn to actively listen, be courteous to others and don’t be afraid to take the initiative and lead whenever you can.

Build an audience

If you have knowledge, then spread the word and you’ll find yourself building an audience. The easiest way to do this? Teach through your blog.

Save some money

You never know what might happen in the future – tech companies are notoriously volatile. Have savings put away in case of emergencies. If you are out of work, then you will have a cushion to give you time to find something new.

Network

Meetup is a great resource for finding networking events. These may also be “soft” networking events such as co-working or tech talks. Remember that everyone you meet may be a potential client.

Read

Keep learning, but be particular about what you read. Pick one or two blogs to follow, find authors that you like and trust. Continue to learn: Coursera is a great online learning hub.

To sum up, don’t get complacent. Things are great for developers right now, but there are always ways to improve your craft.

photo credit: resting by Michael Cory, on Flickr

Know Thy Editor

Code

I’ve used many editors for programming over the years.

  • 1996 - 1999, Emacs
  • 2000 - 2007, BBEdit
  • 2009 - 2011, Emacs
  • 2012 - Present, Sublime Text 2

This week I was providing some mentoring with somebody that was using Notepad++ as their code editor of choice. What struck me was how few features of the program he was using. Cursor keys to move around. Not using the find function. Clicking rather than using keystrokes.

It was painful to watch!

The thing is, it doesn’t really matter which editor, or indeed IDE, you use. What’s important is how you use it.

As Andrew Hunt noted in The Pragmatic Programmer, use a single editor well.

Watching somebody who really knows their editor is a joy. I remember a few yers back marvelling at a colleague who used vim and he just flew around it. He had mastered it.

The most important thing is that you know your editor inside out. Be efficient. Be effective. It can make a huge difference to your software development productivity.

photo credit: Code by Riebart, on Flickr

Some Documentation is Better than No Documentation

LimeSurvey v2 schema

Ever started work on an existing software project that has NO technical documentation whatsoever?

I have recently, and I immediately felt lost.

No coding standards, no testing guidelines and most importantly, no notes at all about how the existing codebase was designed.

Why is this a problem? Well, for me it meant a lot of time reverse engineering the codebase and subsequently generating new documentation. I had to learn the project from scratch. It added a huge amount of time before I could do any real work on the project.

Every little piece of documentation that you add to your project can help save time later on – either for yourself or for another person working on the project.

What’s the minimum you should have in your project documentation?

  • Database schema in visual form
  • Coding standards
  • Source control branching strategy
  • Deployment instructions for all environments (e.g. staging and/or production)
  • Development environment setup

Wikis are perfect for collecting this kind of documentation. They are free-form, so you have freedom to structure as you wish.

Have no documentation at all? Fear not, it’s easy to get up and running. A few ideas to start with:

  1. Use a database management tool, such as MySQL Workbench, to reverse engineer your database schema and produce a graphical model
  2. Use your unit testing framework to produce agile documentation from your tests – for example, PHPUnit has a –testdox option for generating documentation.
  3. Start using standard inline documentation. For example, use phpDocumentor for PHP code.

Take a look at the documentation you have for the project you are currently working on. If a new developer came onto the project today, would the documentation be enough to get them up to speed? If not, what would you need to add?

image credit: LimeSurvey v2 schema by juhansonin, on Flickr

Premier League transfer rumours -- visualised

This is a visualisation of transfer speculation involving English Premier League teams, and their players. The rumours were taken from various sources, including the BBC, The Guardian and The Daily Mirror. Click on the thumbnail to view the full size image (around 900Kb).

The data was collected and saved as a graph as a set of nodes and edges. These were then visualised using Gephi and exported as a PNG. Thicker lines between players and teams means a greater number of reports (e.g. Wayne Rooney to Chelsea).

6 Books to Improve Your Freelancing Life

Here are the best books I've read recently that have helped to improve aspects of my freelancing career.

E-Myth Revisited

I could have done without the cringeworthy tales of "Sarah's Pies", but there many nuggets of advice in this book about creating processes and systems to grow your business.

The Checklist Manifesto

Related to the above, Atul Gawande gives some real-world examples of where the humble checklist have helped improve many situations -- and this is something that can easily be applied to freelancing.

Winning Without Losing

How to grow a successful business without having to work every hour in the day. I found this book aligned with my philosophy about building a business without impacting on my family life.

Switch

Changing behaviour -- for example in your client's businesses -- is difficult, and this book gives a solid framework to ease any transitions.

4-Hour Work Week

More good advice on creating processes and systems in order to free yourself from the more mundane aspects of running a business.

Book Yourself Solid

Describes a system whereby you can become an expert or authority in a particular market, and solve problems experienced within that field. Good advice about building up an audience that trusts you.

What books have you found helpful in your freelancing career?