olivierlacan

Screencasting Framework

The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.

Why you should care about screencasting?

You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.

1. Communicating more effectively - At Envy Labs we produce screencasts for our clients all the time. Whether it's demoing a new feature or for a presentation for an invester, they're often much more effective and pleasent than a phone call or screen sharing.

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

alexknowshtml

/* After switching stackingthebricks.com to ConvertKit in the last few months, I found a handful of things */
/* that seemed to slow me down/force additional scrolling, so I tried hiding them from the UI with these UserStyles */

/* Obviously, these are without warrantee and could potentially break, so don't blame me if they do. */
/* Also, I am not a designer so these may not make the UI better in _your_ eyes, but they make it better for me. 😅 */

/* Hide the dashboard graph (not useful enough to be there taking up 3/4 of the screen real estate every time I log in) */
.account-graph {display:none;}
.subscribers-index div[data-component='ReportsContainer'] { display:none;}