in reply to Roll your own!

I tried to make a case for replacing a background process we have to unload some data from a database, ftp/scp it, then load it to a remote database. It would be perfect in a dynamically typed language like perl, would not even require extra code to transfer extra sets of data, that could all be handled by a config file, or very little extra code. Its currently being done by an unreliable program in a nightmare of spaghetti code in a statically typed language. The decision was made that we're not going to use a non-MS solution, so we'll spend more time trying to fix the current process than to replace it all with perl. And eventually we'll replace it with VB.NET, because it's the latest, greatest buzzword. I am the only decent perl programmer in the shop, so it may or may not be a reasonable decision.

Replies are listed 'Best First'.
Re: Re: Roll your own!
by Anonymous Monk on Nov 15, 2003 at 20:45 UTC
    there will be some database work later in this project. there's already some resistance to the idea of using db access modules. it's better to write them ourselves...
[reply]
      Simplest question to ask your boss - "What business are we in?"

      If you are in the software business and are ready to duplicate the efforts of thousands of other companies in order to produce something better than they have, fine.   Money spent and time used _may_ equal profit later.

      If you are not in the software business, however, why is your boss advocating the expense of producing something that already exists, is of better quality, and which is not _central_ to your business?

[reply]

In Section Meditations