This blog is officially closed…

Hi,

Just wanted to announce that this will be the last post on this blog.

To all of you who read these posts and took the time to comment, thanks a lot. And may our paths cross again in the future.

Good bye, and good luck!

NetBeans day at the JavaOne conference…

Just to let all you guys know that I will be presenting a 30 minute session on “Architecting thin-BLL applications using Open-ESB and BRMS” at the NetBeans day [Day 0 of the JavaOne conference] this year. If you are in the San Francisco area on May 7th and have some free time, please feel free to drop by and chat.

Some important links:

1. JavaOne conference homepage - http://java.sun.com/javaone/sf/index.jsp

2. NetBeans Day @ JavaOne - http://www.netbeans.org/community/articles/javaone/2007/nb-day.html

3. Introduction to my talk - http://www.netbeans.org/community/articles/javaone/2007/partnertalk-yasutech.html

See you guys there!

Customer Service & British banks…

Been reading through some of the blogs on cricket [the game, not the animal], since this weekend is THE game - the World Cup finals! For those of you who have no clue about how cricket is played… think of it as a far more complicated version of baseball, and lets leave it at that :-)

So, anywayz, chanced upon this post: how-to-deal-with-a-british-bank

Funny, funny! Simple problems to solve with modern technology…. the only thing that preventing the solution from being implemented is a kind of corporate madness [err…. empire building inside the office], I guess.

Enjoy!

Out of hibernation…

Whew! Its been a while since I’ve posted anything up here…

My apologies for the unscheduled break in the blog - it seems to me that, no matter how many times I’ve relocated (9 times in the last 15 years!!), it just does not seem to get any easier :-)

Getting the basic stuff up and running (apartment, utilities, cable, internet, et al) is a matter of 2 - 3 weeks, right? Right! But doesn’t that mean you are “settled in” and ready to go? Wrong! Getting used to a whole new office environment, getting to know colleagues, the work, learning a whole new domain [business and/or technical], figuring out where to buy/rent furniture, a car, etc., etc. - I’ve had to re-discover that some of these things just take time…

Anywayz, the end result was that, for the first 45 - 50 days, I simply was in no position to read any blogs… much less think about what I’ve read and post something up here. Its only been in the last week that I’ve managed to consistently touch the blogosphere on something approaching a daily basis…

Anywayz, here is a synopsis of the last 2 months:

  • “The Colbert Report” is awesome :-)
  • Rajgo got his blog into the “Top 100″ technology blogs in the world! Way to go, buddy… you deserve it!!
  • The sub-prime mortgage market melted… taking with it some of the biggest names in the mortgage industry. Talk about an implode… there goes one of the cash cows for the BPM / BRMS / BI guys - at least for the next few months.
  • Google Analytics tells me that the average number of visits to my blog hasn’t changed much! Wow!!

Oh, and…

  • Enterprise Library 3.0 was released - with a new Policy Injection Application Block. What are the implications to the business rules products out there?
  • Windows Presentation Foundation & Silverlight are getting into the mainstream - built on top of XAML. Does this make authoring validation logic easier? Again, what are the implications for BRMS vendors?

Which brings me to something that’s been puzzling me… BRMS, BPM, and BI blogs seem to be talking about pretty much the same things… Why? Are things so stable that only the nitty-gritties are changing?

Has anyone posted on the synergies between WPF / WCF / Silverlight and BPM / BRMS, and the implications [positive / negative] of these new technologies for .NET-based BPM / BRMS products?

Also, Microsoft partners are now allowed to develop / market products for the “Office Live” marketplace.. and K2.Net has already put up its BPM offering up there! Anyone else with a roadmap?

Finally, here’s an interesting piece on the advantages of BRMS technology to a BI solution…

Cheerios! And, if I can’t post tomorrow, have a nice weekend, everyone!

Jet-lagged et al….

I am through with the 28 hour flight from Hyderabad, India to Irvine, CA, USA - got into office for the first time today.

I am, of course, still getting setup in the country - getting an apartment, driving license, bank account, etc. Assuming that I will be done with the formalities by the end of this month, I will start getting productive in anothe couple of weeks :-)

