Posts tagged productivity

How to fail a PhD

I read an inter­est­ing post today by Matt Might on “10 rea­sons PhD stu­dents fail”, and I thought it might be help­ful to reflect on some of the bar­ri­ers to PhD com­ple­tion that I’ve seen. Matt’s ideas are not all rel­e­vant to Aus­tralian PhDs, so I have come up with my own list below.  Here are the seven steps to failure.

1. Wait for your super­vi­sor to tell you what to do

A good super­vi­sor will not tell you what to do. PhD stu­dents are not meant to be research assis­tants, and a PhD is not an extended under­grad­u­ate assign­ment. So wait­ing to be told what to do next will usu­ally get you nowhere.

By the time you grad­u­ate with a PhD, you are sup­posed to be an inde­pen­dent researcher. That means hav­ing your own ideas, set­ting your own research direc­tions, and choos­ing what to do your­self. In prac­tice, your super­vi­sor will usu­ally need to tell you what to do for the first year, but even­tu­ally you need to set the research agenda your­self. By the third year you should cer­tainly know more about your topic than your super­vi­sor, and so are in a bet­ter posi­tion to know what to do next.

2. Wait for inspiration

Sit­ting around wait­ing for great ideas to pop into your ahead is unlikely to work. Most of my best ideas come after a lot of work try­ing dif­fer­ent things and becom­ing totally immersed in the problem.

A good way to start is often to try to repli­cate some­one else’s research, or apply someone’s method on a dif­fer­ent data set. In the process you might notice some­thing that doesn’t quite work, or you might think of a bet­ter way to do it. At the very least you will have a deeper under­stand­ing of what they have done than you will get by sim­ply read­ing their paper.

Research often involves dead-ends, wrong turns, and fail­ures. It’s a lit­tle like explor­ing a pre­vi­ously unmapped part of the world. You have no idea what you’ll find there, but unless you start wan­der­ing around you’ll never dis­cover anything.

3. Aim for perfection

Per­fec­tion takes for­ever, and so stu­dents who are aim­ing for per­fec­tion never fin­ish. Instead they spend years try­ing to make the the­sis that lit­tle bit bet­ter, pol­ish­ing every sen­tence until it gleams. Every researcher needs to accept that research involves mak­ing mis­takes, often pub­licly. That’s the nature of the activity.

Don’t wait until your paper or the­sis is per­fect. Work through a few drafts, and then stop, rec­og­niz­ing that there are prob­a­bly still some errors remaining.

4. Aim too high

Many stu­dents imag­ine they will write a the­sis that will rev­o­lu­tionise the field and lead to wide acclaim and a bril­liant aca­d­e­mic career. Occa­sion­ally that does hap­pen, but extremely rarely. A PhD is an appren­tice­ship in research, and like all appren­tice­ships, you are learn­ing the craft, mak­ing mis­takes, and you are unlikely to pro­duce your best work at such an early stage in your research career.

It really doesn’t mat­ter what your topic is pro­vided you find it inter­est­ing and that you find some­thing to say about it. Your PhD is a demon­stra­tion that you know how to do research, but your most impor­tant and high impact research will prob­a­bly come later.

My own PhD research was on sto­chas­tic non­lin­ear dif­fer­en­tial equa­tions and I haven’t touched them since. It showed I could do high level research, but I’d lost inter­est by the time I fin­ished and I’ve moved onto other things. Few peo­ple ever cite the research that came out of my PhD, but it served its purpose.

5. Aim too low

My rule-of-thumb for an Aus­tralian PhD is about three to four pieces of pub­lish­able work. They don’t have to actu­ally be pub­lished, but the exam­in­ers like to see enough mate­r­ial to make up three papers that would be accept­able in a rep­utable schol­arly jour­nal. Just writ­ing 200 pages is not enough if the mate­r­ial is not suf­fi­ciently orig­i­nal or inno­v­a­tive to be pub­lish­able in a jour­nal. Point­ing out errors in every­one else’s work is usu­ally not enough either, as most jour­nals will expect you to have some­thing to say your­self in addi­tion to what­ever cri­tiques you make of pre­vi­ous work.

6. Fol­low every side issue

Just because you use a max­i­mum like­li­hood method, doesn’t mean you have to read the entire like­li­hood lit­er­a­ture. Of course you will learn some­thing if you do, but that isn’t the point. The pur­pose of a PhD is not so that you can learn as much as you can about every­thing. A PhD is train­ing in research, and researchers need to be able to pub­lish their find­ings with­out hav­ing to be expert in every area that is some­how related to their cho­sen topic.

