Matt Stjernholm matt-stj

When shipping code for an upcoming release, we're responsible for creating release branches (and closing previous ones) for any of the following repos with new code changes:

peak
legistarweb
chronus
atreyu

We use git flow to manage our branches around releases, so be sure to set it up and read through the docs here if you don't already have it.

Before cutting new release branches, make sure all open release/hotfix branches are closed.

From the DTR protocol, the most effective piece that I noticed was having Mod 3&4 students share their experiences of working on teams with students from newer cohorts. The role playing felt a bit forced nad unatural, but there seemed to be great value in sharing group experiences that I've had and how to producively work through them.

Web Sockets Lesson Plan

Fork this gist
Include a link to your application's repo
Your repo should have a link to your production app in the README
Git Repo
Include questions/comments for anything you'd like us to specifically give you feedback on
Would you recommend using jQuery to add elements to the DOM? I had a hard time pulling in the the library...

The websockets homework is graded on 'completion' or 'semi-completion' - but we'll try to leave you feedback on anything we see that requires feedback in the gist.

Follow this Lesson Plan
Fork this gist
Include a link to your PR in this fork

My PR

Follow this Lesson Plan
Fork this gist
Include a link to your version in the gist fork

Matt's Repo Here

Watch Recursion
Fork this gist
Answer the following questions in your fork
- Do you pronounce 'babel' in the same way?
- I do not use the word 'bobble' in place of babel.
  - Follow Up Question: Will you now?
  - If it makes me a better programmer, yes.
- What is an example of why/where you might use recursion
If you're building a binary search tree and want to add functionality where you can remove a node and rebalance the tree, recusion can be very useful. I tried to solve this problems with ~80 lines of code in multilpe loops, and found out later than ~10 lines of a recursive function could do the same thing.

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 really liked her use of a game constructor that oversaw the main functions of how the game would be played. Makes her code very clear and easy to understand. Her use of a keyboarder object and way to implement collision detection were also cleaner than what I currently have in my game, and I'll look to model mine after hers.

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

Step One: Watch Writing Testable JavaScript - Rebecca Murphey from Full Frontal 2012 (award for worst conference name ever?)

Step Two: Fork this gist.

Step Three: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded).

Did any of the responsibilities that she lists surprise you?
All of the responsibilities that Rebecca lists make sense now, but I hadn't thought to break up my Javascript that way before. In the past, I wrote code based on convenience instead of splitting them up into clearly-defined pieces. I really like the data/communication/server interactions piece, as I wasn't breaking up my code that way before.
Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?

	const MinHeap = require('min-heap')

	module.exports = class Sorter {
	constructor(logSources, printer, async = false) {
	this.heap = new MinHeap
	this.min = null
	this.logsObj = {}
	this.currentMinLog = null
	this.complete = false
	this.logSources = logSources