Skip to main content

Bootstrap

This is a blog. I write this.

I am, as I write, a Senior Systems Specialist at GE Healthcare. Well, that is a good title to have. I am not what sure that exactly means though, but it is a mouthful. My in-laws are impressed. And so was my ex-landlord. Small things matter.

I have been with GE Healthcare since 2000, the year I was declared to be mentally and educationally competent to hold a full-time job. That explains the seniority. Seven years is not exactly a short time. Especially, when you can learn Java in 24 hours. Or, the Bible.

The team I am on, develops advanced post-processing applications in the Molecular Imaging and Computed Tomography. That's again, quite a mouthful, but this time I can stand to defend myself. The stuff people do on my team is pretty awesome, actually. Things like segmenting out the left ventricle of the heart from a gated PET cardiac scan and then detecting which muscle tissues are not getting enough blood.

I try to help from time to time, but they keep on giving me important tasks like setting up meetings, making sure the projector and the cord are in the same room, updating dates on a website to notify that the product is not getting delivered this quarter because the lead system designer is going for her honeymoon to St. Lucia; stuff like that. They also call me the "Lead Program Integrator" and I am told that I am responsible for end-to-end delivery of a couple of our premium products.

I am also told once I figure how to make these ends meet, I will be up for promotion.

When I am out of errands to run, I write. Poems, music and another blog. By now, you must be sure that this is yet another blog, even if you are not sure about what.

That's definitely vague.

Comments

Popular posts from this blog

Barcamps over the world: BCB3/Minnebar

I think I am kinda special. Not quite like Paris Hilton special, but getting a  chance to attend two Barcamps separated by 8000 miles in a span of 3 weeks has got to be some kind of special stuff. I think the big guy above is smiling at me. Invest in my equity. This is an article outlining some of the interesting differences I saw between the barcamps in Bangalore (BCB3, 31 March -April 1, 2007 ) and Minnesota(Minnebar 2007, 21 April). This is not an article intended to compare or pass a judgement. Just throwing up some observations, fwiw . I am not offering explanations, I am not a socio-anthropology by training. Some of these do not require a degree to arrive at the reason of causation, but I want to keep this blog close to what I saw, not what I think. At most, some "could-be"s. Both the barcamps have a local flavour and preservation of local flavour to me, is inherently good.  Consider food, for example.  A predominantly South Indian buffet spread for lunch at BCB3 a

Bambi 2.0

Bambi is a small coding-fest that we organise in our group at GE Healthcare. It was inspired by Yahoo Hackday after I heard about it at BarCamp Bangalore last year. I still remember, I came back all charged up after BarCamp and with some help from Arun B, we put together the first version of Bambi. Ours was a small team, roughly about 60 people, so spreading the news was not much of a problem. Getting people out of their workload was a bigger problem. The load is high and the work is, I guess, somewhat exciting ;-)  It is sometimes tough to lure people out of writing indexing algorithms for proprietary image databases or mitral-valve plane adjusters for segmentation of the human heart.     Today we had the demos for Bambi 2.0 The quality of demos were much improved and people came on the last day with some utterly cool demos. Unfortunately, I do not think I can write about them in detail owing to Intellectual Property issues but a mash of  Biometrics, Bluetooth, MRI scanners and

5 Ways to Kill a Post-Mortem

Software projects fail. One of the techniques you could apply to a project not going well is a post-mortem. A meeting where the critical participants meet to discuss what is going wrong. Preferably when there is still time to salvage things. But before you run a post-mortem of a project, here are some things you would want to consciously avoid. Hopefully as a project lead or in similar capacity, this will help you facilitate the meeting and shape positive outcomes. It starts with you.  The Final Blame-Game The idea of a post-mortem is to take an earnest look at some of the things that went wrong and understand why and how to avoid them. In brief, make mistakes, but please make new mistakes . If the meeting degenerates into blame-fixing, then you are headed in the wrong direction. Rule the meeting politely but iron glove. Don't let it become a mudslinging match. If you have been deeply involved in the project, chances are high that you would have your own frustr