Ah, the calm before the storm… At least I hope there will be a storm. My team has just release a beta and I am trying to be patient as I wait for *real* user feedback. Let me step back a second and allow myself to introduce… myself. (1: I like movie quotes.) My name is Travis Bright and I’m the Program Manager for the Java Language Conversion Assistant (JLCA). Don’t know what the JLCA is? The short version: JLCA converts Java-language source code into Visual C#; making it easier for a developer to move to the .NET platform. If you are interested I have links at the bottom to a couple of press announcements that also include instructions on joining the beta.
Ok, back to the storm which sounded a lot more interesting before I had you read the condensed version of the professional life of a guy you have never met (me). Any release is wonderful, a milestone to smile-in-passing and know that all of the hard work was worth it. But beta is even more fun. JLCA doesn’t run an alpha program, so beta is the first real measure of a version. Sure, we have some of our partner companies try it out and give us their feedback (which is pure gold in my world) but pre-beta JLCA bits get to less than 20 companies. The first week, our beta touched an order of magnitude more customers. Which, living for customer feedback, is guaranteed to keep a smile on my face. As the bugs come in (hopefully this is where the storm starts) I get a couple of lines on what my customers think about the tool. Not to mention the improvement to the overall product. I can’t lose. Even duplicate bugs give me a great idea of the areas customers are exploring. One thing is sure: language converters are evolutionary products. And I don’t mean that they fundamentally change the world. I mean they take revision after revision to come to fruition. This is made even more challenging by the fact that neither the Java-language nor Visual C# (nor underlying .NET framework) is static. And trying to keep a bridge suspended between two moving points insures my job is never boring!
Why a new BLOG? Everyone has to have one right? No, actually. I have seen a few lonely comments about the JLCA and even more questions about migrating JSP, EJBs, … to .NET and wanted to create a compiling area for all of these. I fancy myself a bit of a developer and routinely write code to migrate. This gives me a great feeling of understanding. I _think_ that I know the normal issues and problems with running migrations, but the only way to be sure is to have real customers tell me. So, I will try to post interesting information on interoperability (yes I like when everyone can play together*), conversion, helpful (hopefully) tips from my recent migrations, and whatever else had caught my interest. Thanks for reading my FIRST POST!
*No, I do not think myself the guru of interop. that Simon G. is, but it is a wonderful model that actually works in practice!
Quick note: I will slip and say “my team”, “my customers”, or “my product”. I think that falls into the _motherly_ aspect of being a PM. I feel that I have responsibility over every part of the JLCA which gives me an improper since of ownership. If anything, the MS JLCA owners are my wonderful Dev and QA leads. Please take possessives with a grain of salt.
As with most BLOGs, this is my personal view of the world.
This posting is provided "AS IS" with no warranties, and confers no rights.This posting is provided "AS IS" with no warranties, and confers no rights.