text stringlengths 0 1.15M |
|---|
That doesn’t mean the game itself should be simple. It just means that the experience and interface should be approachable and understandable. |
Conclusion |
I’m extremely happy with what I’ve done and, especially given that this was my first Ludum Dare. However, I feel like I’ve learned a lot of what not to do. |
The biggest problem is overscoping. Like Eric Decker said, the biggest lesson we can learn with this is probably with scoping – deciding what to do beforehand in a way you can complete it without having to rush and do something half-assed. |
I’m sure I will do more Ludum Dares in the future. But if there are any lessons I can take of it, they are to make it simple, to use frameworks and platforms you already have some absolute experience with (otherwise you’ll spend too much time trying to solve easy questions), and to scope for a game that you can complet... |
This entry was posted |
on Monday, August 27th, 2012 at 10:54 am and is filed under LD #24. |
You can follow any responses to this entry through the RSS 2.0 feed. |
You can skip to the end and leave a response. Pinging is currently not allowed. |
3 Responses to ““Survival of the Tastiest” Post-mortem” |
darn it , knowing that I missed your livestream makes me a sad panda ;( but more to the point, the game is … well for a startup its original to say the least ;D it has some really neat ideas and more importantly its designed arround touch screens whitch by the looks of the submission is something rare ;o or that could ... |
<?xml version="1.0" encoding="UTF-8"?> |
<segment> |
<name>PD1</name> |
<description>Patient Additional Demographic</description> |
<elements> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.1</name> |
<description>Living Dependency</description> |
<datatype>IS</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.2</name> |
<description>Living Arrangement</description> |
<datatype>IS</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.3</name> |
<description>Patient Primary Facility</description> |
<datatype>XON</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.4</name> |
<description>Patient Primary Care Provider Name & ID No.</description> |
<datatype>XCN</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.5</name> |
<description>Student Indicator</description> |
<datatype>IS</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.6</name> |
<description>Handicap</description> |
<datatype>IS</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.7</name> |
<description>Living Will Code</description> |
<datatype>IS</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.8</name> |
<description>Organ Donor Code</description> |
<datatype>IS</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.9</name> |
<description>Separate Bill</description> |
<datatype>ID</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.10</name> |
<description>Duplicate Patient</description> |
<datatype>CX</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.11</name> |
<description>Publicity Code</description> |
<datatype>CE</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.12</name> |
<description>Protection Indicator</description> |
<datatype>ID</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.13</name> |
<description>Protection Indicator Effective Date</description> |
<datatype>DT</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.14</name> |
<description>Place of Worship</description> |
<datatype>XON</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.15</name> |
<description>Advance Directive Code</description> |
<datatype>CE</datatype> |
</field> |
<field minOccurs="0" maxOccurs="0"> |
<name>PD1.16</name> |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.