• About

    Swaroop C H is 27 years of age. He graduated in B.E. (Computer Science) from PESIT, Bangalore, India. He has previously worked at Yahoo! and Adobe.


    Email: swaroop (at) swaroopch.com

    Read more about him

  • Subscribe

    If you want to know when new stories appear on this website, you can subscribe to the RSS feed or have them emailed to you:

  • via RSS

  • via Email

    Enter your email address:

  • Want me to write about something?

  • I'm a Wannabe Hacker

    The Glider: A Universal Hacker Emblem

The point of being Done

February 1st, 2010

Listening to Seth Godin say “What you do for a living is not be creative, what you do is ship” reminded me of the The Cult of Done manifesto:

The Cult of Done Manifesto

If you find the image inconvenient to read, here’s the text:

  1. There are three states of being. Not knowing, action and completion.
  2. Accept that everything is a draft. It helps to get it done.
  3. There is no editing stage.
  4. Pretending you know what you’re doing is almost the same as knowing what you are doing, so just accept that you know what you’re doing even if you don’t and do it.
  5. Banish procrastination. If you wait more than a week to get an idea done, abandon it.
  6. The point of being done is not to finish but to get other things done.
  7. Once you’re done you can throw it away.
  8. Laugh at perfection. It’s boring and keeps you from being done.
  9. People without dirty hands are wrong. Doing something makes you right.
  10. Failure counts as done. So do mistakes.
  11. Destruction is a variant of done.
  12. If you have an idea and publish it on the internet, that counts as a ghost of done.
  13. Done is the engine of more.

My favorite is Point 6.

Joining InfiBeam

January 15th, 2010

Thanking the community

First and foremost, thanks to all who encouraged me, and offered support and help when I wrote about leaving my own company. Many people, without any personal benefit in mind, connected me to very interesting opportunities. And this is exactly how I got my next gig.[1]

What was specifically amazing to me was that folks were connecting me to opportunities that I would not have heard of otherwise, and enthusiastically vouching for me. Now that was really humbling. Within two weeks of my blog post, I had a job! And I didn’t even have to look for it, so thank you guys. As Seth Godin put it, who needs a resume indeed!

InfiBeam

So where am I joining? InfiBeam – which I can best describe as “Amazon of India.”[2]

infibeam 001

So why am I excited about InfiBeam?

In my previous startup, I experienced the phase of starting from scratch till creating a product. Unfortunately, I did not get to see the second part, the business side of things, including the hard part of selling, the act of knowing the customer, the logistics and operations, etc. I was still yearning for that.

At the same time, getting to see this second phase a few years later would not have made sense because I would’ve lost the enthusiasm and momentum that I have at this point in time. So, in that sense, I’m really excited about InfiBeam because I’ll get to be part of this second phase.

Second, I was specifically looking for companies in “core” areas, in the sense, someone who makes consumer products and services in India for India, and specifically, either ecommerce or mobile. And, voila, the universe conspired.

Third, I was being cautious and really looking to understand the people in the company and not only what the company makes. After all, it’s only the people aspect which makes or breaks your experience and enthusiasm. And I spent quite a bit of time interacting with the people I would potentially work with, and I came out of the discussions very happy.

Fourth, what I especially liked most about the company was their customer focus as well as the focus of building the right culture inside the company. It’s very hard for startups to focus on these soft aspects, because it easily gets sidelined compared to the hectic everyday.

InfiBeam Customer Service InfiBeam Core Values (list)

There were quite a few opportunities that I explored, but I intuitively felt that InfiBeam was the place to be. And I went ahead with that gut instinct.

Both Business and Tech

And, as an example of a great fit for me, my job description says that I have to take up any product or strategy and deliver it end-to-end from the business model to the technical implementation.

I had thoughts of shifting back to pure coding at first, but then decided a business focus is indeed a good thing, and something I wish I had taken seriously right at the start of my career (better late than never!). For example, quoting from a recent Deccan Herald article: > It cites Nasscom study which states that India faces IT talent shortfall of between 8,00,000 and 1.2 million workers by 2012. It observes that, though many producers continue to work with universities, government and other firms to improve the quality of technology education, and Asian countries continue to produce large numbers of IT employees, they, however, lag in comparison with North America and Europe in providing well-rounded technology education. Among Asian economies, the concern is that education systems puts too much focus on pure IT skills and not enough on IT in the business context. Likewise, top schools in the US and Europe, which do better in this area, face long-term challenges in cultivating science and technical engineering skills of its younger students. Thus, globally, the study posits that investment in skills development remains long-term imperative.