Of course, you do need to read as much of the rel­e­vant lit­er­a­ture as pos­si­ble. A key skill in research is learn­ing what is rel­e­vant and what is not. Ask your super­vi­sor if you are not sure.

7. Leave all the writ­ing to the end

In some fields it seems to be stan­dard prac­tice to have a “writ­ing up” phase after doing the research. Per­haps that works in exper­i­men­tal sci­ences, but it doesn’t work in the math­e­mat­i­cal sci­ences. You haven’t a hope of remem­ber­ing all the good ideas you had in first and sec­ond year if you don’t attempt to write them down until near the end of your third year.

I encour­age all my stu­dents to start writ­ing from the first week. In the first year, write a series of notes sum­ma­riz­ing what you’ve learned and what research ideas you’ve had. It can be help­ful to use these notes to show your super­vi­sor what you’ve been up to each time you meet. In the sec­ond year, you should have fig­ured out your spe­cific topic and have a rough idea of the table of con­tents. So start writ­ing the parts you can. You should be able to turn some of your first-year notes into sec­tions of the rel­e­vant chap­ters. By the third year you are fill­ing in the gaps, adding sim­u­la­tion results, tidy­ing up proofs, etc.


  • Share/Bookmark

Tags: , , ,

Backing up Gmail

I rec­om­mend Gmail to every­one who asks, and many who don’t, as it is far supe­rior to every other email plat­form around. But being para­noid, I don’t like all that valu­able email in some­one else’s hands. What if Google goes bust one day? Or the Aus­tralian government’s inter­net fil­ter stops gmail? Or I move to China? So I need a local backup just in case. I also need the backup to be pain­less and not require much attention.

The solu­tion is Thun­der­bird, but there is a bit of set­ting up to do at first, then you can sit back and let it do its work. The instruc­tions are here. You need to fol­low them — sim­ply set­ting up Thun­der­bird to access your gmail is not enough as Thun­der­bird won’t down­load your mail for local stor­age by default.

Once you’ve set up Thun­der­bird to down­load every­thing, all you need to do is open Thun­der­bird every few weeks and leave it to do it’s stuff.

If that’s too much work, you can always have Thun­der­bird open auto­mat­i­cally at start up but stay min­i­mized to the tray.

  • Share/Bookmark

Tags: , ,

Scheduling meetings

I don’t go to many meet­ings as I find they are largely a waste of time. In fact, I have the fol­low­ing poster on my office wall to remind every­one who walks in not to ask me to attend a meeting!

But I’m now a chief inves­ti­ga­tor of an NHMRC grant and I have to meet with other mem­bers of the team from time to time. We’ve started using Doo­dle to sched­ule our meet­ings, and it is so good I thought I should share it.

Doo­dle is a cloud-based way to sched­ule a meet­ing (or any event). Here is how it works.

  1. The per­son orga­niz­ing the meet­ing selects some poten­tial times and dates on Doo­dle, and then sends an email to all par­tic­i­pants with a link to a page where they can reg­is­ter their availability.
  2. Each per­son who receives the email clicks on the link and adds their avail­abil­ity to each of the pos­si­ble times/dates.
  3. The meet­ing orga­nizer can then see a sim­ple table show­ing when the best time for the meet­ing is.

This sim­ple pro­ce­dure saves a lot of emails and phone calls try­ing to sort out the best time.

I’ve since dis­cov­ered some other web-services that are sim­i­lar. The best of these seem to be Need­ToMeet and WhenIs­Good.

Of course, I’d still rather not go to any meet­ings, but if it is really nec­es­sary, using one of these ser­vices saves some time in sched­ul­ing when the meet­ing should be held.

UPDATE: I’ve just dis­cov­ered another ser­vice that looks eas­ier to use than any of those men­tioned above. Check out Sched­uleOnce — I think I’ll be using it from now on.

  • Share/Bookmark

Tags:

Saving web pages for later reading

Often I’ll come across a web­page that I want to read, but it is going to take more time than I have. For exam­ple, it might be an online research paper or a news­pa­per arti­cle, or it could be a lengthy blog arti­cle that you would like to read but you don’t want to sub­scribe to the whole blog. Of course, you could just book­mark the page, but book­mark col­lec­tions tend to grow wild and you might for­get to come back to it.

There is a very neat solu­tion to this prob­lem if you already use Google Reader (or some other feed reader) for online read­ing. Here are the required steps for set­ting it up.

  1. Set up an account on Instapa­per. This is a tool for sav­ing web pages for later reading.
  2. Go to http://www.instapaper.com/u and add the RSS feed (link at bot­tom right) to your Google Reader account.
  3. Read Later ← Drag this to your Bookmarks Bar.

Now every time you want to save something for later reading, just click the "Read Later" bookmark. A "Saved!" message will briefly appear in the corner of the page. The page will be saved to your Instapaper account, and so will automatically appear on Google Reader. Assuming you are in the habit of checking Google Reader every day or two, there's nothing else to remember.

You could read the page within your Instapaper account, but then you would have to remember to look at one more website, and I find it much simpler if everything I want to read turns up in Google Reader automatically. Apart from setting up the Instapaper account, you should never need to go back to the Instapaper website again.

It sometimes takes an hour or so for a page to turn up in your Google Reader account due to the frequency of refreshing the feed at Instapaper. But since you are saving it to read later, that is hardly a problem.

There are other similar services to Instapaper including "Read it later”. Pre­sum­ably you could do some­thing sim­i­lar with these other ser­vices, but I haven’t tried them.

  • Share/Bookmark

Tags: ,

Using Google Reader

Google Reader is a fan­tas­tic way to keep track of new papers that are appear­ing in many dif­fer­ent jour­nals, and also to fol­low some of the inter­est­ing research blogs (and blogs on other top­ics) that are out there. Google Reader checks web­sites for you and lets you know of any new mate­r­ial that appears. Instead of you hav­ing to look at dozens of dif­fer­ent web­sites to dis­cover new infor­ma­tion, all you need to do is open up Google Reader and all the infor­ma­tion comes to you. In some ways it is like an email account, but where the mes­sages con­tain new addi­tions to web­sites that you are inter­ested in.

Google Reader is called an “RSS reader” because it reads RSS feeds. RSS stands for “Really Sim­ple Syn­di­ca­tion”. A web­site with an RSS feed makes it pos­si­ble to track addi­tions to the site with­out actu­ally vis­it­ing it your­self.  There are other RSS read­ers, but Google Reader is the most widely used. Recently Google Reader added a facil­ity so that it now also tracks sites that don’t have RSS feeds.

If you haven’t used it before, here’s how to get started.

  1. Go to www.google.com/reader and log in. If you already have a Google account (e.g., you’re a Gmail user), then just use your usual Google details. If you don’t have a Google account, then you will need to set one up.

     

  2. Click “Add sub­scrip­tion” and type the URL of any web­site you want to track.
  3. When you are read­ing a web­site that you would like to sub­scribe to, click the orange RSS but­ton that looks like this: .
    A mod­ern browser such as Fire­fox or Chrome will fig­ure out that you want to sub­scribe to the RSS feed. If that doesn’t work, just copy the link address and paste it into the “Add sub­scrip­tion” box in Google Reader.

Each morn­ing I read through any­thing new on Google Reader includ­ing new research papers in jour­nals that I track, new arti­cles on some sta­tis­tics blogs that I fol­low, etc. In fact, I have over 500 sub­scrip­tions! I don’t read every arti­cle or it would take all day, but I do scan the head­lines and read what looks interesting.

It can take a while to col­lect all the sub­scrip­tions for jour­nals you might want to read. To make it easy, you can just piggy-back on my jour­nal col­lec­tion (which cov­ers all sta­tis­tics jour­nals, both fore­cast­ing jour­nals, plus a few econo­met­rics and demog­ra­phy jour­nals, as well as all sta­tis­ti­cal preprints on arxiv). Click here if you want to sub­scribe to all the same jour­nals as me.

If you are inter­ested in R, R-bloggers is very use­ful as it com­bines the posts from a large num­ber of blogs about R.  Just go to the site and click on the RSS feed icon and you will be able to add a sub­scrip­tion to your Google Reader account.

For those who like to keep up with LaTeX, the TeX com­mu­nity aggre­ga­tor does some­thing sim­i­lar for blog­gers writ­ing about LaTeX and related top­ics. Again, just click on the RSS feed icon.

Here is a list of sta­tis­tics research blogs. Check them out and sub­scribe to any­thing that takes your fancy.

This web­site has an RSS feed, as do my other web­sites. Just click the orange but­ton at the top-right of the page and select “Google Reader” and then you will receive any new posts I make in your Google Reader account.

  • Share/Bookmark

Tags: , , , ,

iPhone apps for research

I love my iPhone and I thought it might be help­ful to oth­ers who use iPhones to list the top 10 apps that I find use­ful for research.

  1. Gmail. It is easy to sync the native iPhone email app with your gmail account and this works pretty well for most pur­poses. But if you want to search more than the last 50 mes­sages, or you want to see the whole con­ver­sa­tion, it is also help­ful to have the app from Google. See http://www.google.com/mobile/mail/
  2. Google sync. It is also very help­ful to sync your iPhone cal­en­dar with Google cal­en­dar, and the iPhone con­tacts with Google con­tacts. Some instruc­tions are given here. (This is not an app, but a sug­ges­tion for how to use the con­tacts and cal­en­dar apps more effectively.)
  3. While we’re dis­cussing all things Google, read­ing research blogs is becom­ing an impor­tant part of my day and hav­ing a good app for that is impor­tant. The web app from Google itself is pretty good, but it has no facil­ity for read­ing offline. For that, you’ll need a native app with sync­ing to Google Reader.  I’m using Byline.
  4. I use my iPhone as a notepad and I like to have my notes avail­able on my com­puter as well. Unfor­tu­nately, the native notepad app doesn’t sync with PCs. I’ve tried a few other solu­tions, and the best I’ve found is NoteMas­ter which syncs with Google docs. It is not free, but the few dol­lars is well worth it.
  5. As I’ve pre­vi­ously explained, I like to use task-list soft­ware to stay orga­nized. I use Too­dleDo, and there is a nice app which syncs with my online to-do list. Again, not free, but worth a few dollars.
  6. A good sci­en­tific cal­cu­la­tor is handy. I’m using Touch­Calc which seems to work pretty well.
  7. I keep all my files backed up on Sync­plic­ity. I can access every file stored on my PC via my iPhone by going to https://my.syncplicity.com/. You can save the link to your home screen so it func­tions like an app.
  8. I can update this web­site, and my other sites, using the Word­Press app.
  9. Occa­sion­ally I need a dic­tio­nary, and the dictionary.com app is great. It also has a thesaurus.
  10. Time­Scroller is use­ful when I have a phone meet­ing with some­one in another time zone.

While I’m dis­cussing apps, the fol­low­ing will prob­a­bly never be used for research pur­poses, but I find them useful.

  1. Pocket Weather: much bet­ter than the native app and it access Bureau fore­casts so it is more accu­rate. It also shows cur­rent weather read­ings and fore­casts for nearby suburbs.
  2. Mobi­cast: the cricinfo app for cricket scores.
  3. Olive­tree Bible reader: the best Bible read­ing app available.
  4. ABC: for news (that’s the Aus­tralian Broad­cast­ing Cor­po­ra­tion for the Amer­i­cans who are read­ing this).
  5. Wikipedia: there are sev­eral apps out there. One nice one is Wikipan­ion
  6. Cycleme­ter: for the cyclists out there.
  • Share/Bookmark

Tags: ,

The 7 secrets of highly successful PhD students

It seems every­one has 7 secrets to suc­cess, and now some­one has hopped on the 7-secrets band­wagon with some­thing for PhD stu­dents. Thinkwell is an Aus­tralian com­pany offer­ing a sem­i­nar and asso­ci­ated work book on “The 7 secrets of highly suc­cess­ful PhD stu­dents”. I bought the book out of curios­ity, but “book” is a gross exag­ger­a­tion — only eleven pages of fairly sim­plis­tic advice. I hope the sem­i­nar has more sub­stance. For what it’s worth, here are the so-called seven secrets.

  1. Care and main­te­nance of your supervisor.
  2. Write and show as you go.
  3. Be real­is­tic.
  4. Say no to distractions.
  5. It’s a job.
  6. Get help.
  7. You can do it.

If you can work out what is meant from those head­ings, you’re doing bet­ter than me. After read­ing the “book”, I think a bet­ter sum­mary would be as follows.

  1. Meet reg­u­larly with your supervisor.
  2. Write up your research ideas as you go.
  3. Have real­is­tic research goals.
  4. Beware of dis­trac­tions and other commitments.
  5. Set reg­u­lar hours and take holidays.
  6. Make full use of the avail­able help.
  7. Per­se­vere.

Noth­ing too sur­pris­ing there. Per­haps it should have been called “Seven obvi­ous things PhD stu­dents should already know”.

