Databases
StackOverflow2013
Postsdbo
POIs contributing internal tools to open source worth the effort?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs contributing internal tools to open source worth the effort?
    primarykey
    data
    text
    <p>I know this is a general question, but I'd like to hear other people's opinion about our case:</p> <p>I work in a small company. Our main development tool is PowerBuilder, which is a very limited IDE with a shrinking community. We've created some tools, which we use internally to solve a certain needs. They have neither been properly designed nor properly tested, and are not in production quality. OTOH, they do save us quite some time, and might help others as well. I'm sure other companies have the same kind of tools, and was wondering how common a practice is it to share them with others. As I see it -</p> <p>The pros:</p> <ul> <li>Good karma</li> <li>More attention to our website</li> <li>Perhaps getting fixes and improvements from others</li> </ul> <p>The cons:</p> <ul> <li>Without investing more development, the tools might make us look bad</li> <li>Publishing of the code requires some effort</li> <li>Some of the tools might be too specialized for our needs</li> <li>The whole effort might go unnoticed given the shrinking community</li> </ul> <p>Have you or your company ever contributed such tools, or used such tools developed by others? Is it worth the effort?</p> <p><strong>EDIT:</strong> </p> <p>For those how wondered, the tools I had in mind include -</p> <ul> <li>A tool that makes using SourceSafe easier, by listing objects that are checked out to the current user or others, backing up checked-out objects, and reconstructing PBGs.</li> <li>A tool that recognizes PB controls at runtime, like Spy++ does (requires some infrastructure at the target app).</li> <li>PBNI wrapper for SQLite (in-process access, no ODBC).</li> <li>An SQL client, text measurement tool etc.</li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USeran
    1. USeran
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs contributing internal tools to open source worth the effort?
      1. USeran
      1. VTFavorite
    2. VO
      singulars
      1. POIs contributing internal tools to open source worth the effort?
      1. USRobert Greiner
      1. VTFavorite
    3. VO
      singulars
      1. POIs contributing internal tools to open source worth the effort?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you decide to release, please link your site from this question! We are a powerbuilder shop too and I would definitely be interested. In fact I might be able to get one or two of our internal tools released too.
      singulars
      1. POIs contributing internal tools to open source worth the effort?
      1. USColin Pickard
    2. COVery much interested in the code, too.
      singulars
      1. POIs contributing internal tools to open source worth the effort?
      1. USFrerich Raabe
    3. COThis question has been eloquently answered and your question is a great one. I just wanted to say good job; it is developers thinking like you do that make an IT shop (and user community) better. Of course there are exceptions; but how can anyone argue with your sincere desire to not just think of yourself but to put extra effort in and make things better for everyone. In my experience this always comes back around in a positive way. There is one Fortune 100 client I've worked for that is an exception; and it was just one department; they were all about slamming junk out the door.
      singulars
      1. POIs contributing internal tools to open source worth the effort?
      1. USRich Bianco
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload