This site is helped by many donations- thanks
Full list of articles

walking Camino Real in winter

A pal who has just walked the whole Camino in winter (finished a few days ago) had this to say about his kit choices:

"The kit was amazing.  The Paramo Cascada jacket with ‘one’ long-sleeve icebreaker merino sleeve was good in ‘feels like’ -9C whilst walking.  With another merino and / or gilet, good when stationary too.  And kept me dry when it pissed it down torrentially for 4 hours.  Loved the gaiters - kept the trousers clean and made me look, and feel, like a ‘pro’.  Biggest surprise hit was the icebreaker merino wool beanie.  When it arrived in the post one day before leaving I was, “ah fuck!  I’ve ordered the wrong item”, but for the first time I had a breathable, tiny, lightweight head-covering that kept me comfortably warm but not too hot - love it.  Total Osprey convert.  Items I should have taken but didn’t... a change of shoes (man, should have got those crocs!); and, a small dry bag for phone / wallet."

Get out there!


angry emails

Write the angry email. Keep it as a draft for a few minutes. THEN Delete it and write the same message in a cunning way, with humour and self-deprecation but still firm, still achieving the same result.


what you need to know about new technology

1. Technology goes through three phases: inventing, developing, maturing. Once a technology is mature it rarely disappears forever. Even wooden ploughs are still being used because they have a utility in places where welding is difficult and costly. The notion of obsolescence is replaced with that of increasing breadth of option. Technology in the inventing and developing phase moves forward, but in the maturing phase it just moves sideways, fanning out, ever increasing our options. 

2. Recognise when a technology is entering the maturing phase. New versions show ever smaller improvements. They answer non-universal problems or even non-existent problems (a parking camera?). Disproportionate cost goes into small improvements. The technology moves slowly- predictions replace actual developments. This is the key moment- when you cease to be surprised by a new technology - it just appears in the market place- and have to be told to wait until 2020 or some other date, then you know the technology has entered a fanciful immitation of development- when actually it is either mature or even a failure. Think driverless cars and nuclear fusion here.

3. The internet is now a mature technology. Already people are working around it, putting up with its intrusions, using it, sure, but not being used by it.

4. New technology is always beneficial at first and then increasingly negative in its effects. Sometimes terribly so, sometimes not.

5. To predict the future better think of technological developments as spreading ever wider in a widening front that faces the future and yourself at that widening front looking out. The technology is vastly secondary to other concerns you may have about the unknown facing you...


what car design tells us

Cars over the last ten years have got harder and harder to see out of.

They resemble increasingly chopped and squashed hotrods with tiny perfunctory windows and lowered roofs.

In the past - starting in the 1960s- we saw a move towards more and more visibility. Huge acres of glass- the old Mercedes 350SL, the humble cortina, the mini metro and early Nissan Micra. There were glitches- the Ford Capri and later Cortina were a step back towards less visibility- but generally the move was: better visibility equals better safety.

This assumes the burden of safety is mainly on the driver. An active view. But now cars are increasingly like padded boxes. Egg boxes for people yet to be even chickens. Less visibility, not more. Passive safety not active safety.

Increasingly the mainstream culture sees people as not to be trusted....


developing ideas

Lots of people have ideas. Writers develop ideas.

I have just finished a book about computing, by a computer expert, not a writer. It was long winded and didn't say much because the ideas, and there were some, were buried, thrown away, not developed. One was: what if you designed an operating system without files. Are files as integral to computing as we think? This idea- which is interesting and kind of amazing (apple's very first OS tinkered with a no files concelt until Steve Jobs decided to embrace them) is just left hanging out to dry.

Taking an idea and turning it over in your palm, as a diamond cutter turns over a gem, looking for lines of interest, where it will crack open, what potential jewel is hidden within- all this the work of the writer.

Often writers have LESS ideas than normal folk. But they are good at spotting good ones, stealing them and running with them. Unpacking is mainly what writers seem to do.


the database problem revisited

I am very indebted to my friend Rob Walters, a computer telephony engineer and author, for telling me all about the 'database problem'. Indeed it is one of the founding laws of creating databases: there shalt only be ONE database. You have a calendar in your office and one at home. You update them both, kind of, but sooner or later one slips ahead...and then you get real problems. Neither database becomes absolutely reliable. Things start getting stressful...

Multiple access points for communication are a form of database problem. You have the mobile, you have the home phone, you have twitter, facebook and email- and maybe instagram, linked in and pinterest too. Each one allows communication. Of course you can keep everything on your mobile and keep checking through all of them- kind of like having four calendars on the wall all next to each other- still overkill and still room for missing things.

Many people I know have given up having a home phone and the mobile becomes the main portal for everything. The problem is- it's never off. And there is no hierarchy of communication. Everything from the utterly trivial to earth shattering is 'normal' for it. Noise increases. Stress increases.

Always aiming for one database is an ideal worth striving for. Unattainable perhaps, but all steps in this direction are useful. Communication technology 'uses us' more than we 'use it' when we service multiple databases, wasting our time keeping them all updated.


What robot wars can teach us about design

Robot wars is hard to resist. A bunch of engineers and fabricators of machines compete to build a robot that can kill all other robots. What’s interesting is to see the evolution of design- which is part determined by the robot arena and partly by the opposing robots.

The arena is a caged off zone- maybe the size of a squash court with a few tethered house robots that are larger than the competers but fairly predictable. They stick to their patch so it’s important not to break down within their ambit. There are various hazards- a hole that appears- which once you are in is very hard to extricate yourself from.

But the major design influence is the opposing robot.

At first the robots looked cool and robot like. This changed over time as top heavy robots proved easy to flip. So new ones became flip friendly- able to right themselves or even run when upside down. They became sleek and wedge shaped with hidden wheels – and all had wheels- none have legs which I guess would make it too hard to be an evenly matched game.

The robots defeat each other either by smashing, cutting, flipping or electrocuting the opposite machine. For a while no technology prevailed then it became apparent that a bit of each didn’t work. Your robot had to commit to one tactic or another. Hammer wielding smashers worked for a while. Then wedge powered flippers were the rage. Then a team looked at the rather feeble circular saws on some robots and built a spinning rotor- like a mower rotor- out of turbine steel. It was lethal and virtually unbreakable. Just getting the tip of your robot caught by this killer device could result in it being spun out of the arena.

Of course you need speed, manoeuvrability, armament and the ability to react to being flipped- but at the end of the day you need unstoppable firepower that is fast. A hammer or even a taser is a bit slow. A rotating blade is like a gatling gun- devastating. Momentum is what halts another object- Mass multipled by velocity. Mass is not enough. And speed is not enough. Thinking about devices that raise both of these easily (things that spin rather than oscillate, stop-start) is a good way forward.

Even when designing other products think about its momentum, think about ways of making it spin so as not to need constant inputs of energy to keep starting it again. Think of a book, instead of being launched (with the inevitable return to earth), being put in a series of low orbits that just keep rising. What a ‘low orbit’ would be or what form this spinning would take would obviously differ for each product.

Page 1 ... 2 3 4 5 6 ... 93 Next 7 Entries »