Talk:Development Guide

we should probably include a generic problem solving strategy game plan to most effectively address problems.

1:try to resolve issues directly. 2:work on side quests of related technologies improving things that could in the end help your final product. 3:collaborate and work on effectively communicating what end goals you're looking for. communicate your ideas of your side quests, and direct solutions, and report back when things are solved, or new issues arise. to note that a child issue is a sub issue of another parent bigger in the background issue that's trying to be solved. 4:understand that looking at an issue backwards is sometimes helpful. 5:publish so you don't have to re-explain yourself, and so you can remember what you were thinking at the time when you install from scratch the next time around, when your mental gymnastics are not as honed.