SeanBritt.FA16CSTerms History

Hide minor edits - Show changes to output - Cancel

Changed lines 6-9 from:
* ex. data types?
to:
* data types - bool, char, int (longint, shortint), string, float (double, long, short)
* include - iostream for cin and cout statement
* main function
* return 0
Added lines 3-4:
%center%'''Programming'''
Added lines 10-12:

%center%'''Problem Solving'''
Added lines 3-7:
Let's do some thing a little different with terms: Can you list important coding terminology and explain it?
* ex. data types?

----
----
Added lines 27-33:
Incrementing -

Accumulating -

----

Types of loops? Wild loops! :D
Changed line 23 from:
* Codes v. Indicators -
to:
* Codes v. Indicators - Codes are data to be entered by the user, while indicators are internal signals to change the processing path.
Changed line 21 from:
* Positive v. Negative Logic -
to:
* Positive v. Negative Logic - sequential logic can only progress when a true value is input for positive logic, only when a false value is input for negative logic
Added lines 15-20:
* Syntax Error v. Logic Error - Syntax could be an error in a single string or an error in the way you entered the instruction, which might cause the computer to misinterpret; Logic could be a problem with the process you've designed to get to the solution, or your code sucks.

* Module - It can be separate and independent from the rest of your code; has one entry and one exit, one function; easier to interpret, helps organize the program; easier to troubleshoot (you can identify bugs within modules, rather than sifting through the whole code)

----
Deleted lines 26-30:
* Syntax Error v. Logic Error - Syntax could be an error in a single string or an error in the way you entered the instruction, which might cause the computer to misinterpret; Logic could be a problem with the process you've designed to get to the solution, or your code sucks.

* Module - It can be separate and independent from the rest of your code; has one entry and one exit, one function; easier to interpret, helps organize the program; easier to troubleshoot (you can identify bugs within modules, rather than sifting through the whole code)

----
Added lines 12-17:

----

* Positive v. Negative Logic -

* Codes v. Indicators -
Changed line 17 from:
* Module -
to:
* Module - It can be separate and independent from the rest of your code; has one entry and one exit, one function; easier to interpret, helps organize the program; easier to troubleshoot (you can identify bugs within modules, rather than sifting through the whole code)
Changed line 15 from:
* Syntax Error v. Logic Error -
to:
* Syntax Error v. Logic Error - Syntax could be an error in a single string or an error in the way you entered the instruction, which might cause the computer to misinterpret; Logic could be a problem with the process you've designed to get to the solution, or your code sucks.
Changed lines 15-21 from:
* Syntax Error -

* Logic Error -

* Modules -

*
to:
* Syntax Error v. Logic Error -

* Module -

----
Changed lines 13-21 from:
----
to:
----

* Syntax Error -

* Logic Error -

* Modules -

*
Changed line 11 from:
* Variables -
to:
* Variables - something you can change or adjust based on the needs of the program. examples include integers, also things like name, date, time (on a computer or on a receipt, or any number of other things!) They serve the purpose of holding the information that will become part of the output.
Changed line 9 from:
* Constants -
to:
* Constants - Something that doesn't change. In programming/problem solving, these are the elements that form the framework for your instructions or steps in the solution. Like in Dr. Rita's example, things on a something like a receipt that are constants would include age, company name, (maybe) font, location, symbols (like a dollar sign)
Changed line 5 from:
* Heuristic Solutions -
to:
* Heuristic Solutions - A solution that isn't solvable with step by step directions; it requires trial and error. An educated guess fits with this kind of problem solving more adequately than with algorithmic solutions. Deciding whether to expand a company is a good example because it's based on experience and knowledge. Opinion-based choices generally require more heuristic solutions; thus, computers are not always the best tools for solving them.
Changed lines 3-5 from:
* Algorithmic Solutions -

* Heuristic Solutions
-
to:
* Algorithmic Solutions - problem that can be solved by a series of steps. no straight-forward solutions; more complex than just a reaction to the problem. Like baking a cake or addressing a medical emergency or performing maintenance on a machine, there are a number of parts to the solution.

* Heuristic Solutions -
Changed lines 5-13 from:
* Heuristic Solutions -
to:
* Heuristic Solutions -

----

* Constants -

* Variables -

---
-
Changed line 1 from:
(:title:) Terms of the Day
to:
(:title Terms of the Day:)
Added lines 1-2:
(:title:) Terms of the Day
Added lines 1-3:
* Algorithmic Solutions -

* Heuristic Solutions -