If it feels scary…

I am positive about this gig because I will be forced to become good at what I do because of the quality of people I work with, and knowing that you’re in a good environment when you consider yourself the dumbest guy in the room.

In such situations, I keep quoting Jeff Atwood:

> If it feels scary, it’s the right choice.

Wish me luck!

[1] Specifically, a shout of thanks to Nimish Adani of Workosaur.

[2] Yes, this was a way of skipping the topic that, yes, InfiBeam’s current web design looks similar to that of Amazon.com design. Yes, I don’t like it too. It is a distraction which prevents potential users to proceed to the next step of appreciating the amazing services provided by InfiBeam.

Update on Jan 31, 2010: InfiBeam has launched the first Indian ebook store and the first Indian ebook reader.

Fun can change behavior

December 26th, 2009

Once in a while I come across something really inspiring, and this time it was The fun theory – a “thought that something as simple as fun is the easiest way to change people’s behavior for the better.”

Getting people to use the staircase than the escalator


Getting people to throw into the garbage bin


Getting people to iron their clothes

Road Roller Iron

“Ironing clothes can be a boring task and getting the creases removed from your clothes perfectly is next to impossible. Now all you need to do is place your shirt on a customized iron board with sensors. You need to define the task. What is to be ironed? Shirt, trouser etc. The board defines your play area with lights depending on your selection. Creases are highlighted. Place the mini road roller iron on the shirt, sit back and let the fun begin. With a remote control you need to guide the road roller around the highlighted creases. If you move out of your play area, you lose points. If you get all the creases sorted in quick time you gain points.”


Getting children to clean their rooms


So what?

I hope to keep this inspiration in mind whenever I’m building products for others to use.

P.S. Go vote for the best entries before January 15, 2010!

Musings on 2009

December 22nd, 2009

- Work -

Resolutions

Life is what happens to you when you’re making other plans. I got sidetracked by struggling to make a business. But don’t regret it for even a moment. Learned a lot about the real world. Changed from being a meek guy who liked to hide behind email to someone who has now learned to “work the room.”

Business

Reinforced, the hard way, that “you’re not here to write code; you’re here to ship products.” — JWZ

Job

Ironically, after a startup experience, I think I will be a far more cooperative person in a corporate environment, because now I realize the problems and hardships faced in each role in a company.

Psychology

Realizing that it all boils down to psychology. Understand the other person’s psychology and only then you can navigate through life.

Rationality

My new law: “Never ever assume that people have made their decisions rationally.”. People take decisions for all sorts of reasons, just don’t assume that the reason was rationale.

Confidence

Realizing that self-confidence comes from within. Everybody has their own talents. So what if I can’t code like geniuses? When I work with intensity, I can get the job done. Good enough, I think.

- Life -

Decisions

You don’t make decisions, decisions make you.

What Matters

What matters to me is force and family.

Friends

Good times don't last. Bad times don't last.

(Drawing by Jessica Hagy)

Realizing how often you lose friends that you care about. Good friendships last ~2 years only.

Real Troubles

Don’t worry about the future.
Or worry, but know that worrying is as effective
as trying to solve an algebra equation by chewing bubble gum.
The real troubles in your life
are apt to be things that never crossed your worried mind,
the kind that blindside you at 4 pm on some idle Tuesday.

Baz Luhrmann

Pursuit

As humans, we will always be in the pursuit of something.

At the end of the day, all we want is to be missed and to know that we have made a difference.

The 5-year limit to being a coder in India?

December 9th, 2009

Let me start with a story I had heard about long ago when I was at Adobe.

There was this guy who had come in for interviews for a technical role. He passed all the tech interviews with flying colors, the team liked his personality and felt he would fit in well, and the manager was all smiles. In the last HR-style round with the group head, he was informed that the team works on products that are completely owned by the Bangalore-based group and that there won’t be any travel to USA. The guy was taken aback. He told the group head “Sir, please let me go to USA for just one day. If I have a USA stamp in my passport, I will get one crore dowry.”

Needless to say, the guy was not offered a job.

I’m sure you can draw your own lessons and observations from this incident, because it will come into context below, about a discussion we’ve been having on Twitter. It all started with @debabrata who read my previous blog post on the magic of foss.in and asked:

why this ‘5 years limit’ applies to Indian software pro ? In other countries people are happy being programmer after 20 years .

I asked the tweeps for their opinions, and it got very interesting.

