Mac@Work : The Ultimate Business Machine

The
Ultimate
Business Machine

Technology, business
and innovation.

And, not least, about
the Mac.

Weblog • Archive • Cutedge

by: Bernard Teo

Mon 02 Jun 2003

Clogged Google

Category : Commentary/cloggedgoogle.txt

On a hunch, I used the Google field in Safari to search for "bernard teo". Try it. You'll see that I'm top of the heap. From out of nowhere, in three months (I know because I've tried this before, using Sherlock). There's been an outcry about bloggers clogging up Google and the other search engines. Now you know why.

Posted at 2:17PM UTC | permalink

"I Remember May"

Category : Commentary/may.txt

That's the name of the novel (website down while being moved to China) by my friend Kein Kwok, the guy doing web and 3D design at Chengdu.

"Bittersweet and unexpectedly funny", says the blurb at the back of the book, and I can attest to that. I like the humour and love the ending. It's about first love and memories of old Singapore. It contains three or four stories that intertwine and unfold at a very nice pace, with flashbacks tying the stories together, lending the novel a sepia-tinged perspective.

The dialogue's unpretentious. It's not like he's trying to be an artist; he's just trying to tell a good story. But I believe it must have required creativity, precision, and good sense of timing to try to weave together a narrative the way he did. I couldn't do this in a million years.

Actually I don't why I'm still talking to this guy. He's a PC geek who totally dislikes the Mac. Snake oil salesmen, he calls the guys at the Mac shops (hah hah). Somehow I'm not offended.

Posted at 2:16PM UTC | permalink

Sun 01 Jun 2003

Hollywood

Category : Commentary/hollywood.txt

I was just updating a friend about what I'm doing (This guy's interesting. He's been up at Chengdu since April, last year, building a web design and 3D graphics business. He's also interesting because he's written a book - a novel, actually, and quite a good one, too. I think he's written something that should be made into a film. But that'll be another topic).

But for now, I was just explaining to him why I think maybe the current model for doing IT projects doesn't work. I'm thinking that the process used by Hollywood (seriously!) could be a better model - the client hires a reputable producer, who will determine the requirements, hire the talents - coder, designer, tester - and they come together for a few months, and deliver the system, and the client gets the source code (because they're all going to use Open Source tools). When the client wants to build something more, they can form another project (could be a wholly different team next time) and it gets done. And the whole thing works by reputation. Mess up, and it'll be hard to get invited to join another project. (It works the other way, too. An inept project lead will soon lose an ability to attract talents.)

For this to work, you've got to have an eco-system, and a grapevine, and lots of contacts. That's why tools like phpbb2 could become the great enabler. It faciltates discussion, contacts, collaboration, and provides some privacy in terms of its ability to set up different levels of access.

I let a couple of projects pass by last year because I grew too tired of the old way. If they ever come round again, I'll try this other route.

I tried to visualise how this would work a few years ago when I was reading William Goldman's "Adventures in the Screen Trade". Certainly, I believe that writing software is not a factory job. There's a lot of creativity and inspiration needed that you can't legislate for. Talented programmers are as temperamental as any artist. And it'll get more combustible as you add graphics designers and writers to the mix, especially for web-based work.

Just this morning I was reading this in "The Creative Economy": "As a process for turning ideas into business, and as sustainable economics, Hollywood can teach some useful lessons... In recent years, the ordinary economy has begun to see the benefits of Hollywood's ways of working... "

Posted at 2:53AM UTC | permalink

Sat 31 May 2003

Search this Weblog

Category : Technology/searchphrase.txt

Now, I'm really glad I took the trouble to understand the PHP code running this weblog. Adding just about three lines of code, I'm now able to let people search the weblog archives for articles containing the phrase they have entered.

Google has been leading people to this weblog when they search for things like "mail server os x". But when they get to here, they see only the latest day's edition. I've never seen anybody having the time to go search the archives manually for the relevant articles.

So, in yet another effort to make this particular corner of the blogosphere a friendly place, I've added the Search Weblog button on the left. (Try searching for "alfred hitchcock"). It's just a simple function - only able to match the complete phrase you've entered, nothing more (for now).

If you're interested in the source code, you can download it from the Weblog Tutorial page on the right.

Posted at 3:57PM UTC | permalink

Fri 30 May 2003

The phpbb2 Bulletin Board System

Category : Commentary/phpbb2.txt

After a day with phpbb2, I think it's got fantastic potential as a content management tool. It boggles the mind (to use a hackneyed phrase) to think that these (including YabbSE) are freely downloadable tools, easily set up in minutes, and have (in the case of phpbb2) great documentation, too.

I'm going to use phpbb2 over YabbSE because it seems slicker and better organised (especially in the way the code is packaged because I'd like to study the code). Behind the software, I think, is a supremely gifted designer (or group of designers). Do you realise that this is an Open Source Project and nobody is paid anything to do it?

Any business can benefit from these tools. You can run a help desk for the users of your product. Your users can help each other. You can set up private discussion groups for internal staff, contractors, management, etc... You can capture useful knowledge, facilitate communication, arbitrate disputes. You can move the info around - from the private to the pubic domain and back. And, because the code is available, you can extend it to work with other parts of your business system.

But the question I'm pondering is : how come this method of development works? The developers, designers and testers come from all over the world. Many likely have never met face to face. They don't get paid (at least not directly from the project). They're fast. The whole thing just works. I love the design because they've thought of most things and they do the 80% most common tasks very well. And you don't really need to read the manual.

Is it the Open Source nature of things? These guys may be fast because they can grab code from all over the place to re-use in the system? Is it because they know how to make the good trade-offs? Is it because they live on the cutting edge, not just of technology, but also of a new way of living which requires an ability to think, negotiate, arbitrate and communicate, within a framework of self-restraint and understanding for the rights of the commons?

It's a different world from the plodding nature of most in-house IT departments. I just know we've got to learn something from this.

Posted at 10:33AM UTC | permalink

Creating a Community

Category : Commentary/community.txt

I wrote this weblog because I really had a hard time finding other people interested in the things I had written about here - technology and innovation, building a business, systems thinking, art and design, and of course the Mac. I've always felt the Mac was central to making this particular combination work. And part of the purpose of writing this weblog was to describe how life can get a bit more interesting when you start making these connections.

I've attended Mac Users' Group meetings (in the days of Lynette Herbert), monitored the discussions at Mean, and also the Mac Users' Group forums - all to no avail. They're usually about the latest gadgets, configuring stuff, etc. And I'm more like the pianist who doesn't want to spend any more time than is necessary peeking inside the piano.

So I wrote this weblog to see if I can find other people of a like mind. Sort of like, build it and hope people will come. If you've come back regularly to read this weblog, it may be because you're looking for the same thing, Windows users included.

So why not connect? You never know where that might lead. Write in, Join the dialogue. Ask questions about MySQL, running an IT project, making Mac and Windows work together, books to read, etc... And maybe, just maybe, end up helping to create a unique community.

Posted at 9:31AM UTC | permalink

Thu 29 May 2003

The Ever Resilient Me@ner

Category : Commentary/resilient.txt

Found TUBMac linked to from this page at MacSingapore. Scroll down to the Singapore section. I suppose "the ever resilient ME@NER" means me. Thanks, guys, for the mention.

Posted at 2:03PM UTC | permalink

Kristian@soundingblue

Category : Commentary/soundingblue.txt

Kristian@soundingblue.com has posted some very nice pictures. Great talent. Wish I could do shots like these. Go look.

Posted at 7:20AM UTC | permalink

The Creative Economy

Category : Commentary/creativeeconomy.txt

I'm half-way through "The Creative Economy - How People Make Money from Ideas" by John Howkins. It's a wonderful book, so far, and so full of gems. It's been a long time since I've had so much pleasure from a "serious" book.

There's this quote fom Terence Conran, the designer: "Creatvity is hard to define. It's mostly straightforward but there's also something magical, almost spiritual, about the process... You need to know the history of things and to be able to see a gap in the market."

"You need to know the history of things". Quite akin to what Steve Jobs said about needing to have a wide range of experience so that you will have enough dots to connect.

Which brings me to something written about in yesterday's STREATS - "Former oil man refines hair salon idea" - about someone hoping to copy the success of the QB (for Quick Beauty) chain of hair shop, by bringing a Balinese element into the mix. A phrase in the report stands out: "That he had no experience in the beauty business did not daunt him".

I believe that the basic idea of a quick, no-frills hair cut is incompatible with the languid, sensory experience you would associate with a Balinese spa resort. To create that ambience, you would need lots of wood, which takes up space - a reported 600 sq feet when compared with the 200 sq feet needed by the spartan Japanese-style QB Shops. It's that gestalt thing again. There's an expression the architects like to use: "the design must have integrity". The design, as a whole, must resonate - through the expression of each part keeping faith with the objectives of the whole.

This guy (or more likely, his investors) could lose his shirt. I'm not saying he won't succeed; it's great that people are willing to try new businesses. But I believe that he'll be making changes to his trajectory, if he were to eventually succeed.

Posted at 6:19AM UTC | permalink

A Digression - About the Epson C1900 Aculaser

Category : Technology/digressEpson.txt

Google is hitting this weblog in search of answers to "colour laser printing" and "Epson C1900 Colour Laser" - probably because these were mentioned in previous posts. My log file shows that they're coming from Mac users.

In case they're looking for the answer to : "how do you get the Epson C1900 Colour Laser Printer to support Postscript printing from OS X machines", the answer is :

The Epson sales reps and local tech support people may say that the Epson Aculaser series does not yet support OS X for Postscript printing. But they ought to know better. If you buy the Epson C1900 with the Postscript option, and if you're a Mac user, you'll get an OS 9-based CD. Open up this CD from an OS 9-based Mac, and look for the PPD file that is associated with this printer. It's called "EPSON AL-C1900 PS3". Copy this out and put it in the OS X machine. I place mine simply under "/Library".

Then, when you're asked to give a PPD file when you're setting up the printer in OS X's Print Centre utility, navigate into "/Library" and select the PPD file you placed there. And that's it. You get great Postscript printing from the Aculaser.

Actually, because of OS X's Quartz technology, you can get close to 90% of the quality of a Postscript printout, even without using the Postscript option. But, with the Postscript option, fonts look great even at very small point sizes, and they look more refined. Hope this helps. (And this method should work with all the other printers in the Aculaser series).

Posted at 5:30AM UTC | permalink

Wed 28 May 2003

The hardest thing in life

Category : Commentary/hard.txt

The hardest thing in life is to get people to think. If you're a software developer or vendor, that's the one that will wear you down.

For example, I've described in the previous post about the user who wants the sun to rise from the east, and another who wants the sun to rise from the west, and they both refuse to budge. This happens all the time.

If you're an outside contractor, there's an added twist - you'll find both guys supporting each other's position with great enthusiasm. It's that old Asian feeling about "family and sticking together" kicking in - only now you're the outsider, so good luck with all that shit.

We can laugh about it when we get some distance from the memories. But believe me, it is no laughing matter because a lot of sofware projects fail. Not for technical reasons. But for a failure in project management.

I'll try to summarise the problems with software projects. One is, we're dealing with technology. And that makes people feel that they ought to be throwing around buzzwords so that they can sound like they're in the know. But I'm trying to explain that we can deal with the technology from a purely descriptive level and still get a lot of work done.

The second point leads from the first. Because people lack the confidence or even the awareness that you can visualise the system purely in terms of the data flows, they haven't build a mental framework they can use to think three or four steps into a problem. That's why it's so hard to make them see where their requirements collide with that of another party.

The problem is compounded by that peculiar Asian need to save face and look after your own family (whatever you define it to be).

So there's a gridlock you can only break with a lot of tact, doggedness, and (I daresay) idealism. You literally have to force people to face the trade-offs. There's a lot of incentive to just cop out, and go through the motions of building the system. After all, what do management know about technology? But, like they say, be sure your sins will find you out.

I don't want to make a mountain out of a molehill (to quote a phrase). But you can't build The Ultimate Business Machine if you cannot build the system to run it on. It's a problem that is hard to solve.

Posted at 7:36AM UTC | permalink

Tue 27 May 2003

Making the Trade-Off

Category : Commentary/tradeoff.txt

If you should ever find yourself managing IT project, there are two things (I hope to persuade you) that you should have.

One is the ability to see the system in terms of pipes, reservoirs, and taps. Let me explain.

You should start off by imagining how each part of your organisation could work better if it has the kind of information you hope the system will produce for you. Then you imagine going around and placing the taps so that people could get the right information, on tap, when they're needed.

Then you work backwards to see how you can collect that information. That's when you design the piping system to suck the information from wherever they are being produced. And bring them towards the reservoir, which is the database system you will use to collate and store that data. From the reservoir, other pipes bring the information back to the taps. So there's a circulation.

It's important to visualise that circulation. For example, in an insurance application, the premium you charge for an insurance policy has to cover the costs of all the claims incurred by policies of a similar type. So you will want to set up the system such that information collected by the claims department is sent back towards the underwriting department so that the pricing of new policies can be automatically adjusted. That should make sense, right? But most systems don't have that feedback loop.

Two is the ability to make trade-offs. E.g., to get useful statistics, you've got to have a structure, so you can compare like with like, apples with apples. But the users may rebel against a structure and want to enter data free-form, simply because they can then record anything under the sun.

This is like having a user who wants the sun to rise from the east, and another who wants the sun to rise from the west, and you say OK to both. Even God can't do that. (Or can He?)

I've observed that this is somehow hard to get people to do. But you've got to think three or four steps into a problem before you can see where they collide with another "must-have" requirement. Then you've got to make the trade-off. There's no free lunch.

So you see, to do IT well, you don't need to be buzz-word compliant (three-tier, four-tier, Java, for heaven's sake). You've just got to be capable of logical thought, be intellectually honest, and be a decent human being. Welcome to the human race.

Posted at 2:48PM UTC | permalink