Justin Lowery cerebrl

Debugging & Profiling Node.js - Moved! Click here to be redirected to the new location.

Couldn't find the text of this for a while...

Original (404'ed) -- https://plus.google.com/115094562986465477143/posts/Di6RwCNKCrf
Fakeout -- http://www.dzone.com/links/rss/ryan_dahl_i_hate_almost_all_software.html
Repost -- https://plus.google.com/116904230181415286707/posts/DnAMAN5sUR8

I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.

From Require.js - Why AMD:

The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"

I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.

I have a list of components that are dynamically bound to a parent region via region.components. This is an array that is rendered via ng-repeat. Since they are polymorphic and arbitrary, but all share the same base, I've created a base component directive. However, I want to hook (by component id) a directive up to the same component item. Since the property is dynamically evaluated the second directive never hooks into it.

First attempt:

CSS Layout Debugger

A tweet-sized debugger for visualizing your CSS layouts. Outlines every DOM element on your page a random (valid) CSS hex color.

One-line version to paste in your DevTools

Use $$ if your browser aliases it:

~ 108 byte version

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

	// An object with a property and a method.
	var obj = {
	name: "Ben",
	logName: function() {
	console.log(this.name);
	}
	};

	// And another global variable, for good measure.
	var name = "Whoops";

	<!doctype html>
	<html ng-app="Demo" ng-controller="AppController">
	<head>
	<meta charset="utf-8" />

	<title>
	Logging Client-Side Errors With AngularJS And Stacktrace.js
	</title>

	<style type="text/css">

	// DISCLAIMER: This is not necessarily good code. It’s just code that I wrote
	// as quickly as possible to do each task.

	// 1

	return 2*i;

	// 2

	return !(i%2);

	- my normal flow?
	- good commit messages ******
	- searching commit messages (group by keywords)
	- searching code *
	- working with history (viewing, time traveling)
	- rebasing (for pulling & squashing, splitting a commit) *

	- undoing local commits (soft, hard reset)
	- forgot to add / change message (amend)
	- LOST commits? *