jhummel

Did you read the article?!

You are thinking about this in terms of one applicant. When you get 200 applications it's very useful to be able to quickly weed out people who are obviously not a fit.

Has anyone seen any clauses within an independent contractor agreement, which would allow the retention of certain pieces of the finished work? For instance, I write a class/component/plugin/etc. that I want to use in several projects to increase productivity. Is there a standard way to carve out and retain those pieces of code?

So, I have no idea what's going on, but just because this guy could only find these two examples, doesn't mean those are the actual reasons for him being dismissed. In fact, I'd be very surprised if that was the case.

For the record, I've seen Crockford talk... It wasn't offensive, it just wasn't very good. He seemed more interested in calling out business decisions which companies have made that he felt were stupid, than actually talking about anything related to JavaScript. Maybe that's just how his talks go and I didn't realize, but it wasn't what I was expecting.

I guess I have never had a job that counts lunch as an hour, or heard of such a job! My wife, friends, etc. all seem to do a 8-5 with breaks and a lunch hour. I guess I've technically been working 45 hours all my life if that's the case.

I started a consulting/services company a few years ago, and this year was finally in a position to start hiring. I'm a big proponent of this type of thinking, so while I couldn't offer the best salary, or the best benefits - I could offer a better work/life balance. I knew it was a win-win for us and the new employee.

We landed on a 36 hour work week. 8-5 Mon-Thurs, then 8-12 on Friday. We had more applicants than I ever dreamed of, and scored a great hire that was coming from the 70-hr-a-week startup life. Everyone's been extremely happy over the past six months, and I don't feel like I'm missing out on any productivity what-so-ever.

I don't think OP was saying that dart sucks. He was saying it was a pain to have to write his ts code in a certain way to accomodate the Dart side of things. By splitting the repo he doesn't have to worry about that anymore, just like Dart developers won't have to worry about the ts/js side.

Didn't Neal Stephenson write about this in Cryptonomicon? I never thought it was actually possible.

In JavaScript you have to contend with a dozen different run environments. Maybe you realized your fix actually broke the feature in IE8 because you left a comma at the end of an array. It's quite common to have your fix break something in a very specific environment.

We've found this out at one of my contracts. We've moved off of the typical $watch/$apply model for our directives and replaced it with a simple observable solution like Scheming (https://github.com/autoric/scheming). Our components are always watching attributes on our Scheming models, which are outside the digest cycle. It speeds things up, and is much nicer to work with IMO.

As I pointed out on twitter http://twitter.com/#!/jhummel/status/169561232045649921 it seems that the * selector doesn't apply to pseudo elements. If you're going to take this route it might be a good idea to include *, ::after, ::before { box-sizing: border-box } to make sure everything is being sized the same.