mirror of
https://github.com/Xevion/contest.git
synced 2025-12-05 23:14:34 -06:00
minor corrections in formatting/spelling STUDY and Spending 02/15.11 solution
This commit is contained in:
@@ -280,7 +280,7 @@ I would mostly pay attention to what it looks like, more than truly understandin
|
||||
* Coupling
|
||||
* Refers to how tightly or loosely two objects depend on or use eachother.
|
||||
* Tight Coupling
|
||||
* For example, a tightly coupled relationship, a Human and his/her Heart, they are highly dependent on eachother to continue life.
|
||||
* For example, a tightly coupled relationship, a Human and their Heart, they are highly dependent on eachother to continue life.
|
||||
```java
|
||||
class Human {
|
||||
private Heart heart;
|
||||
@@ -325,9 +325,17 @@ In fact, it's likely that aspiring Software Engineers will want to get used to t
|
||||
* Make sure your lines are straight across the paper, and do not slant haphazardly.
|
||||
* Write somewhat large. Not excessively large, but larger than one would do for Essays in English and other writing assignments. Gauge how much room you need to answer the Free Response and write in a size accordingly.
|
||||
* APCentral has actually released a example of good penmanship, seen below.
|
||||

|
||||
<br>
|
||||
<div align="center">
|
||||
<img src="https://i.imgur.com/mx1PP73.gif" alt="APCentral Penmanship Example">
|
||||
<br>
|
||||
<sub>
|
||||
Notice the superb spacing and straight, aligned lines of text.
|
||||
</sub>
|
||||
</div>
|
||||
|
||||
* Bracketing Style
|
||||
* When writing brackets, follow this format (I may not be following this format in the rest of this file, sorry).
|
||||
* Brackets go on new lines (I may not be following this format in the rest of this file, sorry).
|
||||
```java
|
||||
class File
|
||||
{
|
||||
|
||||
@@ -10,6 +10,6 @@ Without thinking, it would seem that it's similar to the rest, and can be implem
|
||||
|
||||
Here's an example of how it might go wrong, a implementation that essentially buys the most expensive items first... With three items with three distinct worths, $40, $30, and $20, with a total budget of $50, one can quickly notice that purchasing the two items worth $30 and $20 will yield the budget matched perfectly. However, a implementation that buys the most expensive item first will fail!
|
||||
|
||||
Similarly, a implementation that does the opposite will fail too: five items, [$50, $25, $15, $5, $1], budget of $65. The implementationn will attempt a combination of $1, $5, $15, and $25 for a total of $46. The proper choice would in fact be $50 and $15. The choices picked have no distinct pattern, and a `Combinations` algorithm will need to be implemented, which can be very difficult for those new to it (me included!).
|
||||
Similarly, a implementation that does the opposite will fail too: five items, [$50, $25, $15, $5, $1], budget of $65. The implementation will attempt a combination of $1, $5, $15, and $25 for a total of $46. The proper choice would in fact be $50 and $15. The choices picked have no distinct pattern, and a `Combinations` algorithm will need to be implemented, which can be very difficult for those new to it (me included!).
|
||||
|
||||
My implementation is incomplete as of this moment.
|
||||
Reference in New Issue
Block a user