diff --git a/src/diary/entries/250831 b/src/diary/entries/250831
new file mode 100644
index 0000000..4abcfac
--- /dev/null
+++ b/src/diary/entries/250831
@@ -0,0 +1,28 @@
+<!---->
+<h1>starting a new game project? don't forget to add these!</h1>
+august 31, 2022<br>
+#gamedev <br>
+<br>
+All the new gamedev project essentials. <br>
+<br>
+<h2>top ten </h2>
+<br>
+<ul>
+    <li>The core loop! Make sure it's prototyped and fun before wasting any time. </li>
+    <li>A way of assigning IDs and specific instance IDs for comparison and identification. </li>
+    <li>A translation. Embed no strings into the code. Instead use keys that retrieve a translation from a spreadsheet. This way, your text is separate from your code and easier to edit. It's not that much more effort to ensure changing the language works, so might as well. If you only know one language, use Pig Latin or just English with special characters, etc, for testing purposes.  </li>
+    <li>Version control. </li>
+    <li>Automated testing. </li>
+    <li>A GDD </li>
+    <li>A style guide.</li>
+    <li>Documentation.</li>
+    <li>Good debugging system. Add in cheats (god mode, infinite money, etc), skippable intro and cutscenes, and a way to check and edit in-game values. </li>
+    <li>Make input feel good. Responsive controls, smooth movement, etc. </li>
+    <li>A process - set granular goals, hold meetings with yourself, reevaluate your schedule, whatever you need to do to make consistent and meaningful process towards completion. </li>
+    <li>Save/load, serialization. </li>
+    <li>Game time - logic time and draw time </li>
+</ul> <br>
+<br>
+<br>
+Last updated August 31, 2022 <br>
+<br>