They say you learn something new every day.

Posts tagged ‘computers’

Less Advanced Than You Think (24/03/2012)

I remember a while back reading that “Listen Again” (the radio version of iPlayer) only accounts for 2% of all radio consumed. And being amazed.

This was in 2009, so it may not still be true now, but I don’t expect it’s moved that much.

The thing is: most people aren’t as technically advanced as you think. Not being they’re stupid, they’re just not as interesting as you are (especially if you’re reading this, you’re almost certainly in the top quartile. Even if you don’t think it, you probably are: you’re reading a blog for Christ’s sake. Most people don’t even know what a blog is.)

A colleague of mine has to give a presentation about a Corporate iPhone AppStore that we’re building. Half way through, he realised the audience weren’t feeling it, and so said, “Who here knows what an appstore is?”. About four people their hands up.

It’s back to this thing about making basic applications. Almost no one cares about fancy features. It’s why the iPad and iPhone have taken off, even though they have the computing capacity of my eight year old laptop. Get the key basics right – the things people are actually interested in – and you’ve got them. And get those bits sorted before you start adding all sorts of new features that no one wants.

Advertisements

Couldn’t give a Flying Duck (15/03/2012)

There’s a great post on CodingHorror about solving problems by explaining the problem very clearly.

Bob pointed into a corner of the office. “Over there,” he said, “is a duck. I want you to ask that duck your question.” 

I looked at the duck. It was, in fact, stuffed, and very dead. Even if it had not been dead, it probably would not have been a good source of design information. I looked at Bob. Bob was dead serious. He was also my superior, and I wanted to keep my job.

I awkwardly went to stand next to the duck and bent my head, as if in prayer, to commune with this duck. “What,” Bob demanded, “are you doing?”

“I’m asking my question of the duck,” I said.

One of Bob’s superintendants was in his office. He was grinning like a bastard around his toothpick. “Andy,” he said, “I don’t want you to pray to the duck. I want you to ask the duck your question.”

I licked my lips. “Out loud?” I said.

“Out loud,” Bob said firmly.

I cleared my throat. “Duck,” I began.

“Its name is Bob Junior,” Bob’s superintendant supplied. I shot him a dirty look.

“Duck,” I continued, “I want to know, when you use a clevis hanger, what keeps the sprinkler pipe from jumping out of the clevis when the head discharges, causing the pipe to…”

In the middle of asking the duck my question, the answer hit me. The clevis hanger is suspended from the structure above by a length of all-thread rod. If the pipe-fitter cuts the all-thread rod such that it butts up against the top of the pipe, it essentially will hold the pipe in the hanger and keep it from bucking.

I turned to look at Bob. Bob was nodding. “You know, don’t you,” he said.

“You run the all-thread rod to the top of the pipe,” I said.

“That’s right,” said Bob. “Next time you have a question, I want you to come in here and ask the duck, not me. Ask it out loud. If you still don’t know the answer, then you can ask me.”

It’s a really good point. Too often, we just haven’t sorted through things clearly enough in our head and that’s why we struggle to come up with the solution.

I read this, this morning. And while I haven’t had chance to try it out yet, I can think of times when I’ve done it. And now that I’m aware of it, I’m going to make a greater effort to think through the question when I’m facing a problem.

Moving Times (11/02/2012)

I’m moving house again.

These days, I seem to move house almost every year. I think it gets easier over time. I can’t say I’ve got it down to a fine art (like George Clooney travelling in Up in the Air) but I’ve down it enough times now to know to keep the boxes stored somewhere between moves and things like that.

This time, because I’m hoping to buy a flat soon, I’m renting somewhere for six months which means I’ll be moving again in 5 and a half months time. In some ways it’s a little unsettling. In other ways, it’s upsetting. Of all the places I’ve lived in London, this is my favourite, and I’ll be sad to see it go. Of course, if all goes according to plan, I’ll be moving back in a few months time to a nearby flat. But you never know until the keys are in your hand.

The process has flagged a few things to me though.