I know it sucks, but in the meantime, I’ll probaly manage to update this blog just a few times :-(

Co-ordinates: A change…

Just to let you guys know that I am relocating to the USA on a long-ish assignment for my employer, YASU Technologies.

I will be based out of Irvine, CA [Orange County… south of Los Angeles] for the next few months, and maybe for as long as 3 years. I would love to meet up with any of you in the vicinity…

I should be reaching Irvine late evening, 12th Feb 2007, provided the guys in immigration / customs @ LA airport let me through :-)

Have a nice week, everyone!

Recruiting visionaries from IIT???

Whew! I am done with the recruitment process for the year, and am finally back in town / office!!

First things first… we did follow the methodology I wrote about earlier and we did manage to recruit a few people from the Indian Institutes of Technology. One of the things I noticed about the successful candidates is that all of them seem to have some kind of a hobby or the other - video games, sports, dancing, music, biking, wildlife, etc., etc. - which should keep the office an interesting place for at least another year. Does the fact that we chose to select people who are good at teaming up have a bearing on the fact that everyone has a hobby? I certainly think so…

Second… I seem to have attracted a rather long, and unnecessarily acerbic, comment to my post on the recruitment methodology. By “Mr. Anonymous” too, at that… am I that terrifying in person that people are scared of telling me their identities? I wonder… maybe I should grow a beard + mustache, dye them florescent blue, and wear red contact lenses to look more human and less terrifying?

Whatever… the comment seems to be based on the fact that we are choosing firefighters [so sorry, Mr. Gates, you have no clue about strategy :-) ] and not strategists. To answer the valid points in the comment, though:

1. The ability to test sustained learning. Yes, this methodology does not test for this ability, thoroughly. On the other hand, I am forced to choose 3 - 5 people from 60 - 100 IIT-ians [supposedly brilliant / genius - by definition - right?] in a single session of 4 - 6 hours. So how can I go about it? Is there a way to do it? What is “sustained”? 6 hours of learning? 8 hours? I can argue that sustained learning for a whole month is also no judge of this ability - since careers last 45 years! So, I don’t know - anyone with ideas, please feel free to tell me how…

2. This whole mish-mash about choosing strategists over firefighters, etc., etc. On the one hand, you need strategists for a company to grow and prosper. On the other hand, there is an old aphorism about “Too many cooks…”. So the question is, how many do you need? And what should they be doing? The corollary to that one is, if the strategists are in the wrong place in the hierarchy, what would happen?

From my perspective, we hire fresh college graduates for developer positions - not to tell the CEO how to run the company. I would rather test and select people who can write some code and have a life outside of office - rather than, say, creating a HR nightmare by selecting “visionaries” [@ 21? Right!] who will crib and complain about being made to write code. Thats my perspective, and as the recruiter, my prerogative too.

So where are the strategists going to come from? Well, for one thing, lateral hires at a senior level [CxO, VP, Product Manager, etc., etc.]. Second, home grown talent that rises in the organization by hard work and perseverance - at a minimum, it will take 8 - 10 years for the newly recruited candidates to even start thinking about it… which is plenty time to learn “strategy”.

The argument against those statements could be - strategists / visionaries are “born”, and not “made”… Really? For sure, you’ll have people who have this uncanny business sense right from the word go - in any field, there will always be geniuses. On the other hand, most people who get to be CxO at some company or the other get there by going up the ranks - they are the ones with talent that has been honed by sheer practice.

So, thanks for the suggestion, but I’ll go with firefighters who may turn out to be good visionaries in the end - I’ll worry about it if none of these guys are getting there after spending 10 years in YASU Technologies.

Aaah! Its good be back blogging!!

Recruiting candidates from college: Thoughts on “What is the best interview process / approach?”…

As mentioned here, I am in the middle of an extremely hectic trip around the country to recruit the next generation of YASU-ites from the premier engineering colleges in India - the Indian Institutes of Technology (IIT). I am done with IIT Delhi, IIT Kanpur and IIT Roorkee - IIT Chennai, IIT Kharagpur, and the rest still beckon…

The recruiting trip has made me think about the methodology involved and the inevitable question - how should a small company like YASU Technologies go about recruiting final-year undergraduates into its workforce?

Before I get into the details about the methodology, here is the background:

Most IT companies visiting college campuses [in India, at least] go armed with predefined question papers containing lots of “analytical” questions [puzzles, lateral thinking stuff, geometry riders, etc.] - the assumption being that anyone good enough to solve a certain number of these questions within a short time-frame should be good enough to write code [after training, of course].

