m christensen wrote:
But, I'd presume the intent here is 'Experience' a software
development process.
Design and build in a vacuum and see what the users think after it's
done, as suggested above, is an all too common and WRONG
approach IMHO.
I don't think you are INTENDING to 'ask us to do your homework' but I
don't think you have yet done the work you need to
do before asking opinions. Final project or real-world-work the issues
are the same.
Mr. Newby you appear to have failed to do basic research into your
market or users needs.
First assess the need for your project.
It would appear you are under the assumption there are no GUI tools
for sqlite.
A Google search like "sqlite GUI" shows otherwise.
I DO think your general approach of asking people what they need or
want is a good one and could be
quite enlightening although probably not entirely along the lines you
probably first expected.
Do your research, figure out what YOU think the requirements and
options are.
Ask some direct and possibly leading questions but be open to answers
that may not be what you expect.
General open-ended questions may very well not spur any real discussion.
They often indicate you have not done your homework so-to-speak.
This applies even more in the 'Real World'.
I also see such questions in the real world as in indication of a
lack of commitment to the proposed project.
In short if YOU don't have the commitment to do your part FIRST why
should I spend a lot of time and effort on a response
you may or may not even look at before you flitter off to something else.
Just like in the real world some people may support your pet project,
some may be hostile, some couldn't care less and some
people think you 'shouldn't bother them with the details or
questions'. You will need to learn to deal with this too, it's part of
the job.
Let's say you take this advice and look at "SQLite Analyzer"
You then come back to this group with an intelligent question such as...
"I noticed SQLite Analyzer has a drag-and-drop qry builder. Is this a
Feature anybody here would actually use?"
Due to the fact most people here are developers I'd ASSume the answer
would be a resounding
"NO. If you can't write a SQL Qry, you'd probably be better off using
Access or something..."
Then someone may chip in "You know I have no need, but the end users
for my app sure COULD use a nice
PDF-Generating GUI Report Builder with a drag-and-drop Qry Builder..."
I'd sure Hope the intent of your project is NOT 'Write a PROGRAM to do
X' but to truly 'Learn how to develop an application
from inception thru needs analysis to development, debugging, and
final release and to provide a usable tool.'
This may not be an answer to the questions you thought you asked, but
IMHO it does provide
"other information 'I' feel would help YOU on YOUR journey"
Marc
This is a nice response to the issue. I still remember my own student
days when I'd put much effort into my papers. There was no internet back
then. To do my research, I hoofed it from library to library, lab to
lab, office to office. I'm a lot older now, and have the incredible
power of the internet to help me. I still am a student and still try to
learn new things. It's not easy, and won't always offer instant
gratification. But in the long run it counts for something. It's better
to learn something new than to sit in a lawn chair swatting flies!
Bob Cochran
Greenbelt, Maryland, USA
