Typora is a great Markdown editor that brings distraction-free writing to Windows and Linux.
.
There’s a full smorgasbord of Markdown editors for Apple users. Windows and Linux users who want to simplify writing have fewer options. Typora changes that.
It’s possible to run Typora on a Chromebook. While there are no versions for Android or iOS, that may change.
Markdown editors are stripped-back distraction-free writing apps. If you want to focus on getting your words onto the virtual page and nothing else, they are your best option.
With Markdown editors you can enter formatting codes directly into your text. A pair of * symbols tells Markdown the next few characters are in bold type and so on.
Keep it out of sight
Other Markdown editors tend to keep these codes in sight. You type onto a blank pages and can see your markup codes. You can then switch to a second screen to see how they look after formatting.
Typora doesn’t do that. In normal use, it styles the text as you type. This takes us back to an acronym that we don’t hear much these days: wysiwyg – what you see is what you get.
There is an option to choose a view with pure Markdown codes. Yet, for the most part, Typora keeps this out of sight.
I’m not convinced this is an improvement, but you may feel otherwise.
Themes
The other departure from standard Markdown editors is that Typora offers a series of themes. Many allow you to switch from dark text on a light background to light on dark, or perhaps, format the output in different ways.
Typora takes themes further than that. There is a theme gallery, you can download more themes If you are handy with CSS, you can create your own custom themes.
While this is neat, it is a form of distraction. Instead of procrastinating over font choices and layout options when using Microsoft Word, you can now waste valuable writing time looking at these themes.
Document format
There are Markdown editors that store files in a proprietary format. Thankfully, Typora does not do this. Proprietary formats are a backward step.
The files store as .md documents that you can open with other Markdown editors and applications or services that accept Markdown input. This can be handy if, say, you have a WordPress blog.
You can save direct to Word format if you need to stay compatible with colleagues. Typora has HTML and PDF output too.
Typora verdict
If you already use a Markdown editor, Typora can make sense if being able to see formatted text as you type appeals. I find it doesn’t help, but it doesn’t do any harm.
Typora is the best Markdown editor I’ve seen for Windows and Linux systems. If you want to simplify your writing and you use one of these, it is the smartest option.
If you are a Mac user, take advantage of the free trial period to see if Typora suits better than the other Markdown options.
Typora costs a one-off US$15. There is no cheeky annual subscription to worry about. I couldn’t find it in app stores, you can buy direct from the Typora site.
Is iA Writer 5 a text editor? Or is it a minimal word processor? The software is both and neither at the same time. It’s an elegant stripped down writing tool that’s perfect for 2018.
iA Writer starts from the premise that some writers focus on their words, not how they look on a page.
There are no distractions. The software has almost no moving parts. Words on a screen, that’s it. iA Writer feels the nearest thing to using paper in a typewriter and yet it is as modern as the iPhone X.
If you like your writing software flashy and complex go elsewhere. If you need to do tricky typographic work or lay out pages, this is not for you. It is a writer’s tool, pure and simple.
MacOS and iOS
There are versions of iA Writer for iOS, MacOS and Android. It works best with Apple kit. If you don’t use Apple hardware, the software is a good reason to change. If you have an iPad Pro, this would be a good time to invest in a keyboard, although iA Writer is fine if you write on a glass keyboard.
That’s because cloud is central to the software. You can store documents locally on a Mac, iPhone or iPad, but why would you when you can save them the cloud and have them sync between devices.
This works so well that you can type away on, say, a MacBook, race out the door and pick up from where you left off on an iPhone.
The app-OS-hardware integration has only improved with Apple’s recent move to iOS 11.
iA Writer a breeze compared to Word, Pages
Of course you can do much the same with, say, Microsoft Word or Apple Pages. Up to a point.
Word is a hefty MacOS app. It rarely starts without checking to see if there is a software update — usually once a week. Often you’ll need to wait 15 minutes or so before working while Microsoft handles the latest updates to all the Office apps.
Even when there are no updates Word is not instant on. iA Writer is ready immediately. Often a Word work session starts with something other than jumping straight into writing. Maybe you need to find the right fonts or styles. There are always things to fuss over.
With iA Writer you are ready to go almost from the moment you click the app’s icon. There is nothing to fuss over. Almost no possible choices to make.
Focus
The idea behind iA Writer isn’t new. A decade ago there were minimalist word processors and writing tools for Macs and PCs. You may recall WriteRoom or Q10.
There were others. And if you didn’t want a special app, there were the basic text editors shipped with operating systems and tools derived from the Linux or Unix text editors. Even the MS-Dos versions of Word Perfect were minimal in this way. So were older programs like WordStar.
All of them attempted to keep out of your way. In place of a fancy user interface and menus full of esoteric commands, they relied on the user learning a few standard codes. These were embedded among the words to handle things like bold text, heads and so on.
There is a WordPress OSX app that aims to simplify writing blog posts on a Mac. In practice I’ve found sticking with iA writer and integrating with WordPress is much more efficient.
Markdown
iA Writer uses Markdown to do this. Markdown is simple and keeps out of the way. Type a single hash # character at the start of the line for a top level head, two hashes means second level head and so on. It takes seconds to learn, days to master.
One key difference between iA Writer and earlier simple writing tools is the beautiful integration with the hardware, software and cloud services.
It’s as if the the software developers digested the entire Apple less-is-more credo and spat it out as a perfect writing application. Perfect is not too strong a word here. Although this style of perfection may not be to your taste.
iA Writer 5 rival
Only one other application comes close to iA Writer’s elegance and simplicity. The excellent Byword has its own minimalist aesthetic. It too is lightweight, simple and stays out of the way.
Unlike iA Writer which offers next to zero choices, Byword gives you some options. You can change a few things.
This may sound like a cop-out. It isn’t. I have a medical condition which means my eyes sometimes don’t work well. When I’m having bad eyesight days, I can’t adjust the iA Writer type to a bigger size, I can’t alter the font or screen colour to make reading easier. With Byword you can make these changes.
Subtle difference
The result is the two similar minimal writing tools have distinct personalities. They work for different types of use. iA Writer is all about the writing and precious little else. You can use it for complex writing jobs, but it works best for blog posts, putting down thoughts and things like journalism.
Byword is a touch more sophisticated. You can write a book or a 3000 long-form feature in either app. If you want something more, Byword is the first stop on the road from iA Writer to more complex tools like Apple Pages or Microsoft Word.
Efficient
There’s something else important about iA Writer and Byword. The two apps have an impact on the way you write. I find I can sit at a Mac or iPad and zip through a thousand words or so in quick time. This blog post will take less than an hour to write.
Between the minimal software and the Markdown editing language there is almost no reason to move your hands from the keyboard. That’s when you have one on a Mac or say with your iOS device.
With, say, Word, the composition part of the writing process takes longer. There’s more scrolling up and down the page. More distraction. Sure, you can make the words look pretty as you go, but that’s a barrier to getting the right words written efficiently.
iA Writer 5
In November iA Writer reached version 5. It was a free upgrade to those who had earlier versions. There are changes. First the iOS version now works with the new iOS file system.
There are other changes which added functionality without adding complexity. One is that it is now easier to create tables in text.
iA Writer’s other big change is there is a new duospace font. Since the software first arrived there has been no choice other than a standard monospace, typewriter-style font. Now you can choose monospace or duospace.
This sounds like a big deal. In many ways it is. And yet, you’d hardly notice it. I knew I had set the new font in my preferences after downloading the update, but had to go back a moment ago to check I was using it. That’s how subtle it is.
Indeed, while typing away you hardly notice any of the improvements in the last seven years and five versions of iA Writer. That’s the whole point of a minimalist application.
It may not work for everyone, but switching from Microsoft Word to a Markdown or text editor boosted my productivity.
Almost everything I’ve produced in the last 13 years was written first using Markdown.
If we want to be technical about it, Markdown is a simple, lightweight markup language.
At a pinch you can write Markdown using a plain text editor. It is better when you use an app. My favourite Markdown app is iA Writer.
Swiss Army knife
Microsoft Word is the writing equivalent of a Swiss Army knife. It aims to cater for every possible need.
Markdown and iA Writer are like one of those extra sharp Japanese cooking knives.
They do far less, but what they do, is done better with greater efficiency.
If you don’t know what life will bring you, the Swiss Army knife makes sense. But a chef would choose the latter to prepare a meal.
Simple, minimal, that is the whole point
The beauty of Markdown is there are a mere handful of commands to remember. There are few features.
That is a good thing. It means you can focus on writing words. Nothing else.
In this sense it is the closest thing to using a typewriter.
A few good commands
You can type out the commands for, say, bold text. That would be a couple of * symbols before and after the words you want in bold.
In a Markdown app you could also use Command-B (on a Mac) and the symbols are inserted for you. That’s the same code used in word processors like Microsoft Word.
This means there is almost nothing new to learn. You can be up and running with Markdown immediately.
Zero distraction
The advantage of this simple, minimal approach is you are not distracted by things that don’t matter.
There is no dithering over font choices or layout options.
Trust me, you can spend hours wondering if that editor waiting for your latest story prefers to get copy in Arial or Times Roman.
Faster
Simple means fast. A moment ago I fired up Microsoft Word on my state-of-the-art Apple M1 MacBook Air.
The app took three minutes to check for and download upgrades. Then it did something in the background before opening.
There are times when I have waited much longer to get started.
A Markdown editor is there immediately with a blank page ready to go.
Sure, there are times when I use Word. I have clients who expect to receive Word files or Google Docs. It can be easier to go there from the outset.
That said, converting Markdown to Word or Google Docs is no more than a mouse click away.
Comfortable
Markdown has another advantage. It is all about text.
If, like me, you can touch type, it means you can spend more time with your hands on the keyboard and less time mousing.
I find that over time Microsoft Word needs extra mouse activity – or touch screen action. That can give me overuse pains in my hands and arms. The more time you stay with the keyboard, the less discomfort.
It’s easy to miss this point, but if you find yourself cutting text from PDFs or web pages, pasting them into iA Writer is a cinch. Compare that with the fussiness that can happen when you past text into a word processor.
Markdown apps
Many of the posts on this site were written with iA Writer. A handful were written using Byword.
Byword is a Markdown Editor for Apple users. There is a Mac version and an iOS version that will also run on iPadOS.
iA Writer started life in the Apple camp. There’s a reason for that.
Markdown has a strong Apple lineage. One of the authors is John Gruber who runs Daring Fireball, a blog about Apple products and services.
Today there are Windows and Android versions of iA Writer.
iA Writer and Byline
For me two apps run on iOS, iPadOS, which for a long time was, in effect, the same as iOS, and they run on MacOS.
My first iOS version of iA Writer cost NZ$2.59 at the end of 2011.
It was, and remains, a bargain. That was the best $2.59 I ever spent on software. In 2016 iA charged a further NZ$5.99 for an upgraded app.
I’m not complaining. Even after buying MacOS apps, iA Writer works out at a fraction over one New Zealand dollar a year.
Phone, tablet, laptop, desktop
Because both apps store files in Apple’s iCloud, you can switch between Apple devices without missing a beat.
I can, and have, started writing on a phone, edited on a desktop, polished on a tablet and send from a laptop.
iA Writer and Byword are both solid apps. I recommend iA Writer over Byword because it has had more consistent attention from the developer over the years.
Although there is not a lot in it.
At the time of writing the most recent update of iA Writer was three months old. The most recent Byword was six months ago.
After a decade with iA Writer, it remains my main writing app on iPhone, computer and iPad.
There are a few minor niggles. iA Writer works best for my journalism and blog posts.
Once a story needs to go longer than a few thousand words it can be unwieldy. Last year I wrote around 4000 words for a book chapter using iA writer.
If that happens, I find it best to break the text into smaller chunks.
There is no question I’m more productive with Markdown than with any alternative. I get more done with less mental and physical strain.
People selling technology love using words like platform, ecosystem or environment.
Almost everything in the tech world is one of the three.
Some are all three. Hence: the Windows platform; Windows ecosystem and Windows environment. Are they the same thing are are they each different?
Likewise Apple, Android, AWS and so on.
The words are a problem for trained journalists because they are non-specific, even ambiguous. They rarely help good communication. We prefer to nail things down with greater precision where possible.
Often you can replace one of these words with thing and the meaning doesn’t change.
Platform: redundant, used badly
Or you can remove the word altogether. Usually Windows, Apple and Android are good enough descriptions in their own right for most conversations.
The other problem is that the words are used interchangeably. People often talk about the Windows platform when they mean the ecosystem.
There are times when you can’t avoid using platform or ecosystem. That’s not true with environment, the word is always vague or unnecessary.
Ben Thompson offers great definitions of platform and ecosystem in The Funnel Framework:
A platform is something that can be built upon.
In the case of Windows, the operating system had (has) an API that allowed 3rd-party programs to run on it. The primary benefit that this provided to Microsoft was a powerful two-sided network: developers built on Windows, which attracted users (primarily businesses) to the platform, which in turn drew still more developers.
Over time this network effect resulted in a powerful lock-in: both developers and users were invested in the various programs that ran their businesses, which meant Microsoft could effectively charge rent on every computer sold in the world.
Ecosystem:
An ecosystem is a web of mutually beneficial relationships that improves the value of all of the participants.
This is a more under-appreciated aspect of Microsoft’s dominance: there were massive sectors of the industry built up specifically to support Windows, including value-added resellers, large consultancies and internal IT departments.
In fact, IDC has previously claimed that for every $1 Microsoft made in sales, partner companies made $8.70. Indeed, ecosystem lock-in is arguably even more powerful than platform lock-in: not only is there a sunk-cost aspect, but also a whole lot more money and people pushing to keep things exactly the way they are.
Thompson then goes on to discuss why platforms and ecosystems are no longer as important as they were in the Windows era. His point is that in the past owning the platform and ecosystem was the key to sales success, today being the best product or service for a consumer’s needs is more important.
This story was originally posted June 2009. It remains relevant today.
People spend less time reading online news than reading printed newspapers because reading a screen is more mentally and physically taxing. For a closely related take on this see E-books harder to read, hard to comprehend.
This has consequences.
In Newspapers online – the real dilemma, Australian online media expert Ben Shepherd examined why online newspapers earn proportionately less money than print newspapers. He says it comes down to engagement. A typical online consumer of Rupert Murdoch’s products spends just 12.6 minutes a month reading News Corporation web sites. In comparison the average newspaper reader spends 2.8 hours a week with their printed copy.
Print still better in some ways
There are other factors. But I’d argue, the technology behind online reading is part of the problem:
Newspapers and magazines are typically printed at 600 dots per inch or higher resolution.
Computer screens typically display text and pictures at 72 pixels per inch. Some display at 96 dots per inch. This was the case in 2009 when the story was orignally written today’s phones typically have 300 to 500 dots per inch. Tablets are around the 200 to 300 DPI range. Laptops are 150 to 250 DPI. Desktop displays vary from 90 to 160 DPI.
Contrast is usually far better on paper than on screen.
Screens often include distracting elements. This can be particularly bad where online news sites have video or audio advertising on the same page as news stories.
Lower resolution means it takes more effort for a human brain to convert text into meaningful information. Screens are fine for relatively small amounts of text, but over the long haul your eyes and your brain will get tired faster even when there are no distractions. You’ll find it harder to concentrate and your comprehension will suffer.
Scientific reviews involve research, prising the back from things, taking them apart and dropping them on hard surfaces. Listening to noises. Measuring everything. Running battery life tests.
You come away from these tests with numbers. Often many numbers. Maybe you’ve heard of data journalism. This is similar, you need maths and statistics to make sense of the numbers.
Scientific reviews take time. And money. You need deep pockets to test things to breaking point.
Benchmarks
Benchmarks are one reason scientific reviews take so much time. You do them again and again to make sure. You draw up meaningful, measured comparisons with rival products. Then put everything into context.
We used the scientific approach when I ran the Australian and New Zealand editions of PC Magazine.
This was in the 1990s. ACP, the publishing company I worked for, invested in a testing laboratory.
We had expensive test equipment and a range of benchmarking software and tools. Specialist technicians managed the laboratory. They researched new ways to make in-depth comparisons, like the rest of us working there, they were experienced technology journalists.
The scientific approach to product reviews
My PC Magazine colleague Darren Yates was a master at the scientific approach. He tackled the job as if it were an engineering problem. He was methodical and diligent.
You can’t do that in a hurry.
There were times when the rest of my editorial team pulled their hair out waiting for the last tests to complete on a print deadline. We may have cursed but the effort was worth it.
Our test results were comprehensive. We knew to the microsecond, cent, bit, byte or milliamp what PCs and other tech products delivered.
There are still publications working along similar lines. Although taking as much time as we did then is rare today.
Publishing industry pressure
It’s not only the cost of operating a laboratory. Today’s publishers expect journalists to churn out many more words for each paid hour than in the past. That leaves less time for in-depth analysis. Less time to weigh up the evidence, to go back over numbers and check them once again.
At the other end of the scale to scientific reviews are once-over-lightly descriptions of products. These are little more than lists of product highlights with a few gushing words tacked on. The most extreme examples are where reviewers write without turning the device on — or loading the software.
Some reviews are little more than rehashed public relations or marketing material.
The dreaded reviewers’ guide
Some tech companies send reviewers’ guides. Think of them as a preferred template for write ups. I’ve seen published product reviews regurgitate this information, adding little original or critical.
T
hat’s cheating readers.
Somewhere between the extremes are exhaustive, in-depth descriptions. These can run to many thousands of words and include dozens of photographs. They are ridiculously nit-picking at times. A certain type of reader loves this approach.
Much of what you read today is closer to the once-over-lightly end of the spectrum than the scientific or exhaustive approach.
Need to know
One area that is often not well addressed is focusing on what readers need to know.
The problem is need-to-know differs from one audience to another. Many Geekzone readers want in-depth technical details. If I write about a device they want to know the processor, clock speed, Ram and so on.
When writing for NZ Business I often ignore or downplay technical specifications.
Readers there are more interested to know what something does and if it delivers on promises. Does it work? Does it make life easier? Is it worth the asking price?
Most of the time when I write here, my focus is on how things work in practice and how they compare with similar products. I care about whether they aid productivity more than how they get there. I like the ‘one week with this tablet ‘approach.
Beyond benchmarks
Benchmarks were important when applications always ran on PCs, not in the cloud. How software, processor, graphics and storage interact is an important part of the user experience.
While speeds and processor throughput numbers matter for specialists, most of the time they are irrelevant.
How could you, say, make a meaningful benchmark of a device accessing Xero accounts?
Ten times the processor speed doesn’t make much difference to Xero, or to a writer typing test into Microsoft Word. It is important if you plough through huge volumes of local data.
I still mention device speed if it is noticeable. For most audiences benchmarks are not useful. But this does depend on context.
Context is an important word when it comes to technology product reviews.
Fast enough
Today’s devices are usually fast enough for most apps.
Much heavy-lifting now takes place in the cloud, so line speed is often as big an issue as processor performance. That will differ from user to user and even from time to time. If, say, you run Xero, your experience depends more on the connection speed than on your computer.
Gamers and design professionals may worry about performance, but beyond their needs, there is little value in measuring raw speed these days.
Instead, I prefer exploring if devices are fit for the task. Then I write about how they fit with my work. I call this the anecdotal approach to reviewing. There has been the occasional mistake, my Computers Lynx review from 40 years ago was a learning experience.
Taking a personal approach this way is a good starting point for others to relate to their own needs.
My experience and use patterns almost certainly won’t match yours, but you can often project my experience onto your needs. I’m happy to take questions in comments if people need more information.
Review product ratings
I’ve toyed with giving products ratings in my reviews. It was standard practice to do this in print magazines. We were careful about this at PC Magazine.
A lot of ratings elsewhere were meaningless. There was a heavy skew to the top of the scale.
Depending on the scale used, more products got the top or second top ranking than any other. Few rated lower than two-thirds of the way up the scale.
So much for the Bell Curve.
If a magazine review scale ran from, say, one to five stars, you’d rarely see any product score less than three. And even a score of three would be rare. I’ve known companies to launch legal action against publications awarding three or four stars. Better than average is hardly grounds for offence, let alone litigation.
As for all those five-star reviews. Were reviewers saying a large proportion of products were perfect or near perfect? That’s unlikely. For any rating system to be meaningful you’d expect to see a lot of one or two-star ratings.
That doesn’t happen.
Loss aversion
Once I heard an advertising sales exec (not working on my publication) tell a magazine advertiser: “we only review the good stuff”.
That’s awful.
Readers need to know what to avoid as much as what to buy. Indeed, basic human nature says losses are twice as painful as gains.
Where possible, I like to warn against poor products. Companies that make poor products usually know better than to send them out for review, so you’ll see less of them, but it can happen.
My approach to reviewing products isn’t perfect. I’d like to do more scientific testing, but don’t have the time or resources. Often The review loan is only for a few days, so extensive testing isn’t possible. Reviews here are unpaid. This means reviewing has to take second place behind paying jobs.
More on media process:
SEO vs. quality – Why authority matters more than algorithms in the AI age.
This story was first posted in 2011 and needs a refresh, but the key points remain as relevant as ever.
Text editors are a lowest common denominator for dealing with documents. That is their appeal.
Plain text always travels smoothly between applications, operating systems and devices. The same can’t be said for Word documents or anything else that uses a proprietary format.
Text is compact and efficient. It is quicker to search and easier to manage than word processor documents.
Geeks already spend large parts of their working life dealing with plain text. Text is widely used for settings and configuration files. Geeks write small programs to merge, sort and otherwise process text files.
Plain text simpler than word processors
Text editors are simpler than word processors. Many have been around for more than 40 years and have roots in pre-graphical-user-interface computing.
They use keyboard commands — writing memos and other notes this way may look scary to non-technical types, but it isn’t much of a stretch if you’ve used the same tools to handle your everyday technical tasks for a decade or more.
There’s an added bonus to text editing; the applications can bypass the computer mouse. Given mouse movements are one of the most troublesome sources of strain injury, switching to keyboard-oriented writing tools makes sense for technical types who spend hours hunched over their machines.
Ergonomics
Similar ergonomic concerns explain why some professional writers turn their backs on conventional word processors. This group has another problem: modern word processors are busy-looking. It is hard to concentrate on writing when there are so many distractions.
It is tricky, but the old Dos favourite WordPerfect 5.1 could be shoehorned into working with Windows XP. Making it work with Windows Vista is more of a challenge. A small but vibrant user community at WP Universe provides tips and even drivers to make the software work with modern operating systems and hardware.
You’d need to buy WordPerfect. Two recently developed applications channel its spirit for free. Darkroom and Q10 are both stripped down text editors designed to offer distraction-free writing.
Darkroom fussily requires Microsoft .Net 2.0, a deal breaker for some, while Q10 mainly gets on with the job, but there is some beta-software strangeness with both programs. Perhaps for now, these text-editors-Word-replacements are a trend to watch and not follow.
In the meantime, find a basic, old-fashioned text editor. If you can adapt, it could be your biggest productivity boost of the year.
_While this was originally written in 2008 and the specific problems mentioned here are history, the main point remains as relevant as ever. _
Converting documents from one format to another can be hard.
Sometimes the problem is incompatibilities between different generations of the same application. Microsoft Word 2007’s docx file format isn’t automatically readable in older version of Word.
The same is true for files generated by Excel 2007 and PowerPoint 2007.
When you know in advance a colleague uses an earlier application version, you can choose to do the polite thing and save your document in the older format. This backward compatibility is built-in to Word 2007. Most applications offer similar backward compatibility.
Backward compatibility – up to a point
This is fine in theory, but you’ll either have to remember which format each colleague can use or you’ll just have to send everything in the older format. The problem with this approach is important things in the newer document format may go missing during translation to the older format.
If someone sends you a unopenable docx file – and you’re running an older, yet still reasonably up-to-date version of Word, you’ll only be able to work with the file if you’ve downloaded the Microsoft Office Compatibility Pack. This will also work with your Excel and PowerPoint files.
Things can be harder when converting files between applications from rival software companies or between applications running on different operating systems.
Not all software companies go out of their way to may conversion simple. Dealing with ancient documents from long-deceased operating systems is almost impossible. I’ve got MS-Dos Wordperfect and Planperfect files that I can no longer read.
Text, the lowest common denominator
Some geeks by-pass conversion problems by sticking with lowest-common-denominator file formats. Just about every application on any kind of operating system or hardware device that deals with text, from supercomputers to mobile phones and mp3 players can cope with data stored as plain text (.txt) files.
Text makes sense if you don’t need to keep style formatting information such as fonts, character sizes and bold or italic characters in your documents. An alternative low-end file format allowing some basic style formatting is .rtf, the rich text format. This was originally developed by Microsoft some 20 years ago to allow documents to move between different operating systems and it is still present as an option in just about every application that uses text today.
While I can no longer read my ancient Wordperfect files, I have recently found prehistoric documents from the early 1980s when I ran the CP/M operating system and a program called WordStar. Because they were stored as text files, they are still readable.
More than 20 years on, Macs and MacBooks are still not typewriters.
Yet Apple’s iPad might be.
My iPad links to an Apple Wireless Keyboard and runs iA Writer. This combination gives me the closest thing I’ve seen in 25 years of computing to an old-school manual typewriter.
For a journalist that’s a good thing.
Typewriter easy
Apple didn’t design the iPad with word processing in mind.
On its own the iPad is a poor writing tool. Although the larger on-screen keyboard makes for better typing than using a smartphone.
Yet here I am tapping away and loving the experience more than I have done since my last typewriter ribbon dried up back in the 1980s.
Have I taken leave of my senses?
Let me count the ways I love you
Three things make the iPad typewriter-like:
1. Radical simplicity.
The iPad, Apple’s Wireless Keyboard and iA Writer make for simple and distraction free writing.
There’s no mouse. That’s great because lifting hands off the keyboard to point and click is the number one cause of pain for old-school touch typists working on PCs.
Until you stop writing, the keyboard controls everything.
At the same time, the crisp serif text on a plain screen is the nearest thing to a type on a sheet of paper. Wonderful.
2. Text editor
iA Writer is a text editor. Not a word processor.
There’s nothing dancing on my screen. No pop-ups, no incoming email. At least not the way I’ve set things up.
It is just me and my words. The only word processor-like feature is the iPad’s built-in spell checker, which mainly stays out of the way.
Best of all, iA Writer doesn’t do page layout. I don’t care how my words look because I can’t tinker. That’s one less thing to worry about.
This all adds up to fast, productive writing.
3. Quick on the draw
Typewriters don’t need to warm-up, to boot or load applications. Nor does the iPad.
My normal morning practice with a laptop was to make a cup of tea while waiting for the PC to be ready for writing. The iPad is ready in seconds.
I can get my thoughts down while they are still fresh. The first 100 words or so are nailed on the iPad before I’d get started on the PC.
The best computer bits are still there
While my iPad writing combination kills the bad stuff about word processing, it keeps the best feature: The ability to go back over copy and make corrections. This was always a pain when using a typewriter.
And I send my writing to just about anywhere in the world in a matter of seconds. Try doing that with a real typewriter.
Other iPad typewriter plus points
My iPad and keyboard are a lot easier to carry than my ageing and neglected portable typewriter – and easier than my laptop.
The battery life is long. I can work a whole day without needing to find a power point.
iA Writer uses cloud storage. You can choose DropBox or Apple’s iCloud. This means my work is available to me on any computer anywhere in the world.
The Mac still might not be a typewriter, but the iPad does the job.
This post was originally written in 2008, hence the mention of Blackberrys. It’s just as relevant in 2026.
Any fool can write a good press release that hits its target audience and creates an impact.
Writing one that fails means work. There are people who have mastered the art.
As an editor I’ve seen some great efforts over the years. I’d like to share them with you.
Here are my top ten tips for making sure press releases get minimum attention:
1. Cripple its chances of reaching editors and journalists
Everyone can read plain text messages in the body of an email. The message will almost certainly get through to any kind of desktop email clients, all flavours of web mail, as well as Blackberrys, iPhones and Palm Pilots.
To reach less than 100 per cent of your potential audience, try putting some of these clever barriers in the way.
Attachments are an effective way of cutting down the reach of your press release. People reading email on mobile devices have trouble reading them. Spam filters treat them with suspicion and if you’re lucky the recipient may use Lotus Notes or some other arcane technology as a client and have difficulty decoding the attachment.
Another advantage of attachments is that you can trim your audience further by using difficult-to-open file formats: such as the new .docx file format used by Word 2007 – many journalists will struggle to read them.
Attachments are also great for bulking up the size of your release so it won’t squeeze through email gateways. If you’re clever, use high-resolution logos in, say, your Word attachments. These add nothing to the press release but can swiftly push the file size over the email gateway threshold.
A further reason for sending a press release as an attachment is its invisibility to email search. So, when a journalist finally decides to look for your press release among the hundreds and thousands in their email in-box, it will be difficult to find.
2. Minimise relevance
One way to make sure your press release fails is to make sure it has no relevance to any sane audience. For example, if you are a technology company and you buy a new fleet of cars you can squander your PR budget and make sure any future release goes directly to an editor’s recycle bin by sending the story to the technology press.
3. Send your press release out whenever
Timeliness is everything. So send releases out when you feel like it to boost your chances of failure. Better still, for print publications try waiting until five minutes after the final deadline. For online publications, wait until the story has already broken elsewhere. Editors love that.
4. Organise schedules so contacts are unavailable for interview
Good journalists are annoying creatures. Rather than printing your press release verbatim and passing the contact details over to their advertising departments, they may want to speak to the people mentioned in your releases.
A tried and tested technique for avoiding these complications is to send the people overseas shortly after dispatching the release. International communications are good these days, so just packing them off to a partner conference in Atlanta isn’t good enough, you need to make sure they are on an 18 hour trans-pacific flight or, better still, holidaying on a remote island.
5. Use poor writing skills
Obvious when you think about it. If your writing is poor and confused so that editors and journalists can’t understand your message you kill two birds with one stone.
First, you’ll make sure the first message gets spiked in the too hard basket.
Second, as a bonus, you can establish your reputation as an illiterate idiot that isn’t worth bothering with under any circumstances. That way, your future releases will go straight to the junk pile without even being read.
6. Try bullying
Sadly this powerful technique is underused. By threatening to talk to a journalist’s editor, or an editor’s boss about their poor response to your press release you can permanently undermine your relationship with scores of people (remember journalists talk to each other so this is an efficient way of burning lots of bridges).
Another approach is to tell the journalist the company in question is advertising in the publication thus triggering their professional editorial independence.
7. Don’t bother with press release photographs
Journalists and editors like photographs. They love good photographs. By making sure they are no photographs of any description you’ll increase the chances that your press release is regarded as useless.
If you think that’s taking things too far, try sending out crappy, unusable photos. Photos with dozens of un-named people work well in this respect. Getting people to hold champagne glasses, stand in front of company logos, gather around an unreadable normal-size bank cheque or impersonate public enemy number one mug shots are all effective techniques for creating instantly ignorable press release photographs.
8. Send it to everyone regardless
This is a great way to upset journalists and degrade both your personal and company reputation. At the same time if you work for a PR agency you can bill the client heaps for having a, er, comprehensive, mailing list and then bill them for time as you and your staff spend all day on the phone dealing with angry editors.
9. Keep your press release as dull as possible
Journalists prefer interesting stories. Public relations professionals recognise this and use clever tricks like passive sentences, boring ideas, irrelevant background facts, tired clichéd adjectives and implausible anodyne quotes to turn them off and help speed their press releases on their way to the great recycle bin in the sky.
In-house and government public relations people are usually better at delivering boring releases than agency staff – if you’re worried your writing sparkles too much, they have much to teach you.
10. Make sure the subject line obscures the message
Even experienced public relations operatives can slip up by giving an email release an interesting subject line. The danger is that after putting in all the hard work required to guarantee nobody takes the slightest notice of their press release they use active language to put a relevant, timely subject line message that tempts editors and journalists to open the document and read more.
The good news is there are fail-safe subject lines that are certain to turn off editors and journalists so they can just skip past your release. A classic subject line like press release will probably work, if that’s too simple try **important press release **or important press release from Company Name.
A neat by-product of badly written subject lines is they can fool spam detection engines into rejecting a message altogether; phrases like important announcement from Company Name or message for Clark Kent can come in handy here. Going straight to spam is the most efficient way of making sure your press release fails.
Want to guarantee journalists ignore your follow-up emails? Start them with “Good morning” so your message looks thoughtless when it arrives at 3pm, or worse, when they read it at 11pm while catching up on email.
Use time-appropriate greetings if you want to look professional. Or don’t, if your goal is to signal that you haven’t thought about the person on the receiving end.
A blog post, article or other piece of copy is what journalists call a story. Here’s how to write one.
You start a story by telling the reader what it is about. You do this briefly in the headline. Then again in the introduction or intro, which is a stop press paragraph.
Ask yourself:
what is this story about
what information am I trying to get across
what points must I make to do this?
Sum up the story in your mind in one simple sentence. This is your intro.
Its purpose is to tell the reader what the article is about and draw the reader in. As a rule, readers prefer brief intros.
Write so a reader who only samples your intro still has a basic grasp of your story.
Newspapers teach journalists — on both tabloid and quality papers — to start with a single sentence of between 15 and 21 words. This is what you should strive for, although at times you’ll need to use more words.
As an aside, proper nouns made up of multiple words only count as a single word when you’re calculating the ideal intro length.
Your first paragraph can be one sentence or three but keep it short and crisp.
Next comes the how: how did it happen or, more usually in your case, what happens next?
This is background information or explanation.
After the explanation comes amplification. You amplify the point or points following on from the intro.
Make these points one by one and in descending order of importance.
Last, after making all the main points, tie up any loose ends — that is add any extra or background information deemed necessary but of lesser importance.
Follow a few simple rules and you’ll be able to write decent, readable articles or stories about technology for any audience.
Good technology writing doesn’t come easy. Not at first
Most people can write simple, straightforward text even if they’ve little formal writing experience.
That is the best place to start.
Next you need to learn to put your readers first. Understand what they need to know and the barriers they might face getting to the information.
After that, good technology writing is about understanding your subject matter and clear thinking — then turning your thoughts into words.
If you can do this in a logical way, the shape of your story will lead the reader through the key points.
Step one: Start simple
Start by sticking to basic words and simple sentence structures. Don’t worry if this feels like plodding. You can experiment with language when you feel more confident.
Inexperienced technology writers often have one of four faults:
A pompous and overbearing style. Avoid this by being friendly, although not chatty. And use active language, it is easier to understand and unambiguous.
Too technical. In other words the writer does not explain the technical aspects clearly enough to non-experts. Fix the problem by keeping jargon to a minimum and explaining tricky ideas in simple terms. You can’t assume your readers know all the basics, so make as much of this as clear as possible. Don’t worry if this makes your writing longer.
Never worry if geeks tell you your technical writing is too simplistic. They are not the target reader and anyway they probably think they know everything about the subject already.
Trying to be cute. There’s nothing wrong with making jokes or using everyday speech, but beginning writers can take this too far, to the point where it is hard to understand their meaning. Think of how jokes often don’t work in emails or text messages.
Being non-specific. Avoid vague jargon like calling everything a ‘platform’ when you mean operating system, software or hardware. These days that word can mean just about anything.
Hitting the right note
Pitching your copy at the right level is the hardest part of technology writing.
Experienced technology writers know no one ever succeeds by overestimating the reader’s intelligence. They also know no one succeeds by underestimating readers.
Remember people who are expert in one area of technology, may not understand other areas. And a technically literate readership does not give one a licence for sloppy explanations of complex technical matters.
If you find this difficult, imagine you are writing for an intelligent colleague working in another area of your organisation.
Picture that person reading your words.
What questions would they ask if you were in the room with them? Make sure your text answers these questions.
Have you written something they would find patronising? Hit the delete button and make that point again.
Lastly, if you can, always get someone to proofread your copy.
Ask them to point out what doesn’t make sense and to see if you’ve made any obvious errors. Don’t take offence if they find things that need changing. Your pride will be more wounded if the rest of the world saw your mistakes.
Apply good writing to all your communications
Technology writers spend significant time communicating via email with sources, PR representatives and editors. The same principles of clear, thoughtful writing apply here.
One seemingly small detail matters: avoid starting emails with time-specific greetings like “good morning.” Your message might arrive when it’s not morning, making you look thoughtless. Use greetings that work at any time.
All you need to know about web writing in under 300 words. From my 2010 Wordcamp NZ presentation.
Start straight away. Don’t waste time warming up.
Reduce barriers between your ideas and your audience.
Write clearly. Use readily understandable language. Be unambiguous.
Learn grammar. Forget what teachers said about long words making you look smart. It isn’t true.
Instead use simple words, grammar and sentences. It is harder to go wrong.
Go easy on adjectives and adverbs.
Spellcheck.
Try to imagine your reader – an ordinary bloke or woman. Write for that person.
Use ‘be’ verbs sparingly to make your writing more interesting. Use them even less in headlines.
“I would have written a shorter letter, but I did not have the time.” Most people think it was Mark Twain; it was Blaise Pascal, a French Mathematician.
Keep sentences short; up to 20 words. A 15 word sentence limit is better.
Keep paragraphs short; usually one to four sentences. Only use more if you need to.
Use plenty of full stops and line breaks. Use lists and bullet points. Be generous with crossheads (secondary headings).
Highlight keywords with bold or italics.
Writing is story telling.
Summarise your story in the headline.
If you write an introduction use it to tell readers what your story is about. Expand on your ideas in the following paragraphs.
Write so you can cut the story at any point yet readers have the maximum information.
Aim for short and crisp. Online readers tire after 200 words and start dropping out at around 300. Keep most stories below this length although you can write longer pieces.
You can find longer explanations of all these points elsewhere on this site.
While all this remains true in 2026, there are good reasons to write more than 300 words. Google favours longer posts and readers are less scared of scrolling down than they were in the past.
Writing good morning at the start of an emai seems a good idea. The words sound friendly and upbeat.
It’s not as good as kia ora.
You don’t know for sure when your message will arrive at the other end. Nor do you know when the reader opens it. There’s a good chance it won’t be in the morning.
At best good morning when it isn’t morning doesn’t make sense. At worst, it looks rude. It says the writer hasn’t thought about the person at the other end.
This matters if you are in business. An out-of-place good morning might be interpreted as “I’m happy to take your money, but I’m too lazy to think about how you might read my email”.
Writers have no control over when people read their emails, so it is best not to start communications that way even when you’re in the same time zone as the reader. And if you are not in the same time zone, it only serves to underline the fact.
Assumptions
Good morning makes an assumption. If it’s the wrong assumption it can come across as arrogant.
If you want to seem polite or friendly, just start the email with hi or hello followed by the person’s name. Use the first name if you know them. Use the first and second name if you don’t or if you are uncertain.
Nothing signals the person at the other end is not paying attention more than getting this wrong. If I get an email that starts “Hello Bennett”, I know something odd is going on.
Kia ora
New Zealanders have two better options.
Kia ora is a Māori language – we call it te reo – phrase everyone should know. Strictly speaking it means “good health” but it is widely used as an alternative to “hi”. Kia ora is a great way to start an email.
The other possibility is g’day – a term we share with Australia. It’s seen as a little old-fashioned these days, but serviceable.
Hi, kia ora and g’day have the advantage of working at any time of the day or night. They don’t make presumptions about what is going on at the other end of the communication.
Both will set you apart from locals when you communicate with people in other parts of the world. It is is the best ice-breaker.
Good morning, g’day, kia ora, how are you? was originally posted on July 13, 2010 at billbennett.co.nz.
A handful of technology brands insist their names are written entirely in capital letters. In the past brands like Asus and Gigabyte pushed this idea. Today the Oppo phone brand likes to see its name appear in lights… sorry all capitals. There are other examples.
The jibe about ‘appear in lights’ is no accident. That’s exactly the effect companies who do this want.
Of course companies can write their names however they want
They don’t need to worry about being literate, sensible or easy to read. Although all of those things might help them.
Journalists should not write company names in capital letters. Their goal is to make information easy to understand.
This means ignoring demands to spell company names in capitals unless there are good, practical reasons to do otherwise. We’ll look at these in a moment.
Readers come first
Journalists serve readers, not markets nor companies. They do this by making information easy to get and understand. Messing around with capital letters interferes with that.
Capitals are the reading equivalent of speed bumps. They slow a reader’s flow. As you scan a text, your eye stops when it reaches a word spelled out in capitals. They appear in lights.
This is a reason companies want their name spelled that way. It increases the impact of the word. They thing words spelled out in capital letters stand out in text passages. They leap out from a page or screen.
Narcissistic companies
A less charitable interpretation is that spelling a company name in capital letters is a variation of [narcissistic capitals.](https://billbennett.micro.blog/2022/07/28/narcissistic-capitals-companies.html)
Puffed-up fools think capitals makes them look more important. It doesn’t. In fact it can do more harm than good.
Editors who nod through product names in capitals knowingly or unknowingly put brands’ interests ahead of their reader’s interests. There can be commercial pressure to do this, especially from companies that are potential advertisers.
Smart readers will realise this and learn not to trust the publication. For similar reaons, readers are, subconciously, less inclined to trust companies who insist their names are spelled in capitals. This may not be true in other cultures, but in ours, a name spelled all in capitals is a warning.
When company name are capital letters
We pronounce names like HP or IBM as a string of letters. It makes sense to write them as capitals. This doesn’t apply when company names are acronyms forming a pronounceable word.
Acronyms are words formed from a series of initial letters or parts of other words, such as: IBM, BBC, Unesco, WHO, Anzac, laser and radar.
Acronyms can make text simpler, easier to read and understand – life would be harder if you had to write light amplification by stimulated emission of radiation every time you refer to a laser.
Spell an acronym out in full the first time you use it unless you are writing for a specialist audience and the term is instantly familiar.
I prefer to write the full term, followed by the acronym thus:
The United Nations Educational, Scientific and Cultural Organisation (Unesco).
Others like to write the acronym, followed by its full title in brackets. Both are equally correct, it is a matter of editorial style. And there are times when you may want to swap, for example when someone uses an acronym in reported speech.
Confusing acronyms
If an acronym is confusing, don’t use it.
Some style guides allow acronyms written with full stops (or periods) between each letter or segment. I don’t. It’s ugly and adds nothing.
Likewise, there are those who think acronyms should always be written in capital letters. Again I disagree. In both cases the result is both inelegant and distracting.
You’ll notice in the examples above, I’ve written some acronyms in capitals, some with an initial capital and some in lower case. Here’s why:
Initialisms
When you pronounce the acronym as a string of letters, ie. eye, bee, emm for IBM the computer company, you should write the word in capitals. This type of acronym is an initialism. Linguists and grammar teachers make a distinction between acronyms and initialisms, but journalists generally tend to regard them as the same.
If the acronym is a word and spoken as a word, then treat it as a normal word with an initial capital if it is a proper noun. Otherwise with a lower case initial letter.
Some American newspapers automatically use an initial capital followed by lower case if the acronym had more than six letters.
One difficulty is deciding whether to use a or an before an acronym. The important thing is how it sounds when spoken. If the first letter sounds like a vowel, use an.
Certain acronyms were deliberately designed from the outset as pronounceable words. For example, Action on Smoking and Health (Ash).
T
he Economist Style Guide offers good advice:
…try not to repeat the abbreviation too often; so write the agency and not the IAEA, the Union and not the EU, to avoid splattering the page with capital letters. There is no need to give the initials of an organisation if it is not referred to again.
He mentions the editors' blogging and the way the BBC opened up its back-end to developers. Both matter.
His first item, the BBC’s web writing style, may prove more important in the long-term.
The organisation’s online news writers write crisp, tight news copy. They get right to the point, line up the important facts, then get out-of-the-way.
BBC learned the hard way
Bradshaw says the BBC learnt to write tight news stories when it ran Ceefax – a teletext information service which predates the internet. Ceefax allows little in the way of graphics and only 24 lines of 40 characters. Journalists had less than 200 words to tell their story.
Sharpening skills on Ceefax before the internet, gave the BBC a head start over other written news outlets which had become wordy thanks to larger newspapers.
Bradshaw says: “Even now it is difficult to find an online publisher who writes better for the web.”
The online team is even better at writing news headlines. Its editors compress the gist of an entire story into just five or six words. Most headlines fit inside that Ceefax page width of 40 characters.
Originally posted at billbennett.co.nz on Feb 21, 2011
Big companies worry about communications. They want every word they send out to stay on message. Their goal is to protect or promote brands.
This means a lot of unreadable corporate writing pours out of their headquarters.
Many companies have brand bibles. These are like editorial style guides – they standardise language.
Newspaper style guides are written to make life easier for readers. Brand bibles have other goals. They aim to help the company sell.
Counterproductive
That’s the theory. In practice this is often counterproductive.
Companies love complicated product names, often littered with jarring capital letters in weird places. Some add odd-ball punctuation. You’ll find trade marks and copyright symbols. Some pepper text with stock market abbreviations.
They give everyday nouns capitals. Some insist on spelling entire words in capitals. They use obscure acronyms and far too many adjectives. Often passive voice sauce is ladled over this sickly concoction.
You’ll even see companies refer to themselves and other companies in the plural, not singular. Perhaps they think this makes them sound like a bunch of fun people. In reality it makes them look like amateurs.
Companies often focus on writing about the wrong things, like dull histories. That is another story.
Corporate writing is often hard to read
None of this is easy to read. It doesn’t help the flow of information from one mind to another. Every non-standard affectation is like a roadblock on the highway to understanding.
Readers often switch off. They just don’t care.
And yet companies persist. Why?
They carry on turning out rubbish communications because it is safe. Nobody loses their job if they stick with the brand bible. Managers can tick off boxes all the way up and down the chain of command.
Sign off is guaranteed.
Everyone is happy. Except the poor soul who has to read the awful prose.
You might be interested in Technology writing for beginners. Follow a few simple rules and you’ll be able to write decent, readable articles or stories about technology for any audience without confusing or boring them.
Don’t waste time warming up when writing for online audiences. Get started straight away.
Readers are busy. They scan text looking for meaning and they want it fast. Other writing competes for their attention and it is only a click away.
Your first paragraph should summarise the entire story in less than 40 words. A 30-word intro is better. And make sure those words aren’t all in one sentence.
Don’t overload the first paragraph with too many facts. Save details for later.
Move straight to the action. Passive first sentences send readers fleeing for the exit.
Online, opening words are often a teaser to lure readers. If Google indexed your story, the first 150 characters become the descriptive text telling people what to expect when they click the link.
If you struggle to write short, snappy first paragraphs, imagine you are writing an old-style tweet. When Twitter still had its 140-character limit that was excellent training for writing introductions.
One of the great things about Micro.Blog is you can use it for quick social-media style thoughts or you can write a more expansive blog post.
Good blog posts communicate ideas and information. Do it with crisp, unambiguous writing.
There’s nothing wrong with flowery writing. Just leave it for poetry, song lyrics and literary fiction.
Here are seven steps to help you turn out snappy blog posts that’ll have readers coming back for more:
Get straight to the point. Set out your store in the opening paragraph. Tell readers what the rest of the story will be about. If you’ve got one, make the first paragraph your opening argument.
Prove it. Follow your opening paragraph by building on the first idea or argument. Provide back-up information to explain or support the first paragraph. Tell readers why you said what you did in that first paragraph.
Make extra points in descending order of importance. Readers can drop out at any point. Make sure they get the best points early while you still have their attention.
Use plenty of full stops and line breaks. Short sentences make your copy dynamic and fast-moving. Short paragraphs make text easier to read. This is more important online. As a bonus, tight copy helps you articulate your ideas.
Murder your darlings. If you think you’ve written something clever, chances are you haven’t. Hit the delete key and move on. Don’t use favourite obscure words or complicated metaphors. Anything that sounds like poetry needs cutting, unless you are writing poetry.
Get on, get off, don’t hang around. And don’t outstay your welcome. Don’t feel the need for a long wrap-up. Make your last point, summarise if it helps, then stop writing.
Check before hitting the send button. Read through your post, spell-check, look for poor grammar, weed out the needless words, make sure the text is understandable. I sometimes walk away from the screen and do something else before returning for one last read. The distance helps.
Learn grammar. Forget what teachers said about long words making you look smart. It isn’t true. Instead use simple words, grammar and sentences. It is harder to go wrong.
Finding simple words isn’t always easy, especially when you are in a hurry.
A thesaurus helps. There are online thesauri and there are two paper ones on my bookshelf at home. There’s a thesaurus built into MacOS.
Thsrs is a short word thesaurus designed to help social users find shorter words to fit in tight character limits. Thsrs is a great tool for digging out a simpler, easier-to-read alternative, option, choice.
You may call it a blog post, article or something else. A journalist would call it a story. Here’s how to write a good one.
Start your story by telling the reader what it is about. You do this briefly in the headline. Then again in the introduction or intro, which is a stop press paragraph.
Ask yourself:
What is this story about,
what information am I trying to get across and..
what points must I make to do this?
Sum up the story in your mind in one simple sentence. This is your intro.
Its job is to tell the reader what the article is about and draw the reader in.
As a rule, readers prefer brief intros.
Write so a reader who only gets as far as your intro still has a basic grasp of your story.
Newspapers teach journalists to start with a single sentence of between 15 and 21 words. This is what you should aim for, although at times you’ll need to use more words.
As an aside, proper nouns made up of multiple words only count as a single word when you’re calculating the ideal intro length.
You can have one sentence in your first paragraph or two or three. Either way keep it short and crisp.
Next comes the how — how did it happen or, more usually in your case, what happens next?
This is background information or explanation.
After the explanation comes amplification. You amplify the point or points following on from the intro.
Make these points one by one and in descending order of importance.
Last, after making all the main points, tie up any loose ends — ie., add any extra or background information deemed necessary but of lesser importance.
Years ago, when training journalists, I would joke that Americans use more commas than British journalists because they are rich and can afford the extra ink. The same applies to journalists in Ireland, Australia or New Zealand.
You would often find long, comma-packed sentences in American newspapers. They don’t make for easy reading.
It’s better to write using plenty of full stops instead — periods if you’re American — and go sparing on the comma.
Keeping track of who does what to whom is hard in long, comma-laden sentences. Breaking sentences into smaller units of meaning makes writing easier to follow.
Only use commas where they aid understanding.
Writers often underrate the comma’s use as an aid to sense.
Some Americans put commas between all clauses and sub-clauses. Som grammar checking software tells you to do the same.
British-trained writers avoid them between short clauses at the start of sentences.
Americans also use commas before and at the end of a list of items. This is sometimes called the Oxford comma. As the name suggests, this is an not exclusively American habit.
Argument in favour of the Oxford comma seems to be gaining ground in some circles. That’s partly because writers who favour the Oxford comma have trained us to read prose the way we might read a formal logic argument.
Some experts say Americans are moving towards British patterns and commas are now less common on both sides of the Atlantic. Let’s hope so.
One last point. Neither approach is right or wrong. How one uses commas and full stops is a matter of editorial style, not grammar. The important thing about style is to be consistent.
Follow a few simple rules and you’ll be able to write decent, readable articles or stories about technology for any audience.