Now, what we asked ourselves was… is the assumption true? Lets look at it in more detail:

1. IT companies typically repeat the same puzzles, riders, and question papers, year after year - the HR managers usually cannot research / create new questions year after year. So, most final-year students know before-hand what the question paper looks like, more or less.

2. IT companies try to minimize this by refusing to give copies of the question paper to the students after the examination is done. However, IIT-ians, on the whole, have good enough memories that each one can remember at least 2 - 4 questions. So, a group of IIT-ians can, in fact, take the whole question paper out of the exam hall without requiring a physical copy of it. Mobile phones with cameras are, of course, just an extra convenience…

3. In essence, what this means is that IT companies are just testing for speed of recall / writing - not for innate analytical ability.

4. The final, and most important, part is something that every cryptologist knows - security by obfuscation isn’t security at all :-) Only if the cryptographic algorithm is out in the open, and reviewed / hacked endlessly, can you be sure of the security… Right? Absolutely! In the same vein, hiding the question paper and expecting that it will be completely unknown to the students is just deluding yourself…

So, now, getting back to the methodology… how can YASU be sure of getting the best available talent from the IITs when the question paper is known before-hand? To answer this question, we asked ourselves what it is that we are looking for in fresh graduates…

The simple answer is - analytical skills [implying the ability to write good code]. The more complex, correct, and elaborate, answer, is - current analytical skills + ability to learn + ability to function both independently as well as in a team. Of these, the first one is almost impossible to test for, for reasons already mentioned. The other two, however, can be…

So here is what we’ve done this year:

Step 1:
1. Go prepared with the usual predefined question papers with analytical questions.

2. At the beginning of the placement session, ask the students to form groups - any number they are comfortable with. Give the question paper to the groups and let them discuss the answers for 20 min.

3. At the end of 20 min, ask them to split up, and write the answers down in the answer sheets on an individual basis. Time allotted: 30 min.

4. Shortlist the 5 - 6 groups with the highest average number of marks, but call only the top 2 - 3 from each group for the second round of the process.

At this stage, what we’ve tested for is the ability to discuss solutions to problems within a peer group, and the ability to formulate solutions individually. Pretty much what happens in offices usually… There is a reason to share your knowledge [groups with the highest average], and a reason to do your best when implementing the solutions [only the top 2 - 3]. As a result, foreknowledge of the paper does not imply promotion to the second round automatically…

One way to beat this would be to come with a group of friends, and solve the paper. If only 2 - 3 people in the group are serious about joining YASU [and the others are not, but are there to help out], then they can orchestrate it so that the serious guys are the only ones going through.

But its still an “iffy” thing - since everyone has to answer as much as possible to get the highest average for the whole group… one mistake by the “serious” guys, and the non-serious students will go through to the second round.

The time-constraint thing is, of course, going to add to the pressure. IMHO, it is not impossible, but very tough, to ensure that only the serious guys in the group will be the ones who get called for the second round.

Step 2:
For the second round, we decided that we will test the ability to learn on an individual basis, given that the guys in this round have already demonstrated sufficient skills to work in a team.

The way we went about it was:

1. All the selected candidates to give a 3-minute talk on their final year project.

2. Everyone is expected to take notes and ask as many questions as required in order to understand / clarify what the speaker is talking about.

3. At the end of the presentation round, we drew lots to decide which final year project each candidate will talk about - their own is, obviously, ruled out.

4. Each candidate to present a 1-minute talk on someone else’s presentation.

5. No candidate will present on another final-year project from the same stream as his / her major [subject], and no candidate to present a final-year project from someone in the same first-round group.

6. Marks to be awarded for the quality of the candidate’s final-year project presentation (20%), for the quality of questions asked (40%), and the quality of the second presentation (40%).

So how can you try to beat this system? One obvious way is to give a slightly bad first presentation, and give a very good second presentation. That way, whoever gets to present your final-year project will, automatically, get a bad second presentation. Minimum damage to you, since its only 20%. Maximum damage to someone else, since it’ll be 40% for him/her.

But giving a sub-standard first presentation invites a LOT of higher-quality questions from the others who want to understand your project. So, they’ll get more marks for the quality of questions asked (40%) that you will, esp. since you cannot ask questions on your own project :-) All in all, again, its a tough test to beat… though not impossible.

