An example of a simple plan is a simple find plan:
iterate through the set
test each set member to see if it is the target; if it is, end the
iteration
Most computer scientists would (hopefully) call this the linear search
algorithm -- and therefore be very worried about using
I think this is a simple readability and/or standards issue. For
example, the APA publication manual specifically separates the label
from the bracket in reporting statistics and degrees of freedom, for
example for an analysis of variance it is F (2, 24) not F(2, 24).
I'm not so sure.
First, hello to Dan Frost.
C.Douce wrote:
Whilst I do appreciate the simplicity (and elegance) of the
'print I'm here' approach, when it comes to developing
embedded systems nothing can beat a monitor program, a
serial cable and the ability to plant break points in your
code when you begin
Ruven E Brooks wrote:
Suppose that you were hired (at an outrageous salary, of course) to be
the chief architect of this system.
If you could have a 20 page initial document on the internal structure
of this system, what would that document contain?...
Other thoughts, suggestions are welcome.
Gaspar, Alessio (USF Lakeland) wrote:
I can understand the love'em / hate'm positions regarding wikis, however I couldn't help but notice that some of the arguments below are very close to what used to be said by corporations about open source projects and development methodologies
All wikis
Ruven E Brooks wrote:
3. I didn't rule out active discovery of content. In fact, that's what
people do today in our organization;
they look at the code and analyze the code, using tools of varying
degrees of sophistication.
The problem is, it's terribly time consuming, and the same discovery
