997 karma · joined March 16, 2011
The reason I wrote my jobs in Resque? Confidence. If shit will break - it will be on my side, not inside a package required by another package somewhere deep inside node_modules. I'm reading the source of almost every node package I use. I check all the issues on GitHub before trying to play with it.
While node core is stable, and everything is so damn fast (thanks Redis) and I enjoy every minute of developing with this stack, I find myself too many times inventing the wheel all over again - instead of focusing on my product.
1. require('sys') throws, use require('util') now. The "sys" module was deprecated in node v0.4.
2.cluster.fork() no longer return a child_process.fork() object use cluster.fork().process to get the object.
3.the 'death' event on the cluster object is renamed to 'exit'
coffee> chute = require 'chute' [Function: Chute] coffee> "tristan".width(5) 'tristan/w/5'
They should do project estimation instead of Security Analysis.
https://gist.github.com/2692091
This fixes part of the problem, but what happens when you reference './models/user.js' from the file 'auth.js' but then auth grows in size and you decide to divide it and put it in auth/facebook.js, auth/twitter.js, etc. -- well, now you are fucked.
Say you would want to write a mixin for a better border radius, you'll have to call your variables MozBorderRadiusBottomleft and borderTopLeftRadius. Clearly not a good style. Why? Because it's just a simple regex: key.replace /[A-Z]/g, (s) -> '-' + s.toLowerCase()
That's why I'm afraid of uploading half baked projects to Github. Though so far, even my fully baked projects didn't get any attention.
No I don't want to go back.
So basically every focus on the element creates a new datepicker. If you're not careful this could mean memory bloat and unpredictable behavior as the plugin is attached several times.
And he has a point. While I dislike the whole "lean startup" thing a lot of people promote and adore it. And along Learn, Measure, Adapt, Innovate and other big words, I don't see a Secure your Damn App section.
When I write my controllers I can't focus completely on my product - I also have to think if this mass assignment is vulnerable.
This is from a book called "Nginx HTTP server":
1. Replace the old Nginx binary (by default, /usr/local/nginx/sbin/nginx) with the new one.
2. Find the pid of the Nginx master process, for example, with ps x | grep nginx | grep master or by looking at the value found in the pid file.
3. Send a USR2 (12) signal to the master process—kill –USR2 , replacing with the pid found in step 2. This will initiate the upgrade by renaming the old .pid file and running the new binary.
4. Send a WINCH (28) signal to the old master process—kill –WINCH , replacing with the pid found in step 2. This will engage a graceful shutdown of the old worker processes.
5. Make sure that all the old worker processes are terminated, and then send a QUIT signal to the old master process—kill –QUIT , replacing with the pid found in step 2.
I was first employee in a start up before I even finished high school. A real start up, with backing from a top VC and an amazing founding team.
On the interview I looked eager to start getting shit done. I was super enthusiastic, asked hard questions, trash talked technologies - I looked like I actually knew what I was doing!
Then I went home and started to learn all those three letter acronyms they talked about.
You have to check that people can actually code. I'm not talking about algorithms, I'm talking about string truncation, url shortening service, time_ago_in_words - some programmers do know how to oversell themselves.
Source: http://translate.google.com/translate?hl=en&sl=auto&...