Learning, Unlearning and Relearning

Most people will be starting work tomorrow. The past week has been good as the traffic in KL was still rather sparse; it was great being able to zip from place to place easily.

I've made a resolve to be more independent when it comes to work. I used to have to depend on the services of a graphics designer to do some of the design that comes part and parcel with app and web development. Engineers are usually hopeless when it comes to even the simplest graphics design. They are almost aesthetically blind, having no sense at all of the basic elements of balance, contrast and harmony.

I've been spending the past week doing some of the graphics on my own. All graphics designers have Adobe Photoshop and Adobe Illustrator as their basic tools. Many use pirated copies. I don't own or pay subscription to any of these tools. And I was reluctant to invest time to build up proficiency in using proprietary tools, even though they are considered industry standards.

Frustrated by the entire industry's dependence on these tools and how we are forced to pay for them, I made a resolve to find open source alternatives. Here, I'm glad to say that I've tested and found good open source substitutes: GIMP for bitmap images and Inkscape for vector graphics. Using them, I'm already able to import all my old Adobe Illustrator assets and make modifications to them. I am finally free, at least for what I'm doing, from the need for the services of a graphics designer and the tyranny of Adobe tools. And it feels very liberating indeed.

I've also made another resolve (I actually have new year resolutions after all!), to be free from the Windows operating system. Unlike many of my friends in the industry, I'm also not a Mac die hard. On the server side, I've been using various distribution of Linux for years and have no issues with it. My laptop is set up to dual-boot with Windows and Ubuntu. And lately, I've been finding myself using Ubuntu exclusive for all my needs and I'm doing just fine. GIMP and Inkscape work beautifully on Ubuntu. Being completely free from Microsoft, Apple and Adobe definitely gives me a great sense of satisfaction.

I rarely write about IT matters on my blog, even though that's been my profession all these years. Today's entry must seem like a rare exception. But I'm also trying to inject fresh subjects into this blog of mine and there are many philosophical insights that one can gain from IT too. These will be interesting blog topics for the future.

I guess 16 years is long enough time for me to get over any disillusionment I had with the industry. I realized that it is the only industry where the skill to learn is perhaps the most valuable skill of all. The pace of change in this technology is staggering and the only survival skill one needs is the skill to re-skill oneself. As the eminent futurist Alvin Toffler once said: “The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn.”

And that's the only thing that I've been doing consistently all my life.

Blogging with Scribefire

The reason why I'm blogging today is simply because I wanted to try out this blog client - Scribefire, which is a Firefox plugin. For many years I've been using Bloggar as my client--especially during my days in Indonesia. At that time, I blogged daily from a cybercafe. I remember having to download and install the client everyday onto the PC that I happened to be using, because the owner cleaned up all unauthorized applications regularly.

Bloggar was good enough for my purpose, until these last couple of years when it was not regularly maintained by the creator, and it didn't keep up with the changes in the Blogger.com API.

I know many bloggers blog directly from Microsoft Word, which is capable of posting to most of the popular blog sites, but I prefer a lighter client. I tried LiveWriter for a while, but didn't find it fuss-free enough for my liking. And I must confess, I'm no big fan of Microsoft applications, nor am I an Apple freak. I like my computing platform to be light, unintrusive and doesn't try to call attention to itself. It should just fade into the background.

I still have Windows on my notebook, but most of the time, I boot from my Ubuntu partition. I find it easier to do my development work on a Unix platform. SSH terminals are my best friends because I need to log on to the server all the time. And Ubuntu certainly feels faster and lighter than Windows.

So this is my first entry using the Scribefire plugin as my Blogger client. So far so good. I've been able to insert links quite easily. And if this gets posted successfully, I'm going to start using it regularly!

The Art and Science of Proposal Writing

I spend most of weekends working from a nearby Starbucks cafe. It is here that I grapple with my multitude of programming problems and hack out my technical proposals and presentation slides.

One thing I've found out being an IT professional all these years: writing code is a lot easier than writing proposals. Coding can even be fun sometimes but technical proposal-writing is always a chore. In programming, most of the time, you know what needs to be done. The challenge is executing it in the simplest, cleanest and most elegant way. Writing code that works is a no-brainer, it's writing good code that's the real challenge.

A proposal is essentially a sales pitch. You are basically putting forth your value proposition--bringing the potential customer's attention to your strong points(and taking the opportunity to indirectly highlight your competitor's weakness), reemphasizing your expertise and commitment and justifying your pricing.

In any IT project, pricing is important. But what's more important is being able to give the customer the confidence that you or your product can do the job. The decision-maker's job could be at stake here. Put yourself in his shoes: can you trust this vendor to help you look good in front of your bosses?

Confidence is an intangible thing which you subtly project through your approach and professionalism. A professionally-written proposal goes a long way towards achieving this goal.

It's easy to hire programmers but finding a good proposal writer in the IT industry is like looking for a needle in the haystack. Writing is a lot of hardwork, especially technical writing. It requires someone who appreciates technology and enjoy stringing words together to illuminate difficult concepts.

Besides being able to understand technology and being able to sell them using words, there's a third skill that's required of a good proposal writer: the ability to illustrate technical architecture and concepts using diagrams. Most engineering diagrams that I see are very badly drawn. Engineers are usually obsessed with getting the interconnections between different components right but they don't have a sense of proportion, balance, contrast and colour coordination.

You see, a good diagram is also like a good proposal. It organizes things systematically for the eyes and the mind of the reader. What does the reader see at first glance? It must work like a good advertisement billboard: the main message must be immediately evident. Example: it's a star topology, or there are 3 major components in the overall architecture or client components are grouped on the left-hand-side, server components on the right. A good technical illustrator must be aware of all these things.

My personal philosophy on good proposal writing is this: it must read like a comic book. The first thing a person does when he receives a proposal is to flip through the pages. In the process of flipping, it's usually the diagrams that catch the eye. If you have a sufficient number of well-captioned diagrams scattered all across the proposal, they alone should be able to convey the gist of the story.

Does that mean that a good IT proposal writer must be a salesman, an engineer, an artist and a writer all in one? Yes and no. Yes, because all these different elements must be present to produce a good proposal. No, because these skills need not necessarily come from a single individual. If a team of people with different skillsets can combine them together effectively, then they can come up with a good proposal.

And one more thing: if you have a team of people working on a proposal, you also need a good proposal manager. He is the person who carries that big picture in his mind, understands what needs to be achieved, sets timelines, ensures that everyone delivers their portion on schedule and integrates them together into a coherent whole. This is a very challenging task, especially when a proposal involves components from multiple vendors and partners. In other words, the proposal manager must be someone with good project management skills.

Does such an ideal proposal-writing team exist in most IT organizations? Very rarely. Usually the task of coming up with the proposal is dumped onto the pre-sales engineer. He's expected to be the salesman, the engineer, the writer, the artist and the project manager. Good luck to him!