Rampidbyter Rampid byter: A byte of my .Net developing life.

I went to the annual all-company meeting yesterday and was greeted with the birthday party for my company. They just turned fifteen years old last week, and in order to celebrate everyone was greeted to a feast. Not only did we get some sweet chow, but we were also given our choice of either a laptop bag that is Ipod accessible, or a backpack with Ipod accessories build in. I think it’s like the one they’re selling on ThinkGeek.com. Anyway, awesome, but we were also exposed to the next big plans of the company. I’ll stay mute on the details other than to say that we’re setting up a company blog.

Our new marketing guru is a giant blog fiend; his presentations reek of success and have the distinct feeling of professionalism that makes my skin want to start taking salsa lessons. In short the guy seems to know how to get his marketing on, and I’ll give it to him he’s got the charisma of a class full of Dallas cowboy cheerleaders. Unfortunately there were no Dallas cowboy cheerleaders, but maybe next company meeting? Guess nobody got my memo.

Anyway, I suppose that means I’ll be blogging on two fronts. The first of which, will be here where my internal dialog has a home, and the second will be my company blog. We’re trying to reach out to the community and share our group knowledge. Borg anyone? That’s a Star Trek reference in case you’re not in the know. However, I’m not going to be able to really talk about anything other than what I’m working on in the vaguest of sense. Like right now I’m working with JD Edwards Enterprise One. Here I can safely rename it to JD Edwards Enterprise Suck. See, freedom right there. No, at the company blog I’ll probably have to tone it down and mention how I have experience with working around, er, I mean making JD Edwards Enterprise One work better.

I suppose at some point I’ll get back to focusing on providing more technical blog posts about some technology I’m working with. Nothing incredibly exciting at the moment, DSN database connections, VB.net windows services, command driven program, management interface software, integrated ASP classic web pages, serviced soft parts pegging application, Kanban quantity calculation processing, and mostly going through the daily grind to work on six applications at once. One thing I can tell you is hard is explaining to a client they have to wait six minutes for an application to refresh its data because you’re having to go through about 40 million database records to get the status, date, and part details for sales orders. Now, that’s the hard one right there sir.