If I haven’t put you all off, one of the authors is pre­sent­ing the sem­i­nar at Monash in a cou­ple of weeks. The details are as follows.

  • Pre­sen­ter:  Maria Gar­diner — iThinkwell
  • Date: Fri­day 16 Octo­ber, 2009
  • Time: 9:30am — 12:30pm
  • Venue: The­atre R2, Build­ing 8 (Rotunda), Clayton

Book­ings are essen­tial (Monash stu­dents only)

The same authors have writ­ten sev­eral other book­lets includ­ing “Time for research: time man­age­ment for PhD stu­dents”, “The PhD expe­ri­ence: what they didn’t tell you at induc­tion” and “Defeat­ing self-sabotage: get­ting your PhD fin­ished”. They are dread­fully over-priced and light-weight, but con­tain some snip­pets of use­ful advice. Stu­dents at Monash can bor­row the books from me.

  • Share/Bookmark

Tags: , , , ,

Workflow in R

This came up recently on Stack­Over­flow. One of the answers was par­tic­u­larly help­ful and I thought it might be worth men­tion­ing here. The idea pre­sented there is  to break the code into four files, all stored in your project direc­tory. These four files are to be processed in the fol­low­ing order.

load.R
This file includes all code asso­ci­ated with load­ing the data. Usu­ally, it will be a short file read­ing in data from files.
clean.R
This is where you do all the pre-processing of data, such as tak­ing care of miss­ing val­ues, merg­ing data frames, han­dling out­liers. By the end of this file, the data should be in a clean state, ready to use. It is much bet­ter to do this here rather than clean the data on the orig­i­nal file as this enables you to have a com­plete record of every­thing done to the data.
functions.R
All of the func­tions needed to per­form the actual analy­sis are stored here.  This file should do noth­ing other than define the func­tions you need for analy­sis. (If you require your own func­tions for load­ing or clean­ing the data, include them at the top of either load.R or clean.R.) In par­tic­u­lar, functions.R should not do any­thing to the data. This means that you can mod­ify this file and reload it with­out hav­ing to go back and repeat steps 1 & 2 which can take a long time to run for large data sets.
do.R
Here is the code to actu­ally do the analy­sis. This file will use the func­tions defined in functions.R to do the cal­cu­la­tions, pro­duce fig­ures and tables, etc. All fig­ures and tables that end up in your report, paper or the­sis should be coded here. Never cre­ate fig­ures and tables man­u­ally (i.e., with the mouse and menus) as then you can’t eas­ily reproduce.

It is a good idea to save your work­space after each file is run.

There are many advan­tages to this set up. First, you don’t have to reload the data each time you make a change in a sub­se­quent step. Sec­ond, if you come back to an old project, you will be able to work out what was done rel­a­tively quickly. It also forces a cer­tain amount of struc­tured think­ing in what you are doing, which is helpful.

Often there will be bits and pieces of code that you write, but don’t end up using, yet don’t want to delete. These should either be com­mented out or saved in files with other names. All analy­sis from read­ing data to pro­duc­ing the final results should be repro­ducible by sim­ply source()ing these four files in order with no fur­ther user intervention.

I’ve tried this process on a few projects and found it rather too restric­tive. In par­tic­u­lar, my do.R file often becomes large and unwieldy. Instead, I am now using the fol­low­ing process.

main.R
This file sim­ply con­tains a list of source state­ments to run each of the other R files in order.
functions.R
As above, all of the func­tions needed to per­form the actual analy­sis are stored here.  This file should do noth­ing other than define the func­tions you need for analysis.
xxx.R
All other code is con­tained in files of the form xxx.R which are called in an appro­pri­ate order by main.R. The num­ber and con­tent of these files will depend on the project. Often it will include a load.R file and clean.R file as above. How­ever, I usu­ally have more than one file con­tain­ing the actual analy­sis (instead of the do.R file).

The impor­tant part of this is that run­ning main.R will run the entire project from scratch. So if the data are updated, or the func­tions are changed, it is easy to repeat the entire analy­sis in one step — just run source("main.R").

It is impor­tant to be dis­ci­plined about keep­ing the R files neat and doc­u­mented. You want to be able to fig­ure out what each part of the code does when you look at it a year after writ­ing it. That means insert­ing com­ments and remov­ing any­thing that is not actu­ally used.

  • Share/Bookmark

Tags: ,

Take a break

Occa­sion­ally, the best research is done in long peri­ods of con­cen­trated effort. Allegedly, Isaac New­ton used to some­times write for eight hours stand­ing up with­out a break.

