StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8130210
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-15T00:49:33.850
FavoriteCount
0
LastActivityDate
2011-11-15T00:49:33.850
LastEditDate
LastEditorUserId
0
OwnerUserId
377270
ParentId
8129932
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think some of your code is a bit too verbose and fluffy to let you see what's really going on. Take this small section: <pre><code>if (foundGold1 == true) { if (field.alreadyFound1() == true) { } else { robot2.addGold(); field.foundGold1(); } } </code></pre> It could be written like this: <pre><code>if (foundGold1) { if (! field.alreadyFound1()) { robot2.addGold(); field.foundGold1(); } } </code></pre> Depending upon how this code will "grow" over time, you might want to simplify it a little further: <pre><code>if (foundGold1 && ! field.alreadyFound1()) { robot2.addGold(); field.foundGold1(); } </code></pre> Please note Matthew Cox's warning: young programmers often get caught up in trying to minify their code as much as they possibly can (Look I did it in 2 lines of code instead of 3!) -- I'm not arguing for the reformatted layout because it is smaller but because I believe this is easier to read. Depending upon the complexity of future code, I might give exactly the opposite advice to break apart conditions. The top priority is writing legible code. (The compiler can figure out nearly anything you throw at it -- you have to be able to understand it too.) His further advice to use arrays for <code>foundBomb[]</code>, <code>foundGold[]</code>, <code>robot[]</code>, etc. is superb -- and is best paired with using function arguments instead of writing multiple functions. Instead of <code>field.alreadyFound1()</code>, <code>field.alreadyFound2()</code>, etc, try: <code>field.alreadyFound(int something)</code> -- when you call them, it'll be <code>field.alreadyFound(2)</code>. This lets you cut the number of functions by three (which means you won't have to fix bugs three times in each function) and makes it easier to grow the program to five or six fields, piles of gold, bombs, robots, etc. It's just a parameter to a function then.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POI need a fresh pair of eyes for debugging
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsarnold
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.