Gyanesh's DITA blog

Raspberry Pi test drive

2013-07-29T03:49:00.002-07:00

Raspberry Pi - The Rs 2000 computer

I was quite excited to hear about this credit-card sized computer that costs just $35 - Rs 2000 Approx.

Immediate thoughts:

On hearing about this tiny, affordable device, I thought:

Growing up (Circa 1995), I wanted a computer and it was quite difficult to spare Rs 40K for my parents. It delayed my introduction to computers by a couple of years. I finally learned computing on a Rs 1.3 lakh Mac in a computer center.
I marveled at the thought that such a thing can revolutionize diffusion of computing into nooks and corners of India. What a great advance that will be. What great things that could lead to.
But right now, this tiny thing could plug into my LCD TV and make it a smart TV. I could surf net on it and stream YouTube videos to it.

Trial

The friend I borrowed it from had already set it up - so for me it was as good as plug and play. I started the computer, added USB mouse and keyboard, and connected it to my TV using an HDMI.

Findings

Start up: As soon as I started it, the Linux home was there on the TV (after a few seconds of command line processing).
WiFi: Setting up the WiFi network on the computer also was easy.
Speed: quite primitive. I found the computer to be slower than a 286. Surfing was a drag. You can't even upgrade the RAM from 512 MB. This is a one-application computer.
Videos: I tried playing YouTube video on the browser and there was no Flash (that means no YouTube). Internet says this can be done with a bit of setting up. But I was too unexcited by this point to try it. Maybe I will try this later.

Conclusion

Raspberry pi is for you if you are a nerd who needs a computer just for writing code and compiling it (I hear the nerds are doing home automation and robotics with pi). You can surf light websites but even gmail makes the Pi cry.
The price may seem very exciting, but it is quite apt considering the performance.
If it is a Smart TV gadget that you seek, try Google Chromecast.
Definitely not a rich-content consumption device.

Are Indian Technical Writers really just churning out SHIT?

2013-02-28T07:16:00.001-08:00

This article originally was an online reply to someone declaring Indian Technical Writing as incompetent and advocating that the work should be taken back to the American writers.
---------------------------------------------------------------------------------------------------------

While there are a lot of TW teams in India who are producing quality work and are delivering far beyond their mandate of “writing grammatically correct content,” there are teams in India who have struggled to meet the basic quality standards. Shipping the work back to the American Writers is a knee-jerk reaction (I know a couple of companies where this has been MADE TO HAPPEN successfully.)

I have myself seen some pretty ordinary people in tech-writing in India. I joke with my friends sometimes that people who get shortlisted for tech-writing jobs are the ones devoid of any language skills, clarity of expression, and technical aptitude. While this joke is the reality of 30-40% tech-writing teams in India, it does not mean you cannot find talent in India. The problem lies elsewhere. What ails the badly performing Indian Tech-Writing teams?

I have seen that the following are the main problems:

1) Me no want pay …me no want train

Best Indian Tech-Writers (just like their American counterparts) are not considered for employement by most companies because they are expensive. New people with good potential are never considered cause they will need to be trained. So most companies end up recruiting the wrong people in the right experience range of 2-6 years.

2) Training? What training?

It is very Indian to speak the same thing multiple times for emphasis and respect. It is also Indian to use minimal (sometimes incomplete) and informal communication. And then Indians are influenced by the British – a nation Americans hate for linguistic reasons. We Indians are also taught British English in the school for 12-15 years.

Again, it is a knee jerk reaction to assume that Indians will struggle with these problems lifelong. NIIT, which use to be big in Instructional Designing a decade ago, had designed training programs that transformed hundreds of Indian new writers into thoroughbred American-style writers. The small NIIT language program was a mandatory one for everyone in the company. (Check with a former NIITian about this program or Google for it.)
If you have no patience for training newbies, be more thorough in your recruitment and be willing to pay a little.

3) How fast can you build a tech-writing team?

The speed with which you can build your tech-writing team is directly proportional to how soon you get frustrated and get ready to undo the whole thing (sending work back to the US). We all know how off-shoring is done - Indispensable tech-writers, domain experts, architects, and developers in the US are let go and new teams are built in quick time and are expected to hit the ground running.
I know of a 100 member strong tech-writing team in Bangalore that was recruited in a matter of months (I know this because while the team was being built 37 different headhunters had contacted me for this team in 3-4 months - and I saw many of my teamies also get countless calls from people hiring for this team).
If you go slow, be selective, and think long term, you will increase your chances of success. Too many teams are recruited too fast to succeed.

4) Let them make mistakes and learn

This one is hard. I remember when I was teaching someone driving. Being an experienced driver, I found it very hard to let go of the steering and controls to a newbie. It was dangerous.
Yet I did not assume that my trainee driver will keep driving like a newbie forever. Unfortunately, too many editors and tech-writing managers fail to understand this.

5) Damager may not be an anagram for Manager.. but sometimes, it’s a synonym

In my 12 years as a Technical Writer, I haven’t seen more than a couple of tech-comm managers who knew their …errr… stuff. For the fear of backlash, I will not elaborate on this point further (or maybe I will write a full blog post on the Tech-Writing Damagers). For now, I will mention a two-line Indian folklore that explains the survival of a lot of TW managers:
“There was a demon who use to kill and eat the King on new moon, so the king’s men use to catch a villager and make him the king for THAT one night.”

DITA Vs AuthorIt

2009-12-20T09:18:00.001-08:00

You may think this is not a fair comparison. One is an open-source, XML-based architecture the other is a proprietary Authoring platform. Perhaps this is why even people at AuthorIt do not compare the two. The both, however, promise to achieve similar things and solve identical tech-writing problems. And some knowledgeable AuthorIt disciples keep asking... "why dabble into open source when you have something out-of-the-box to do everything??" So, what similar benefits do DITA and AuthorIt promise?

-> Config management
-> Localization management
-> Strong typing - no deviation from the standards
-> Multi-channel publishing
-> Integration with business applications
-> Dynamic content delivery
-> Conditional processing
-> Profiling and Re-use
-> Cost savings in the long run
-> Blah, blah, blah

So, if you are looking to achieve the above, the following comparison may help you as a starting point for comparing AuthorIt and DITA (click on the image to enlarge it):