Tag Archives: IT

What’s e-new? How to be your own IT department

This article by Andy Coulson, for the regular What’s e-new? column in members’ newsletter The Edit, looks at how to cope when things go wrong with your technical set-up, from initial troubleshooting to simple fixes, and where to look for more help and advice.

The article covers:

  • Backing up before you start
  • Being methodical
  • The power of the off button
  • Diagnostic tools.

As self-employed professionals, we have to wear a number of hats. One of the least popular and worst fitting is the IT hat. Let’s face it, for most of us faced with IT problems the challenge is avoiding a rapid descent into playing laptop frisbee. But there is a lot you can do to resolve IT problems for yourself and build your confidence and skills in tackling those in future.

Before you start

If you read no further, please, please, please take this one thing on board. Back up all your important files regularly. Also, do it before you try making changes to your system. If you have Microsoft 365 and Windows 10 this should be automatic for a lot of your documents, but here’s how to do it: https://support.microsoft.com/en-us/office/back-up-your-documents-pictures-and-desktop-folders-with-onedrive-d61a7930-a6fb-4b95-b28a-6552e77c3057. If you use a Mac, it is a little more complex: https://techcommunity.microsoft.com/t5/office-for-mac/how-to-use-onedrive-for-backup-on-mac/m-p/29589. Both Mac (Time Machine) and Windows (Backup/File history in settings) have good internal backup systems that also back up the Windows or MacOS. Take a little time to learn how to use them, buy an external disk drive and set them to automatically back up on a regular basis.

When you have a problem with IT there are typically three areas: simple hardware, like a loose plug, covered below in ‘Be methodical’; simple (often inexplicable!) software issues, covered in ‘The power of the off button’; and more complex problems, covered in ‘IT A&E’.

1. Be methodical

When a problem occurs, you need to step away for a moment and be really methodical about it. Say your printer isn’t working. The first port of call in the absence of any other clues (such as a message on screen) is to check physical things: Is it switched on? Is the power plugged in? If it uses a cable to connect to the computer, is that plugged in? At both ends? You don’t need to know much about computers to check these things – you need to look carefully, wiggle plugs to make sure they are fully pushed in, and follow cables to make sure the right ones are plugged in. But the point is to be methodical and thorough.

2. The power of the off button

If a program appears not to be working then closing and restarting it is a good starting point. If the program has frozen, then in Windows, press Ctrl, Shift and Esc at the same time. This causes Task Manager to pop up, and from here you can right-click on the frozen application and select ‘End task’ to close it. On a Mac you use the Option, Command and Esc keys, select the app in the Force Quit Applications window, and then click on ‘Force Quit’. If you then reopen the application, it should run normally.

If this doesn’t work then try restarting the computer. I’m always slightly concerned by how often turning something off and back on is a solution to software issues, but it is nevertheless a fairly reliable method. This can cure some apparently serious issues. For example, if I try and do a reboot on my laptop, I get an alarming-looking blue screen saying ‘Do you want to start Windows in Safe Mode?’ when it restarts after shutting down. With a little help from Google I quickly realised a) this was not a drastic problem, and b) I couldn’t fix it easily, and if I simply used the power button to switch off and then start up again all was OK.

A related solution worth trying if you are having Word issues in Microsoft 365 is to use the repair function. In Windows 10 if you go to ‘Settings’, then ‘Apps’ and find Microsoft 365, click on ‘Modify’ and you will get a pop-up that prompts for a ‘Quick repair’ or ‘Online repair’. Try a Quick repair, and if this doesn’t work run the Online repair (but be prepared to be patient).

3. IT A&E

If you have an error message or make no headway with the earlier fixes, then you need to try some diagnostics to get to the bottom of things.

Google is one of the simplest diagnostic tools to use. If you have an error message, search for the text and any error number in Google. For Windows and Word issues it will often have answers from Microsoft’s knowledge base near the top. These can sometimes be a bit techy, but they are generally accurate and safe. As you get away from Microsoft and Apple’s pages be prepared to be cynical and critical about where the information comes from, as there are bad sites out there. (For example, I would trust a reputable technology site or magazines like Tech Republic or ComputerWorld over a random post on Reddit.)

Device drivers (the software that speaks to the hardware) have a reputation for being a source of problems. With Windows 10 these are generally updated automatically, but occasionally a manual install can resolve a problem. This windowscentral.com article – windowscentral.com/how-properly-update-device-drivers-windows-10#page1 – can guide you through the various options in the order in which you should use them. If you can use the first method, it will be the safest as it uses drivers that Microsoft has tested.

Both Microsoft and Apple provide inbuilt diagnostic tools that can help to identify issues, particularly in hardware. For example, Windows has a number of these tools:

  • Task Manager – Run this using Ctrl-Shift-Esc to see what software is running and how much memory and CPU effort it is using. This can help you spot programs that are doing something odd (for example using a lot of CPU %).
  • Performance Monitor – This can give you an idea about what might be slowing your PC down. You can find it under the ‘Windows Administrative Tools’ section in the Start menu. You can also see something similar under the Performance tab in Task Manager.
  • Reliability Monitor – This is quite well-hidden, but it allows you to visualise how reliable your system is and get historical access to error messages. The easiest way to find it is to search for ‘Reliability history’ in ‘Settings’.
  • Windows Disk Management – This can flag potential issues with disks. This is under the ‘Windows Administrative Tools’ section in the Start menu.

As you go along, it is worth keeping notes on things you fix, preferably not on the computer. This will help by reminding you of what you have done, so you can fix things that happen again. It’s also a good thing to look back over and realise how much you have learned.

Finally, it is worth finding a local computer repair person and building a relationship with them for the times when you can’t fix it yourself.

Summing up

The article has looked at:

  • The importance of backing up files before performing fixes
  • Where to start with diagnosing and fixing problems
  • Simple fixes
  • Finding out more about problems
  • Where to go for more help

What else is e-new?

Andy has written many articles demystifying software and technology. Check out:

About Andy Coulson

Andy Coulson is a reformed engineer and primary teacher, and a Professional Member of CIEP. He is a copyeditor and proofreader specialising In STEM subjects and odd formats like LaTeX.

 

 

About the CIEP

The Chartered Institute of Editing and Proofreading (CIEP) is a non-profit body promoting excellence in English language editing. We set and demonstrate editorial standards, and we are a community, training hub and support network for editorial professionals – the people who work to make text accurate, clear and fit for purpose.

Find out more about:

 

Photo credits: dog desktop support by Pavel Herceg; blue screen by Joshua Hoehne, both on Unsplash.

Posted by Abi Saffrey, CIEP blog coordinator.

The views expressed here do not necessarily reflect those of the CIEP.

How I got started – Graham Hughes

SfEP deskOne of the most common questions asked at Society for Editors and Proofreaders (SfEP) local groups and by those interested in pursuing a career in editing or proofreading is: ‘How did you get started?’.

SfEP professional member Graham Hughes shares his story in this regular blog feature, which explores the many different career paths taken by SfEP members.

This really wasn’t part of the plan. From a ridiculously early age – around 14 – computing was the only career I could foresee for myself. I did the O Level, A Level and degree, and joined British Rail (yes, we’re going back a bit) as a programmer.

After about 15 years, several changes of role and a few changes of employer, I was in a rut. Fresh opportunities were limited by my old-fashioned technical skills, and the work was becoming mundane. I started looking for something else to do – first as a sideline, and maybe eventually as a career.

I saw an advert for the Writers Bureau’s Comprehensive Writing Course. This seemed like something I could do. I’d always felt comfortable working with documents, as well as programs. I did the course – most of it, anyway – and went on to have a sports history book, and some articles, published. Soon, though, I was struggling to produce ideas and convert them into paid work. After two years of not quite setting the world alight, my book was remaindered. The idea of making a living from writing seemed far-fetched.

So, what next? Another Writers Bureau course caught my eye: Proofreading and Copy Editing. It struck me that checking my material – rather than actually writing it – had probably been my main strength. How about checking other people’s material, and getting paid for it? Also, as Richard Hutchinson explains in his blog post on how he got started, there are parallels between programming and editorial work.

A plan came together: (1) do the course, (2) re-edit the book (yes, I now realise I probably should have used someone else), (3) self-publish it as an ebook, (4) look for work as a proofreader or editor. The last part was the tricky one.

My first job wasn’t quite what I’d had in mind. After I’d emailed the leader of a local writers’ group, one of its members asked me to type a short play script that he’d handwritten. He accepted my offer to edit it as well, so it felt like some kind of a start.

After that, finding work was very tough. With my full-time employment in IT, I couldn’t take on big jobs, or even smallish time-critical ones. I joined the SfEP, after dithering for several months, and started learning a lot about proofreading and editing, especially from the SfEP forums – but progress was snail-paced for the next year or so.

The big change came when my IT job ended, semi-voluntarily. Rather than looking for a new one, I decided (nervously) to focus on freelance editorial work. I did look for in-house editorial jobs close to home, but there seemed to be nothing available for someone with my limited credentials. The next few months were very challenging: a few small jobs, then nothing for nearly three months; but my progress with the Publishing Training Centre (PTC) Basic Proofreading course gave me some hope.

Then, suddenly, the work started coming – mostly from students, largely thanks to the Find a Proofreader website and a helpful, nearby SfEP member with an overflowing workload (thanks Helen). Around this time (spring 2014), I completed the PTC course, along with other training, and became an ordinary member of SfEP (now known as professional member), which helped to bring in more work. To shore up my finances, I downsized from a suburban semi-detached house to an urban flat (no great wrench), wiping out my mortgage.

Since then, things have been gradually coming together. I’ve been doing more work for business rather than students, also proofreading two books for a publisher. I’m now leaning more towards editing, to make use of the decent writing skills that I feel I have (though you might disagree, reading this). Technology and business have become my predominant subject areas. Via a long-winded route, I think I’ve ended up in my ideal job.

If you’re thinking of getting into editing and/or proofreading, I strongly recommend it, if you think it’s right for you and vice versa. Being a keen reader isn’t enough: you need a sound understanding of spelling, grammar and punctuation, a knack for paying attention to detail, a professional attitude and a willingness to stay positive and persistent as you build your business. If that’s you: good luck!

Graham HughesGraham Hughes still can’t quite get used to the idea of telling people he’s a proofreader and editor, rather than saying he’s ‘in IT’. He started doing part-time editorial work, and joined SfEP as an associate (now known as entry-level member), in 2012. He went full-time in 2013, before becoming an ordinary member (now known as professional member) of the SfEP – and an online forum administrator – the following year. To learn more about his background and services, please visit the GH Editorial website.

Proofread by SfEP entry-level member Susan Walton.

The views expressed here do not necessarily represent those of the SfEP.