@cruisemaniac said: society defined age to get married and settle down = ~27 = 22+5 failing which u’re an outcast! and: also, post that age, ur risk apetite goes down due to family and other commitments…

to which:

@HJ91 said: True. Very true. Outcast is the right word, and its sad. Outcast. Insulting, hurting and pathetic.

Wow, this feeling runs deep.

so I asked:

You mean risk appetite or time commitment? … how does risk appetite relate to interest in coding?

And the replies came pouring in:

@mixdev: One of the reasons why brilliant people end up being (just) tell-me-whatto-do-n-leave-me-alone software engineers

@cruisemaniac: I’d say both… U cant risk a new tech and venture 4 fear of financial security… U want tat cozy safe zone and pay packet.

@cruisemaniac: time is a big costly commodity 4 us… we indians cant afford to spend it at our will with spouses and children at home…

@mallipeddi: It’s very hard to keep getting bigger paychecks yr after yr if you’re a 30 yr old coder. You’re expected to become a mgr/MBA

@abhinav: I believe the reason is our society. We tie success to degrees, and later, more ppl you manage more successful you are.

@abhinav: Where in western societies your idea fails, here it is you who have failed! Our society doesnt appreciate risk takers

@abhinav: Yes, more money, higher status, easy life. And most importantly, more dowry!

@mixdev: Because our goals are set by the society & achieving them also in their control. You get bored faster.

@debabrata: I guess to the great extent our society dictates us what we want to be unlike the west

I found it surprising that the situation why people cannot remain coders in India is almost the same as why people want to become entrepreneurs! It’s like this: The passion for coding will remain only when you’re doing cool and interesting stuff. But big companies (at least in India) want only stability which implies boring tedious jobs with standard languages and libraries. There is no room for experimentation. So the coder will have to move to a smaller company or a startup if he/she wants to continue to like coding (I’m ignoring the case of research laboratories for obvious reasons of numbers).

But moving to a smaller company or startup is, by definition, not encouraged. As @abhinav mentioned, there is societal pressure for more money, higher status, fancier cars and bigger houses. There is nothing wrong with wanting this, but don’t force it on other people! Alas, it is hard to reason regarding this. I remember having a long argument with an uncle of mine, he was, hmm, “strongly” suggesting that I buy a car and I reasoned out why it makes no sense (after all, most peers of mine use the car only for weekend drives, not for everyday commute) but it fell on deaf ears.

So I’m conflicted here: Are there not enough people who are actually interested in coding, or is it that the interested people are being peer-pressurized into “moving up” into managerial roles and hence lose touch with coding? Or are we completely off the mark here?


Update 1: As suggested by Peter, read this entry tited “Stuck in Code” by Ravi Mohan for his tale on this topic.

Update 2: A related article in NYTimes recently titled “In India, Anxiety Over the Slow Pace of Innovation”


The magic of foss.in

December 9th, 2009

Why do I keep going back to foss.in? Because I’m the kind of person who needs extrinsic motivation. That’s why having a good circle of friends with a positive attitude is so important to me. And that’s why the foss.in community is so important to me. Because one must always strive to be in an environment where you are “the dumbest guy in the room”, i.e., be surrounded by really really smart people, so that you are forced to work on raising your own level. That’s how I feel when I’m in the midst of fantastic people such as bluesmoon, t3rmin4t0r, Srinivas Raghavan, and so many others. They are perfectionists who deep-dive into anything they are passionate about, and are invariably good at whatever they focus on.

The Good

Attending foss.in/2009 felt great for me because I took comfort in the fact that there are still people out there who are passionate about code and passionate about software. That is becoming rarer and rarer off late. I think it’s the “5 year limit” that I have observed in batchmates, most of them don’t want to code any more, and have moved on to so many other fields. While that is okay, the problem is that it has become a fashion to dis IT and software field.

Another factor was that everything is in the cloud and everything is a website these days, so does open source as a process matter anymore? First of all, the applications are not open source and even if we have the code (rare situation), you and I can’t fix the application/website unless you host it yourself.

But the foss.in community made me remember the joy of coding and joy of hacking.

Kudos to Team Foss.in for making the only community event and only IT event that is worth attending. It was fantastic to see how the concept of workouts had just taken off. And everyone’s been saying that all the keynotes have been fantastic.

In case you are wondering, I’m not the only one who was so enthralled by the event, for example:

fossdotin_janakiramm

fossdotin_ramblinggeek

See Lakshman’s writeup on the same. And so on.

Bottom line? Shut up and hack!

The Bad

Will miss the direction of Atul Chitnis.

