This completely removes that. I'm glad it works for you though and happy hacking!
792 karma · joined January 16, 2014
This completely removes that. I'm glad it works for you though and happy hacking!
It's interesting to see this possible view. We might be better off posting duplicates to make this nuance more obvious.
2. You are making an assumption that you aren't binding thousands of times a second. You need to take actual use case into consideration.
3. My example has a 1000:1 method call to bind ratio and it's still a significant difference in benchmarks. Yes, it's that expensive it's important to think about in critical sections of code.
I'm curious because this is what we do and I hadn't considered that we might miss some good people because of it.
function Person() {
this.age = 0;
setInterval(this.incAge, 1000, this);
}
Person.prototype.incAge = function personIncAge(that) {
that.age += 1;
};
http://jsperf.com/bind-vs-closure-vs-paramYes. I work for a large company that does recognize this and does not hire for specific stack experience. We have a hard enough time finding enough good people, regardless of specific experience, to use that as a critical factor.
I use a T440s and it is fantastic. No issues whatsoever in Mint 17.1 Mate 64-bit.
module.exports = function (arg, optionalCb) {
return promiseReturningFn(arg).nodeify(optionalCb);
};I disagree with this advice. I usually refer to this as a "Pokémon Catch" (Gotta' Catch 'Em All!). Never catch a promise that you are un-able to handle. It's better to use a Promise library that supports debugging possibly unhandled exceptions (e.g., Bluebird).
> Rookie mistake #4: using "deferred"
This one is interesting because it's actually used in the Q library documentation for a way to `denodeify` or `promisify` a function. You definitely shouldn't do this if it's already a promise, but outside of that, it's more of a gray area. I tend to recommend using libraries to convert callback functions to promises.
Of course I don't expect anyone to know the answers to all of them, but, if you've been working in Java for a decade and can't answer any nuanced questions about garbage collection in the JVM, then I start doubting either your experience or curiosity.
1. Reject the PR. It needs to be clear that this isn't acceptable. 2. Realize that stopping with rejection doesn't help the problem at all. :) 3. Start with some light comments and refactoring a couple of sections (usually it's the same bad patterns repeated). 4. Only provide the refactors as comments. Try not to fix other people's PR and then submit. It makes it hard for that person to improve. 5. Talk with the individual about it. Ask about the issues they were having and offer fixes. 6. Ask them to try again.
If this cycle happens a few times, you either need to break down tasks into simpler, smaller bites, or let them go. This can quickly turn into negative productivity for the team.
That sounds way more interesting than a scandal. Too bad it's probably a typo. :)
http://scrollsample.appspot.com/items https://news.ycombinator.com/item?id=7314965
However, this quote, "If you run a Redis server and currently use Amazon SQS or a similar message queue you might as well use this fast little replacement" is greatly over simplifying things.
Amazon SQS gives you acknowledgement guarantees that are not possible with Redis. Don't get me wrong, I love Redis, but you can't reliably trust that writes happen.
It's a very powerful and expressive language. That translates to "completely unreadable by people without at least a few months direct experience in it." If you plan on introducing people with little to no scala experience to your code base regularly you will probably want a different language or to severely limit your allowed feature set.
In my experience, unless you are building something either very large and need to worry about your gate count, or something very time sensitive and need to work about component distance, you can just program and enjoy real concurrency. :)
I'm super interested in this question because I honestly don't know. My assumption is that among serious guitar players (defined as individuals who play in groups or in front of people at least monthly) the number is almost nil.
I'm sure the number of casual guitarists (those who rarely play, but technically own one), this number is quite high.
I'm unwilling to even concede the tubes in my amp let alone the amp itself...
With little more than a cap, you can throw on a button that enables the feature on for a period of time then disables it again.