It’s made me realise how expensive moving is. But also helped put money into perspective. Sure, you end up paying several hundred pounds in one month, but in no time at all, that cost disappears. Costs are quite transitory like that. It’s reminded me that money is just there to buy you freedom and happiness and to pay for your life. Obviously, your expectations of money vary depending on how much of it you have. When you have enough for a deposit, you start thinking about buying a flat. If you just have enough for a few drinks, you maybe think of going to the pub. The amount you have affects how you think about life.

It’s also made me realise that so few of the things that make me happy cost money. Spending time with my friends and with L. Reading and writing. Messing around with computers and code. Films and TV. These things are largely free. Obviously I need a computer, and maybe I could get a big TV. But these are minor things. What I really want is to have my own place to live which is mine and is safe so no one can take it away (like our previous landlord did).

Finally, it’s reminded me again how much stuff I have. But, more crucially, how little of it I really use. I’ve felt this lesson keenly the last few Christmasess, where I’ve wanted a WiFi Radio (used for about a week, then stopped using), cordless headphones (used for about a month, then gave up) and some GameCube games for my old games console (played for about a week).

The only thing I’ve got that isn’t now just taking up more space as I lug it from place to place is my Kindle. Which I love. There are so few things like that. Other than my computer, laptop, phone and kindle, there aren’t any other consumable electrical devices that I want. I don’t even have room in my life for them.

But it’s more than that. As I empty my cupboards, I’m shocked by just how much stuff is there. I haven’t really forgotten about any of it, it’s just when you see it all, it amazes me how much there is. And it’s faintly confusing how I feel like I need it, and I can’t throw it away, but I never use it.

Half of my moving time seems to go into boxing up things that I don’t want.

I’ve learnt that I don’t need to buy any other things (I forgot to mention my jumping stilts and my mini laptop, that sit around unused these days).

I’ve learnt that I don’t need much stuff. And in fact, I should spend more time focusing on what I do want. Give the stuff you do want to use space to breath rather than cramping it in with stuff you don’t want. It’s like designing a user interface. You don’t cramp the button you’re going to use a lot right at the bottom of the screen surrounded by buttons you never use.

Finally, I reminded again about recalibrating. I’ve always known I like having fewer things. When I move I always clear up as well. I always say I’ll just get out what I need. But I still have so much stuff. I almost need to pack all my stuff up every month or six months, just how much there is that I don’t need.

Less Manual Work (08/02/2012)

I’m reminded again about this bit of wisdom from Coding Horror:

Truly lazy developers let their machines do the work for them. This is partially motivated out of self-interest, it’s true, but smart developers know that people don’t scale— machines do. If you want it done the same way every time, and with any semblance of reliability, you want the human factor removed as much as is reasonably possible. I know for every problem I encounter at work that causes me to lose time, I ask myself— how can I make sure I never have to deal with this problem again? If my solution fixes it so nobody ever has to deal with that problem, that’s a nice side-effect, too.

It’s close to my heart, because I’m very lazy as I keep saying.

But while I know this, and I mean it and I say it to anyone who will listen, I keep encountering problems that I solve by doing a bit of manual work. And suddenly, I’ve got loads of manual systems that I’m involved with.

I don’t really know a way around this. This is something so close to my heart, and yet I still get caught up in things and end up in a manual mess. I think the only thing to do is keep track of all your project somewhere, and recalibrate regularly – possibly every month. If this blog has taught me anything it’s:

  1. Doing things regularly works. But only if you stick at the regularity
  2. You need to recalibrate regularly. More regularly than you think. As humans we get used to things very quickly.

Unlocking the Scroll (26/01/2012)

Do you know, after all this time, it was only today that I discovered what the Scroll Lock key does. There’s been a couple of times in Excel when I’ve found that the arrow keys are scrolling the window rather than moving cell, and I’ve assumed that there was a setting on, but it was only today that I thought it might be scroll lock.

So scroll lock sets the arrow keys to scroll the active window. Simple, eh? But I’ve never realised that before. And, asking around the office, no one else had either.

