Explanation of data structures, search, sorts algortithms etc

A free test data generator and API mocking tool - Mockaroo lets you create custom CSV, JSON, SQL, and Excel datasets to test and demo your software.

Web #application allowing to find local food trucks. Currently available only in Nuremberg, Germany. Excellent example of Google maps web implementation.

Meadows' book is foundational to systems thinking as we understand it today; it's also part of the first generation of similar books trying to make systems thinking less abstract (see also Senge's Fifth Discipline in business for example). It is not, however, readily applicable to game design.

Her book has long been a traditional entry point for people to understand systems, and was a great inspiration for me in writing Advanced Game Design: A Systems Approach. My focus there was to write a game design text explicitly based on the idea that games are systems. An understanding of sources, stocks, and sinks, and of reinforcing and balancing loops, is just the beginning; there's a great deal more that can be understood and applied in designing games as systems.

Pesonally I would put "Thinking in Systems" in the same class as Alexander's A Pattern Language; Hofstatder's Godel, Escher, Bach; Luhmann's Introduction to Systems Theory; or even Wiener's Cybernetics as sources of deep systemic knowledge useful for but not directly applicable to game design.

I do hope however that more and more game designers begin looking at their games as systems, and that understanding this way of seeing and thinking helps create more effective designs.

Input letters, adds (procedural?) decoration

Changelogs as a Service

• Integrate into App
• Create Public Changelogs
• etc

vsCode extensions, themes, settings, linting etc

explanations at https://youtu.be/zcgHK2DzX3M?t=20m

Changelog Documentation - Versioning

Versioning Changelog Documentation Guidelines

Application life-cycle management.

Create automated builds, deploys, management with habitat.

1. you write your code.
2. you write a plan.sh including dependencies, build steps and compile steps if necessary.
3. you manually or automatically run habitat builder according to the plan (through github hooks - gitlab possible?)
4. you get a .hart package to upload to habitat
5. you can automatically created containerized applications out of it -> docker etc

Examples of Gitlab workflow here, uses chef for provision

"Your marketing should be focused on what problems your product solves for the consumer."

Build a simple shelf of a backlog completing app.

Pulls in data from internet game database (which probably exists)

Displays it beautifully

Can pull in data from steam etc? Achievements, time played,

Pulls in data from howlongtobeat to show how long player has left (roughly)

pull in guides and helpful things

allow simple checking off, ordering in lists etc

Gamebridge.com!