Codex navigation
-
Engines and their tools
-
Game Tools History
-
The Toolsmiths GDC Codex
-
The Toolsmiths Glossary
-
The Toolsmiths Learning Paths
-
◍ Tools Engineer Learning Path
-
◎ Tools Engineer: Core Game Development
-
◎ Tools Engineer: Core Game Tools Development
-
◎ Tools Engineer: Core Software Development
-
◌ Computer Science, Algorithms/Data Structures
-
◌ Computer Science, Computer Architecture
-
◌ Computer Science, Databases
-
◌ Computer Science, Computer Networks
-
◌ Computer Science, Operating Systems
-
◌ Programming Language, C
-
◌ Programming Language, C++
-
◌ Programming Language, C#
-
◌ Programming Language, Python
-
◌ Software Engineering, Debugging/Troubleshooting
-
◌ Software Engineering, Version Control
-
◌ Software Engineering, Writing Code/Unit Testing/Refactoring
-
◎ Tools Engineer: Game Tools Development Disciplines
-
The Toolsmiths Knowledge Base
-
Tools Development Wisdom and Best Practice
-
The Toolsmiths Arsenal
-
The Toolsmiths Toolbox
Knowledge
Writing Code
- good function/variable names
- maintainability/readability vs performance
- commenting code, comment rot
- code smell
- exit codes vs exceptions
- cyclomatic complexity
- code review
- what to look for
- what to automate
Unit Testing
- the “unit”
- other types of testing
- why write test
- mock, stub, spy
- what to test / what not to test
- code coverage
- maintenance vs provided value
Refactoring
- what does it mean to refactor
- techniques
- when it is time to refactor
- estimating the effort
- when not to refactor or when to stop
- testing
Misc
- RegExp
- Development Tools
- Visual Studio Code
- Visual Studio
Resources
Book Links
Web Links
Video links