Of course the question now is whether I can actually use this knowledge in anyway way. I suspect it’s not that useful, but at least I’ll know to turn it off when Excel starts behaving weirdly.

Apples and Pears (21/01/2012)

I’m a Windows user. Yes, you can stop booing now. But I don’t get Macs. I don’t get why they’re all white. I don’t get why there’s only one mouse button. I don’t get why everyone gets so excited about them being “pretty”. My fridge isn’t pretty (it is white though), but I still like that. Unfortunately, I’ve been required to use a mac at work to run our internal iApp store using xCode.

The process of using it has been a bit of an eye opener as well as a much needed slap in the face. I tend to think I’m good at computers, but using a Mac I feel so left handed. Even the simplest of tasks, like navigating to a downloaded file, is incredibly difficult. This must be how my Mum feels when using a computer. Given this, there are probably some things to learn about teaching people how to use computers.

However, while I’ve been trying to be balanced, there are some elements of the mac user interface that I think are objectively wrong.

Don’t get me wrong. There are some bits that are great. This, for example, is brilliant:

This is brilliant

You can’t tell just how great it is here, because it’s a picture, but in the real one, the fingers move. This is a great way of  explaining a quite complex task.

Of course, like all great things, it looks like this has been shamelessly copied:

Shamless copy

It’s clearly been “inspired” by the Apple feature. But the CGI fingers aren’t nearly as nice as the real ones. Not to mention the fact that there are more tick boxes and closer together in the Windows version.

However, I’m not ready to switch to macs just because they have a nice animation.

One of the big problems with the Apple interface is that too much stuff is hidden and not obvious unless you know it. Take the iPhone. How was I supposed to know that double tapping the click button loads up the “task manager”? I didn’t even realise double clicking the click button was a valid action.

There’s so much of this. To right click, you hold control and click. How is that obvious? I’m reminded a comment a friend of mine made once that good games, and applications, allow you to see the state of play and work out valid moves just by looking at the board or screen. Apple applications hide valid moves away. It creates a clique. Which, to be honest, is probably what they’re trying to do.

Also, I’m with Tog, the Apple dock is rubbish. It’s huge and takes up way too much of my screen estate. I had a Windows dock app once. And you know what, I turned it off. I like the quick start bar in Windows. It’s small. I like the start menu. It’s hidden.

I also find it strange how related items are physically distant from each other. Which is made more apparent in applications that load windows all over the screen. Of course, this is part of the maximizing button behaviour. Maybe I should just accept this as a tom-are-to/tom-ay-to thing (although, let’s be clear: the former is English, the later is American. It’s not a free choice which one to use, it’s an accent!).

But I like my windows maximized to my screen, so I can see what’s going on. Having floating windows encourages me to waste my time organising windows. And dragging and dropping windows is not work.

I think really, there are two things for me to learn here. Firstly, be humbled by my computer abilities. As I’ve said when I started this. I’m stupid. We’re all stupid. And I’m never be anything but stupid. However, if I learn something new every day, I might end up a bit less stupid than I started.

Secondly, UI design is tough. And teaching computers is tough as well. You can never make the design too simple, the text too easy to read or too short. It’s something I continue to work on with my software management application at work. For this to be successful it needs to be really easy to use and the text I send out needs to be so simple people grasp it almost immediately.

All is not lost (19/01/2012)

Support@tumblr.com were unable to retrieve the post I lost. It’s one of the first things I can think of that I’ve irrevocably lost on a computer. It’s somewhat ironic, because I’ve only just started my backup plans.

The “missing post” was about some free OCR software called tesseract. It’s not a massively important post, and I have a copy of the one key thing about it (the command line syntax) which is:

tesseract.exe FILE output -l eng

As well as, somewhat ironically, the pictures. Unlike Jeff I’ve kept the pictures but lost the text.

Here they are, showing the effect of the update. Accuracy of old version:

Old version

Accuracy of new version:

New version

However, I don’t want to talk about what’s missing.

Since I started my aim to learn something new each day, I’ve managed to write something every day. But losing this post was the first time that made me think, “oh damn, is it worth it”. It really annoyed me – perhaps more than it should.