At other times, tak­ing a break helps the research process. Think of Archimedes and his Eureka moment. Many of my best ideas come while walk­ing, or tak­ing a shower. In fact, I once sug­gested to my head of depart­ment that we should have show­ers installed in every office as it would increase the qual­ity of our research.

Then there are the times when play­ing around with related ideas can lead to a new way of think­ing about a prob­lem. Some­times I read a paper on a related topic, or do some numer­i­cal cal­cu­la­tions in R, or browse through a book that might have some­thing of inter­est. In this mode, I try not to think too deeply about the spe­cific problem.

Most research tends to involve all three (and other) modes of work­ing. There are times when you need to shut the door, block out dis­trac­tions, and think hard. But after a while, if progress has stalled, it might help to go for a walk. If that doesn’t help, try play­ing around with some related ideas.

Recently, there has been some inter­est­ing research on the value of tak­ing a break. In a recent arti­cle on “Cog­ni­tive Ben­e­fits of Nature Inter­ac­tion” in Psy­cho­log­i­cal Sci­ence, it is reported

Nature, which is filled with intrigu­ing stim­uli, mod­estly grabs atten­tion in a bottom-up fash­ion, allow­ing top-down directed atten­tion abil­i­ties a chance to replenish.

(Thanks to Andy Hunt for the pointer.)
In other words, spend­ing some time in a nat­ural envi­ron­ment (in a park, on the beach, climb­ing moun­tains, etc.) will help our cog­ni­tive pro­cess­ing abil­i­ties. The peri­ods of con­cen­trated effort will be more effec­tive if you also include peri­ods of time enjoy­ing the nat­ural environment.

So go for a walk in the park with­out feel­ing you are wast­ing time. It is a valu­able brain regen­er­a­tion activ­ity, and will help you do bet­ter research.

  • Share/Bookmark

Tags: ,

Backing up

Ever since I deleted the only copy of my hon­ours the­sis, one week before it was due to be handed in, I’ve been obses­sive about back­ups, often to the amuse­ment of my fam­ily and col­leagues. But every time one of them loses a file or has a hard-disk fail, the smiles fade and they ask for advice.

I’ve used many sys­tems over the years, each one a lit­tle bet­ter than the last. Cur­rently, I have two com­put­ers — one at home and one at work. These are kept per­fectly in sync. Every file on one is avail­able on the other. So if my house burns down, I haven’t lost my life’s work (or at least not the elec­tronic files).

The sim­plest way to keep them in sync is to use an online back-up sys­tem. I use Sync­plic­ity, a truly awe­some piece of soft­ware. Every time I save a file on either PC, a copy goes fly­ing off into the clouds to be stored on my Sync­plic­ity account. So every file I have is also online, giv­ing me three copies in three loca­tions. Even when the uni­ver­sity is destroyed in a ter­ror­ist attack on the same night that my hard disk fails at home, all is not lost — I can still get the files from Sync­plic­ity. The prob­a­bil­ity of Syncplicity’s data ware­house in the US being destroyed in a tor­nado on the same night that Monash Uni­ver­sity is destroyed in a ter­ror­ist attack and my home PC fails is so small that I’m happy to live with it. Besides, if all three did occur at once I would con­clude that God wanted me to do some­thing else with my life.

When I turn on either PC, Sync­plic­ity will do a quick check against the online ver­sion of my files and down­load any­thing that has been updated. So I don’t even have to do any work to keep them in sync — Sync­plic­ity does it all for me.

You can spec­ify which direc­to­ries should be kept in sync. If you have less than 2Gb and only 1 or 2 PCs, the ser­vice is com­pletely free. I have paid for 50Gb which costs me $99 per year — not bad given the time it saves and the peace of mind it brings.

One great fea­ture of Sync­plic­ity is that it keeps pre­vi­ous ver­sions of each file. Occa­sion­ally I will stuff up and want to go back to a file as it was yes­ter­day. No prob­lems. Just hop on to my Sync­plic­ity account and down­load the ver­sion saved yesterday.

Another fea­ture that I haven’t yet used is that I can share a folder with another Sync­plic­ity user. So we can both have access to the same files with­out hav­ing to send copies back­wards and for­wards by email. The only trap here is that both peo­ple can’t edit the same file at the same time.

By the way, I did get my hon­ours the­sis back, but not before feel­ing nau­seous for about 10 min­utes, and only because I’d for­tu­itously installed some neat file recov­ery soft­ware the week before. (This was in the dark old days of DOS before there ever was a Recy­cle Bin or Trash Can.)

  • Share/Bookmark

Tags: ,