Re: Definitions of Software and Database
Date: 6 Feb 2006 09:42:11 -0800
> dawn wrote:>
> > Of course then we might have to define "thinking" ;-)
Perhaps we have to define the word "define" :)
What happens if a stone thinks it's a gem, or suddenly turns into a marble? Sorry, couldn't resist :)
> What happens when one encode the state diagram into some memory ?
> What happens when one interconnects lots of those ?
> What happens when one encode the interconnection scheme into some memory ?
> See this:
> > > That definition may be indistinguishable from ye lores of olden, but yet
> > > it is the plaine truthe.
> > This would make a "data entry person" a software developer by
> > definition, right? Perhaps we can add an intent phrase, although I'm
> > not sure that changes it sufficiently:
> > A software developer is a person who intentionally causes 0's and 1's
> > to be ordered in such a way as to bend a thinking stone to obey their
> > will.
> How can you tell a data entry person from a software entry person ? :-)
How can you tell an artist from a copy machine? I think that's what you're saying, and I agree with you x, and I think I can answer that.
To be a good lumberjack, you would probably have to have clout with your fellows, possibly a reputation, dust in your ears, sand on your clothes, and a good bedroll. You then talk like a duck, and walk like a duck, and for me, you probably are a duck -- to make an analogy.
Dawn, with all due respect, I don't think a "software developer" is something you can nail down, for better or worse. And maybe that's part of what's on your mind (among other things, of course :). The data about who is a "developer" can't be nailed down, or then maybe you don't like nailed down thinking anymore (which, as it happens, the RM model seems to ascribe to).
In any case, you are pretty good at stirring up some interesting conversation.
Todd Received on Mon Feb 06 2006 - 18:42:11 CET