B Manoj Kumar bmkmanoj

This is now an actual repo:

https://github.com/cowboy/jquery-tiny-pubsub

Resources for learning web design & front-end development:

ONLINE

Design

#Lessons From A JavaScript Code Review

I was recently asked to review some code for a new JavaScript application and thought I might share some of the feedback I provided as it includes a mention of JavaScript fundamentals that are always useful to bear in mind. Code reviews are possibly the single biggest thing you can do to improve the overall quality of your solutions and if you're not actively taking advantage of them, you're possibly missing out on bugs you haven't noticed being found or suggestions for improvements that could make your code better.

##Challenges & Solutions

Code reviews go hand-in-hand with maintaining strong coding standards. That said, standards don't usually prevent logical errors or misunderstandings about the quirks of a programming language. Even the most experienced developers can make these kinds of mistakes and code reviews can greatly assist with catching them.

Often the most challenging part of code reviews is actually finding an experienced developer you trust to complete

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

	if (typeof window.localStorage == 'undefined' \|\| typeof window.sessionStorage == 'undefined') (function () {

	var Storage = function (type) {
	function createCookie(name, value, days) {
	var date, expires;

	if (days) {
	date = new Date();
	date.setTime(date.getTime()+(days2460601000));
	expires = "; expires="+date.toGMTString();

	echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
	. ~/.bashrc
	mkdir ~/local
	mkdir ~/node-latest-install
	cd ~/node-latest-install
	curl http://nodejs.org/dist/node-latest.tar.gz \| tar xz --strip-components=1
	./configure --prefix=~/local
	make install # ok, fine, this step probably takes more than 30 seconds...
	curl https://www.npmjs.org/install.sh \| sh

	/**
	* Annoying.js - How to be an asshole to your users
	*
	* DO NOT EVER, EVER USE THIS.
	*
	* Copyright (c) 2011 Kilian Valkhof (kilianvalkhof.com)
	* Visit https://gist.github.com/767982 for more information and changelogs.
	* Visit http://kilianvalkhof.com/2011/javascript/annoying-js-how-to-be-an-asshole/ for the introduction and weblog
	* Check out https://gist.github.com/942745 if you want to annoy developer instead of visitors
	*

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
	Version 2, December 2004

	Copyright (C) 2011 Jed Schmidt <http://jed.is>

	Everyone is permitted to copy and distribute verbatim or modified
	copies of this license document, and changing it is allowed as long
	as the name is changed.

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE

	/*
	* Property prefix hacks
	*/

	/* IE6 only - any combination of these characters */

	_ - £ ¬ ¦

	/* IE6/7 only - any combination of these characters */

	// http://www.davidflanagan.com/javascript5/display.php?n=8-7&f=08/07.js
	// This function implements a breakpoint. It repeatedly prompts the user
	// for an expression, evaluates it with the supplied self-inspecting closure,
	// and displays the result. It is the closure that provides access to the
	// scope to be inspected, so each function must supply its own closure.
	//
	// Inspired by Steve Yen's breakpoint() function at
	// http://trimpath.com/project/wiki/TrimBreakpoint
	//