Skip to main content

A New Leaf



Looking back at my posts, it's clear I've been an inconsistent writer at best; most would probably accuse me (and rightly so) of lacking the drive to stay with it. Well, I'm turning over a new leaf and will write regardless of the consequences.

Part of what's held me back is my personal fear of losing my job because I revealed something I wasn't supposed to. I've also struggled with an inferiority complex, and having people comment (or, worse, NOT comment!) on my writing still leaves me a bit queasy.

Anyway, now that I've grappled with my personal demons, let's get into the thick of things.

Today I had a call with representatives from TeamStudio to discuss the merits of their software and service offerings. As I expect has happened at many large companies using Lotus Notes/Domino, the application environment has evolved organically, and with limited governance. Many of those developing Notes/Domino applications operate outside traditional IT, instead reporting within business teams. Since the process of creating Notes applications can be pretty simple, most "professional" developers believe it's not something real programmers need to consider or be concerned with. And since these are the folks who most often drive formal IT infrastructure, Notes/Domino and its more casual developer community tend to be left out in the cold when it comes to effective tools for managing the application lifecycle.

This is the gap TeamStudio sees itself bridging, and based on the brief conversation we had today, along with a quick scan of their product portfolio, I'd say we'll be speaking more in the near future. The challenge will be justifying the resource and financial investments necessary to achieve the expected benefits, when there are so many other important initiatives to pursue.

Ah, I guess that's why they pay me the big bucks ;)...
Labels:

Comments

Post a Comment

Popular posts from this blog

On My Own - Doing It By The Numbers Over the weekend I got my first call on a consulting opportunity.  A few calls later I realized something - I hadn't figured out how to price my "product!" It's pretty hard for someone to buy something (or even determine whether they're interested) if they don't know the price. Of course, that realization came after I nailed down something even more important...my resume. I promised lots of friends, colleagues and former co-workers that I'd let them know how things are going, so I plan to catalog the steps in my process here on my blog in the unlikely event that someone else decides to pursue a similar path. I know this has probably all been written about before, but some of us are just too darned bull-headed to learn lessons from other people and need to make our own mistakes, carve our own paths. Step #1 - Define Your Product (aka Update Your Resume) I know most people probably keep their resumes current by looking at
4 comments
Read more
InfoWorld published this excellent brief overview video on cloud computing. Worth a look if you're in the dark about the cloud!
21 comments
Read more
GullFOSS - Sun Microsystems joins porting effort for OpenOffice.org for Mac We can only hope that there'll be some excellent cross-pollination between Sun's team and the folks at NeoOffice . NeoOffice has done a good job of delivering added value to OOo, and it would be a shame to see that good work fall by the wayside as the OOo core evolves to include its own Mac-native UX. I'm sure mine is not the only voice encouraging the teams to find ways to cooperate and bring the best of both to OpenOffice's Mac user community.
5 comments
Read more