Proper Location for Software Work

From now on I will use the Software Development subdomain to post complaints and reviews about the available social technology software, including WordPress and the various Content Management Systems aimed at managing web content.

This blog is for the parent domain, http://SocialTechnology.ca/ and will be restricted to more general topics, except for brief weekly summaries of development work. This work has only just begun, so all that needs to be reported is that I am experimenting with software to organize that development.

I have hit upon a workpath, however. After much consideration and experimentation, I have decided to do it this way:

write text using Open Office
convert the resulting file to a web page by simply by saving the file as HTML – yes, it is that easy
put the page on the web immediately as a static page, in a folder for raw pages to be edited later
also, do a copy and paste from the Open Office text file to other locations, either this blog, the SoftwareDevelopment blog, or some other location.

For now, I will work this way, very informally. Later the raw HTML web pages can be edited for content, and some imported into other systems.

This would all be unnecessary if … well, I will save my complaints for the other blog.

I got an interesting message today from Phillipe Nicholai (V), a Facebook friend, in which he said he had become a fan of IBM’s Rational Requirements Composer and suggested I become one too. Well, first, I am not interested in commercial software that is not open source. I am sure there is lots of good stuff out there, worth every penny, but I feel that when you by something like that, the seller owns you.
You become dependent on them for support.

Among other things, I used to do software support for a big commercial system. I know how it goes. Maintenance work is programming, and must be paid for. It costs a lot for custom support, but subscription services are not cheap and not reliable, either.

With commercial software it is often supposed to be “try it and buy it”, but since it is so much work to get something working in your environment it is often “buy it and try it”.

I have invested money in what is free open-source software because I felt the need for hardcopy documentation, usually a book.
I have bought a lot of books for software I never used because it proved inadequate in some way or another.

As for IBM’s Rational Requirements Composer, well, for what I am doing it would not be anywhere near the time when such a rigid tool would be necessary. Right now it would be a hindrance.

But let me just make a note of this. One of my first requirements for the new software being developed, “Support Requirements Analysis at Various Levels, Informal to Formal”. To which we might add considerable help based on previously collected information about the user.

Still writing about software development outside of the newly determined proper location, but that is OK for now, I guess. — dpw

This entry was posted in Uncategorized and tagged , , , . Bookmark the permalink.

Leave a Reply