What was missing

What I felt was missing is a discussion on the state of the art of software in each field, not just specific PoTDs. And I think this is more of a community perspective rather than the organizers’ perspective — organizers just provide the platform, community provides the content, as Atul keeps reminding us.

For example, consider my pet topic, the state of NoSQL databases – what’s good, what’s not, is it strange or expected that so many of them have come up in the last 1-2 years and all of them are open source (or at least the ones that we hear of). Taking it a step further, how it affects other fields of software. I’ve attempted to ask this before in a session at barcamp on whether webapp frameworks will adapt to NoSQL.

Similarly, what is the future of compilers, will LLVM + clang replace GCC (as @artagnon was speculating)? Will WebKit and V8 take over the world and leave Mozilla + Tracemonkey behind? Why are there so few projects using AGPL? What does it take to get full database dumps out of Wikipedia ? Will open source phones never take off? How does Eucalyptus help have an alternative with EC2? How does appscale help have an alternative to GAE? And so on.

In toto, I think there are three parts to this and I believe only the third part of which is done well already by the community and organizers: (1) what are the different fields and layers of software, (2) what is the state of the art of open source software in those fields, (3) getting people started and involved. I feel that only when we think on these lines, we will achieve Atul’s stated vision of “open source being the mainstream, proprietary software being the special case”*.

Thoughts?



* No flamewars please. I believe that the world will be better off by having all the infrastructure as open source software and having only the business logic / trade secrets as the proprietary part. At each stage of evolution of software, the stack grows higher, and the infrastructure/open source stack can grow higher along with it. For example, Robot Open Source and the Hadoop umbrella.

Coding Problems for Homework

November 24th, 2009

“Coding Homework” is a small website that I have built to list small problems that one can work on, to learn how to use a new programming language. For example, small problems requiring to read from a file, or to use regular expressions, how to find duplicate files in a folder, and so on.

Note that the problems listed on the site is not for testing your algorithm skills, there are many sites for that already.

This list was inspired by repeated requests and suggestions from readers of A Byte of Python for homework problems at the end of each chapter to exercise the skills they have just learned. So I thought why not make it applicable to any language and multiple programming skill levels. And it’s a good topic that can be collaboratively worked on with the programming community, à la Stack Overflow.

All the content will be licensed under Creative Commons Attribution-Share Alike 2.5 India License so that anybody can reuse this content, especially in classroom situations.

Screenshot of "Coding Problems for Homework" website

I also had my own specific goals when implementing this side project:

  1. Solve the lack of “homework problems” for people to exercise their programming skills, especially in the context of learning a new programming language.
    • I am not trying to replace existing lists but rather focus on making the reader active (providing exercise problems) than letting him/her be passive (reading code listings).
  2. Learn how to do website layouts, specifically how to use YUI Grids CSS.
  3. Learn how to pick colors for website design; ColorCombos turned out to be useful.
  4. Learn to use Google App Engine.

It has been a fun side-project, spending a few hours here and there. It is very far from polished, but the basic functionality works. There is still more to do — adding a search functionality, conforming to standard UI design patterns, caching for the rendered HTML (from Markdown), optimizing the housekeeping code, and so on.

This site itself is a good example on the kind of problems that beginners can work on, but they would not know what kind of problems they can solve and what level of expertise (beginner / intermediate / advanced) would be needed. That is where this list of problems can help.

I request you to spend 5 minutes of your creativity to add a few problems so that beginners and intermediate level folks will have interesting problems to test their learning of a new programming language. Thanks!

It might be helpful to you as well when you’re going to play around with functional languages (Haskell, Erlang, etc.), funky new languages (Ioke), or new languages by big companies (Go).

Link: http://codinghomework.appspot.com

Leaving IonLab

November 13th, 2009

Yesterday was my last day at IonLab, the company that I built with a few friends. It has been a wild ride but I could continue no longer. I am leaving due to internal differences on the progress and transparency in the company.

We have been well-supported in our experience, right from a Govt. of India grant to being one of the few to be selected as a TiE Entrepreneurship Acceleration Program mentee. We owe special gratitude for the people who made that happen and supported us.

But as any been-there-done-that startupper would expect, we delivered on technology, but we sorely lacked in maturity of management skills.

Simply put:

“Shipping is a feature. A really important feature. Your product must have it.” — JWZ

I can’t explain more because it would then amount to washing dirty linen in public.

Anyway, time to move on. Hopefully second time will be better!

I have been reflecting on many of the experiences I’ve had. So I thought I’d jot down the biggest lessons I learned as a startupper:

Stop reading. Start doing.

For every hour that you read, you must gain 3 hours of experience.

I read so much about entrepreneurship, although only after jumping into the startup. One and a half year later, we had made all the mistakes that those articles warned us about. The problem is not in the reading or understanding, the problem is in internalizing what you read. Wannabe startuppers read all the Paul Graham essays and say “Nah, that’s not going to happen to me, I’m going to be awesome and successful”, but when I read his latest essay What Startups Are Really Like, it felt like he crept into my head at night, stole my experiences and wrote a letter to me. Yes, really, it felt like that. But, of course, you won’t believe me. Until it happens to you.

What was the most common response from the YCombinator startups to Paul Graham?

When I look at the responses, the common theme is that starting a startup was like I said, but way more so.

Read those last few words repeatedly 6 times.

And I repeat, my warning to you is that simply reading A-Z of books and essays is not important, you have to internalize the learnings by testing it out on the field and realizing the value for yourself instead of saying “that makes sense” and forgetting about it a few minutes later.

Empathy matters

It is funny how most people will discourage you from doing a startup, and, today, perhaps because things have changed now because of all the media hype, most of my friends were discouraging me from leaving it now!

There are two aspects to this. First, read The Dip and you will know why I decided to quit. As Seth Godin says in the book, “The old saying is wrong – winners do quit, and quitters do win. Winners quit fast, quit often, and quit without guilt – until they commit to beating the right Dip for the right reasons.”

Second, as one of my friends observed, I talked to about 7 people (both acquaintances and friends) whose judgment I trusted. 3 of them sympathized and agreed with my decision and 4 of them admonished me and asked me to “hang in there.” You know what was the clincher? The first 3 had done startups themselves and the latter 4 had not. The latter 4 did not really understand the context, even though they meant well and are intelligent folks.

Imagine that a decision like this was so hard for friends-who-know-you to understand. Imagine how much empathy you should have for the motivations and work life of your customers!

Business is not a big deal, it’s only a mindset

The day I realized that I had started to think in terms of business was this conversation:

Friend: Hey, I wanted to talk to you about a gadget idea. Most phones have large storage space and bluetooth facility. Most cameras have small storage space. I have both of them on trips. I usually run out of space on the camera. So can there be a gadget similar to a bluetooth dongle that can move photos from the camera to the phone?

Me: Interesting… there is much to evaluate there (for example, I want to understand how much battery power it would eat up, which is the major concern when on a trip). But if you’re thinking about such a product, I think we should skip bluetooth and talk about peer to peer WiFi*.

Friend: What? Bluetooth is there on every freakin’ phone out there!

Me: Yes, but by the time you build this new gadget, all the devices would have moved to p2p wifi because it means supporting only one standard. Right now, phones have to support two standards – both wifi and bluetooth which is additional hardware and headache for the manufacturers. Since p2p wifi builds on top of the existing wifi standard, it makes business sense for them to standardize on that. Comparatively, the only advantage of bluetooth, AFAIK, is low power consumption, and that factor will reduce with increasing battery life. So, in 1 or 2 years, bluetooth won’t be the in-thing, and that is when the product will be ready if you start now.

Friend: stunned silence

Me: Did I say something wrong??

Friend: You really are a businessman now.

Me: Heh

See? It’s not a big deal, you just have to learn the right mindset. Note that I didn’t say it was easy, I’m simply pointing out it’s simply a different mode of thinking, and it is doable.

I realized that doing a tech business means you should know both tech and business really well (duh). And since I’m not there yet w.r.t. tech, I’m going to stick to that as my core for the next decade. Or at least, that’s the plan. Coding is still my first love. Update: After some thought and discussions with close friends, perhaps I can contribute in additional responsibilities such as product manager-type responsibilities as well.

* Also see What’s next for Wi-Fi?

Focus matters

A great advice I got from Muki, an entrepreneur was: “Start focusing on three things from day one – relationships, cash flow, balance sheet. You already know how to handle the rest.”

Notice he doesn’t talk about innovation, technology or all those other things. On the same note, the best explanation I’ve seen is that “Innovation is the by-product of a well-executed product”, which brings me to my next point.

“Focus” in the context of startups can be interpreted as good product management skills, which I strongly referred to in my StartupDunia guest post on the recent NASSCOM Product Conclave.

Maintain good relationships with partners, vendors, mentors, and all other folks that you meet in the course of your business. Don’t look at these relationships as opportunistic, look at it as an opportunity to co-create and learn.

Track your cash flow. Yes, you will earn millions later, but if you don’t have money now, you’ll die. You may not realize that the single highest factor why startups die is because of bad cash flow.

Don’t trivialize any aspect

Anything that is not managed will deteriorate, said Bob Parsons.

And it’s very true in this case, whether it is your legal company paperwork (yes, those stuff that you don’t want to be bothered with) or your project timelines (yes, tracking what’s on the critical path is very important, but you already knew that, didn’t you?) or thinking long-term as well as short-term, or networking with similar folks.

We, as tech people, think technology is everything and other people have it easy. I was like that. I learned it the hard way that “Easy is a term you use to define other people’s jobs.” I have a lot of respect for marketing and sales folks now. They have a really tough job, because it is about tenacity and psychology, compared to tech work which is write-once and scalable. Pop quiz: Did you really understand the signifance of that last sentence? If not, go back to my first point.

Have a sense of urgency

For every decision (and you will have a lot more of them than you realize), make sure that you do due diligence but at the same time, have a sense of urgency.

As Tecumseh Sherman said: “A good plan violently executed today is far and away better than a perfect plan tomorrow.”

Bottom-up always wins

This is the single most important learning, if I had to pick one.

Time and again, I’ve observed that bottom-up always beats top-down approach to problems. Note that I’m not discouraging you from planning, but I’m discouraging you from focusing purely on the plan. The plan is a guide to your actions, you should not spend more time on the plan vs. the actions and results!

And you can observe the power of bottom-up thinking time and again, whether it is in terms of societal change or productivity paradigms like GTD or the reason why Wikipedia and open source software are successful. As Linus Torvalds says “Software is grown, not built.” Mull that!

How does this apply to startups? Let us take one specific example: You have a new idea to solve a problem and you want to test if your idea works. If the prototype takes a couple of weeks, then you should go for the prototype. If it will take longer, how do you know that it is worth investing the time? Simple, use Adwords to assess demand for your new product/service. Same thing for doing market research.

Notice that in this example, we first start top-down by ideating and brainstorming, but then switch to bottom-up thinking once the initial plan is done – immediately jump to action by a real evaluation about the need that you are trying to solve. Then decide the second action based on the results of the first action.

How to define failure

This is how I explained failure to a friend: You walk into a new restaurant, and try the food. It can be good or bad. But you still have to pay the bill! You don’t know whether your effort is going to succeed or not, but you still have to put in the effort.

And the friend replied: The problem with most people is, they don’t want to risk eating bad food, that’s why they keep going to the same restaurant, even if they are bored of it!

When to call yourself an entrepreneur

I have this personal demarcation that I will call myself an entrepreneur when I have (1) created something new (2) made money. Until then, I’m a startupper (someone who has done or been in a startup).

This is the End

Hope these reflections are useful for future startuppers and entrepreneurs. All the best! (also see 10 things I wish I was serious about before starting a startup)

As for me, I’m cash-strapped (Didn’t I say lessons learned?), and hence looking for a job (product manager or senior technical role). Do let me know if there are any interesting opportunities out there.

An interactive version of A Byte of Python

November 9th, 2009

Roorky is a new startup that has created a new file format and software for interactive books. As part of the default installation of the software, they are bundling A Byte of Python free with the software.

What is interesting is that this may help complete beginners who stumble in getting started with IDLE, etc. The most common email that I get asked is when people run python abc.py on the IDLE interpreter prompt and wonder why it is not working – both the concepts of two command lines as well as the concept of running a program is not grokked well by beginners who are getting started, especially people who are self-taught. From that perspective, this is an interesting approach to the problem.

I am still not convinced about this approach because people cannot bypass the learning of how to edit, compile and run the code in the native environment, because that will be needed when writing new programs. It will be interesting how the two opposing needs will be balanced.

But I hope beginners will try it out and see if it helps them get started.

A full size video of a walkthrough of the software is available at the Roorky website.

Note: Be warned that it is a beta software.

What I learned at NASSCOM Product Conclave 2009

November 6th, 2009
  1. There are not enough good problems that tech startups are working on and there seems to be no shortage of funds, platforms and ecosystem partners willing to help startups. The ecosystem is hungry for successes.
  2. Product Management skills are the need of the hour, NOT talks about talks about opportunities in X sector, and so on. When there is no culture of knowing how to execute, rest of the topics are moot points.

⇒ Read more at our event coverage at StartupDunia.com.

Update: This has been cross-posted to the official NASSCOM Emerge blog.