Thorne Brandt

My goal for the next year or so is to publish a new one minute documentation of a realtime audiovisual performance every day before I go to sleep. I also plan to stream my process on twitch.tv/thornebrandt

Why am I doing this?

I was commissioned to develop some minigames for a mobile app for the brain training company MindKick LLC. I thought that it would be a useful opportunity for me to develop experince in Test Driven Development in Unity.

Unity has a built-in test tools that parse files for a [Test] Attribute within a C# files in the Editor folder, and displays the passing or failing describe blocks within a test window inside of the Unity Editor.

I was shamefully late in appreciating tests. I saw them as monotonous labor, more complex, cumbersome, and twice as time consuming as the actual code they were supposed to be testing. When I was getting started with front-end unit testing ( phantom, mocha, jasmine ), most of the time it was the tests themselves that were broken. I would spend hours stubbing methods with near-copies, which gave me the frustrating sense that I wasn't actually testing anything. Then when the code changes, you have to basically start all over again. This post is meant for anyone that is feeling similarly discouraged by the apparent lack of value compared to the effort and time-sink required for testing.

This website that you are looking at is powered by Ruby on Rails and React/Redux admin page.

Source is here if you want to make your own artist blog. Read more about design choices here

Shiftgig is basically an ondemand staffing company with a pool of pre-vetted specialists in a variety of fields. This type of business model requires different interfaces for clients, workers, internal account managers, and public facing marketing for potential customers.

I was hired at Shiftgig to diagnose a loading time problem on a backbone-powered admin calendar app in 2014. Backbone was all the rage in that era, so I developed their new work stack, which consisted of grunt compiling backbone.js, jshint linting, and QUnit testing, namespace conventions, bootstrap grid system and media queries, classical inheritance of basic view functions such as afterRender, relied on an event-driven PubSub code design pattern, and created modular helpers to facilitate rapid development.

See some code samples and design examples