Skip to content

Instantly share code, notes, and snippets.

Addressing Communication Gaps at Tech Companies

Development and Customer Support

Set up the topic

  • Intro with well-known "7 red lines" skit
  • Indicate that while it can be true, it's only half of the story
  • Brief overview of my previous company and position on a Customer Success Team

The Scenario

  • Walk through example issue that caused tension between Dev and Support

Step One: Watch Mary Rose Cook Live Codes Space Invaders from Front-Trends. (The second worst conference name ever?)

Step Two: Fork this gist.

Step Three: Respond to this question in your fork: What is one approach you can take from this Mary's code and implement in your project?

  • I actually had watched this prior to starting our project. It lead me to try to be hyper organized and structured with our project and until I got passed that and let myself write gross code first. I did, however, take the keyboard tracker concept from her game and implement it in ours (where it maintains a hash updating true/false values for the keyCode keys. We built more on top of it limiting which keys were recorded and implementing it over socket.io.

Step Four: Totally Optional: take a look at some of the other forks and comment if the spirit moves you.

@jecrockett
jecrockett / require.markdown
Last active April 5, 2016 14:46 — forked from rrgayhart/require.markdown
The Concept of Require

When you start working with WebPack for GameTime, you'll notice that you can't just define a variable in one file and find it in another as easily as you can in Rails.

Read Node.js, Require and Exports and Organize Your Code with RequireJS

Fork this gist and answer the following questions:

In the context of Node, what is a module?
  • Modules are small chunks of your application that serve a specific purpose (cite: 2nd article). It's basically a group of functions/variables that are related and belong in their own separate file. I think of it like a class but I don't know if that's technically the right way to think of it.

JavaScript Functions

I can explain the difference between function declarations and function expressions.

  • Well, at least one of them. Function declarations are hoisted, but with variables only the declaration (NOT the definition) is hoisted, so the variable still isn't defined until the code gets there.

I can explain what the value of this is in a normal function.

  • global object

I can explain what the value of this is when called from the context of an object.

  • it's the object.
@jecrockett
jecrockett / package-management.markdown
Created March 24, 2016 21:27 — forked from rrgayhart/package-management.markdown
The Dangers of Using Code You Don't Control

Which sections were interesting?

  • The initial chapter 3 'quirks' were interesting, as was a lot of the explanation regarding function expressiona and declarations.
  • Objects and their properties -- Feel like I'm starting to mentally put together what OOP will look like with JS
  • The fact that the inverse of 'strict mode' is called 'sloppy mode', at least in chap 17.

Which sections did you totally skim?

  • By the third "variation on IIFE" section I started to skim those.
  • Property attributes and property descriptors. The "advanced topic. You normally don’t need to know how they work." suggested it might not be worth my time. Already felt like info overload.
  • Most of the rest of chapter 17.

Exercism Review

Bob

My Solution

  • 1 - Looks cleaner than mine, though I like that I set up variables to make the code more readable. I also like my .match method better than his .search method for checking to see if the input has letters.
  • 2 - Again, I prefer my way of setting up the variables so that it's clear what everything tests. I prefer the .trim() method to testing for /\S, which I assume is whitespace.
  • 3 - I like how readable it is. It's super broken out into abstrations. It's too much though, I think the functions are unnecessary -- those can simply be saved in variables.
  • 4 - I don't think this one will work. It relies on the '!' input to return 'Whoa

Which of Sandi's rules do you feel like might be the hardest to follow—why?

The hardest for me is for controllers to only instantiate a single object, just only passing a single instance variable to a view. I often find myself sending 3 or 4 instance variables in as various models compile information for a view. Seems like that's not what Sandi recommends. Instead, it seems as though I should use presenter type objects to compile that information, and pass an instance of that presenter to the view.

Room Temperature (working title)

Pitch

Quickly check the temperature, or general tone/sentiment, of a Slack channel to gauge the morale of a given team or project group.

Problem

It's important for managers to be aware of their team's morale, but time-consuming to keep up to date on every post in a Slack channel. Often times large chunks of messages go unread, and it's easy to miss a big success or major complication.

Big O Notation

Overview

  • What is Big O Notation? What does it measure? (Time and Space, we're going to focus on time today)
  • How can we use it? (technical interviews, plus like, writing code every day)

Core Examples

  • O(1): 'Constant time'
  • O(n): 'Linear time'
  • O(n^2): 'Quadratic time'