There’s a section in Transformative Entrepreneurs where Jeffrey Harris talks about what makes people successful:

Successful entrepreneurs combine optimism, creativity, passion, courage and perseverance. They have an uncanny ability to keep going when times get tough. They have such excitement about what they are doing, and a need to prove to the rest of the world that their idea has merit and that they don’t quit.

Now, admittedly, losing one post isn’t the biggest set back in the world. It’s nothing compared to the set backs Mr Honda went through before his company became successful:

Like most other countries, Japan was hit badly by the Great Depression of the 1930s. In 1938, Soichiro Honda was still in school, when he started a little workshop, developing the concept of the piston ring.

His plan was to sell the idea to Toyota. He labored night and day, even slept in the workshop, always believing he could perfect his design and produce a worthy product. He was married by now, and pawned his wife’s jewelry for working capital.

Finally, came the day he completed his piston ring and was able to take a working sample to Toyota, only to be told that the rings did not meet their standards! Soichiro went back to school and suffered ridicule when the engineers laughed at his design.

He refused to give up. Rather than focus on his failure, he continued working towards his goal. Then, after two more years of struggle and redesign, he won a contract with Toyota.

By now, the Japanese government was gearing up for war! With the contract in hand, Soichiro Honda needed to build a factory to supply Toyota, but building materials were in short supply. Still he would not quit! He invented a new concrete-making process that enabled him to build the factory.

With the factory now built, he was ready for production, but the factory was bombed twice and steel became unavailable, too. Was this the end of the road for Honda? No!

He started collecting surplus gasoline cans discarded by US fighters – “Gifts from President Truman,” he called them, which became the new raw materials for his rebuilt manufacturing process. Finally, an earthquake destroyed the factory.

After the war, an extreme gasoline shortage forced people to walk or use bicycles. Honda built a tiny engine and attached it to his bicycle. His neighbors wanted one, and although he tried, materials could not be found and he was unable to supply the demand.

Was he ready to give up now? No! Soichiro Honda wrote to 18,000 bicycles shop owners and, in an inspiring letter, asked them to help him revitalize Japan. 5,000 responded and advanced him what little money they could to build his tiny bicycle engines. Unfortunately, the first models were too bulky to work well, so he continued to develop and adapt, until finally, the small engine ‘The Super Cub’ became a reality and was a success. With success in Japan, Honda began exporting his bicycle engines to Europe and America.

His plans were stopped by the whole world going to war and his factory was destroyed by a blooming earthquake. But he didn’t give up. I’m not sure I’m there yet. I think if an earthquake destroyed one of my projects I’d probably call that one a day, but I think this is an incredible lesson to us all.

The thing I’ve learnt today is to be successful you need to carry on even when you fail. Even if you fail ten times and then succeed, you’ve succeeded. Succeeding isn’t not failing, it’s working through all the failures to get to the success at the end.

It’s like that old joke:

“Why do I always find my keys in the last place I look?”

“Because you give up looking when you find them.”

The only way to not fail is to keep trying.

The other thing, of course, is to review your failures. They may be painful, but failure is the only thing you can learn from.

Consequently, I’ve reviewed Jeff’s list of “how to backup” again and looked at my process:

  • Don’t rely on your host or anyone else to back up your important data. Do it yourself. If you aren’t personally responsible for your own backups, they are effectively not happening.
    [I assumed queued posts were backed up. They weren’t]
  • If something really bad happens to your data, how would you recover? What’s the process? What are the hard parts of recovery? I think in the back of my mind I had false confidence about Coding Horror recovery scenarios because I kept thinking of it as mostly text. Of course, the text turned out to be the easiest part. The images, which I had thought of as a “nice to have”, were more essential than I realized and far more difficult to recover. Some argue that we shouldn’t be talking about “backups”, but recovery.
  • It’s worth revisiting your recovery process periodically to make sure it’s still alive, kicking, and fully functional. 

And I’ve got a plan to stop this happening again.

Tag Cloud