Anyway, by now, the guys have cleared “teamwork”, and “learning ability”, so…

Step 3:
The final step was to test how much the candidates know, and how quick are they in writing down what they know… in essence, measuring what HR managers try to measure using the standard “analytical written test” pattern as step 1.

The way we went about it was:

1. Get all the candidates selected in round 2 together in one area.

2. Give all of them a question to solve at the same time [by reading it aloud].

3. The first 3 - 5 people [depending on the requirement] to solve the question get 1 mark each. The others don’t get any.

4. Repeat the process for 10 - 12 questions.

5. The 3 - 5 candidates at the end of the round are the guys who get selected.

Essentially, this is a “sudden death” round. You need to have your wits about you, enough practice / preparation in solving all types of questions [puzzles, math stuff, riders, etc., etc. - since we chose a good mixture of different types], be very fast, and be able to work accurately under extreme peer pressure.

Conclusion:
By selecting candidates in this fashion, we hoped to get people with the ability to think fast and accurately under pressure in unfamiliar situations, learn quickly, be able to work in a team, and implement things independently.

We also hoped to eliminate the guys who do well simply because they’ve prepared all month long by introducing an element of randomness - essentially, the other people they need to interact with, learn from, help, and work with.

Did this procedure work? Well, since the selected guys are going to join in July / August of this year, I suppose we’ll know in 18 month’s time :)

In the meantime, your comments / criticisms are most welcome. Also, suggestions regarding the ways and means to “beat the system” are doubly welcome - I would love to know how a student can go about it, assuming they’ve chanced upon this post and are mentally ready for the procedure.

And now, its back to traveling and other stuff… have a nice week, everyone.

Business Agility Primer: Requesting your help for AN idea…

I had posted a while back on the “Business Agility Primer” - I’d promised that I want to get it done and over with by 15th Jan… So, I have been preparing a lot of material, etc. for the primer series - things like the capabilities of BRE / BRMS, BPM, ESB, BI, ECM / CMS / DMS, etc. The basic focus was on how they can be integrated with each other to provide far more “agility” than each one can provide by itself.

One place where I am stuck is finding an overall “context” to put all this information in - I mean, just writing post after post on this subject will be of little use unless readers can relate it all to a business use-case that they are familiar with.

Ideally, I want an example business use-case where business processes, business policies / business rules, metrics, regulations, documentation requirements, etc. change often enough to justify the use of “agile infrastructure software”.

Remember, I have been trying to get a hold of a business use-case that ALL of us are familiar with, and not just a few people in certain verticals.

In this context, my thoughts on this have wandered towards the usual suspects - insurance [claims processing], mortgage [anything in the loan origination life-cycle], human resources [hiring, appraisal processes], and telecom [billing] - I am assuming that most of us have been through at least one accident, applied for mortgage, paid cell-phone bills, or hired / appraised someone at work.

Now, my current traveling schedule means that there is no way I will be able to post on this topic till the end of this month. However, I can certainly think about it…

So, if you come across this post and are interested in contributing, please do send me your thoughts on which business use-cases I should consider. You can leave a comment, or send me an email.

Do remember that, when you are suggesting a business use-case, it has to fulfill 2 separate but essential criteria - it has to be in a constant change of flux, and it must be something that people will understand & relate to based on their daily experiences.

Over to you, guys…

Away from Office… recruiting the next-gen

I’m in the process of going around India recruiting the a bunch of kids from college for the next-gen YASU employees…

The schedule is almost impossibly tight - have breakfast by 8:00, do the pre-placement talk from 9:00 - 9:30, conduct the written test from 10:00 - 11:00, finish the shortlist by 2:00, break for lunch, and start the round of personal interviews, etc. by 3:00. Typically, we finish the placement process by 9:00PM, give the list to the placement coordinators, and break for the day…

Its travel the next day to repeat the process in a different place the day after… and I am going to be doing this through the month - till the 30th, to be exact. As a result, my blogging will have to take a back seat… whenever I get some free time, its dedicated to my family, and to responding to my official emails…

I may post a few if I can mange to squeeze in 20 min for it at some point. Otherwise, regular service will resume in February.

Happy new year, everyone!