Home

This document outlines development practices and design patterns used in Tiny Lab Productions.

We use tlplib to provide a lot of data structures and utilities mentioned in this document.

This is not a bible. Discussion is welcome and encouraged. If you have better ideas and arguments to support them - we are listening. If you need clarification on something - you are welcome to ask as well.

Legend

Following notation is used throughout this wiki:

• #foo is instance method named foo.
• Player#foo is instance method of Player named foo.
• .foo is static method named foo.
• Player.foo is static method of Player named foo.

Tooling

• Unity plugin for ReSharper

Code Style

• General Style
• Using formatting to ease code understanding
• Using var
• Naming boolean parameters in call sites
• Do not duplicate meaning in names
• Handling Warnings
• Namespace Naming
• Library Project Namespaces

Principles

• DRY - Don't Repeat Yourself
• Single Responsibility Principle
• Communicating Developer Intent
• Partial Initialization
• Boilerplate
• Use intermediate structures
• Lying Type Signatures
• Functional Programming
• Reactive Extensions
• Garbage Collection

Data Structures

• Unit
• Option
• Either
• These
• OneOf
• Try
• Lazy
• Future
• Validation
• Tuples
• Data Struct
• Immutable Collections
• SList
• IObservable
• Subject
• RxRef
• RxVal

Typeclasses

• Typeclass
• Numeric

Design Patterns

• Only use ToString for debug purposes
• Communicating between scripts
• Refering to tags, scenes & resources from code
• MonoBehaviour Callback Interfaces
• Binding
• MonoBehaviour.Init
• Closing over local scope

Various Tidbits

• Difference between == and .Equals
• Generic Struct Boxing
• foreach Boxing
• Caching Material/Animator/Shader Properties