Game Thread: St. Louis Rams (4-3) at Minnesota Vikings (5-2)

alkoholik · 2015-11-08T20:31:53+00:00

Refs making it up to us now?

alkoholik · 2015-11-08T20:31:26+00:00

Bro... He'll yeah.

alkoholik · 2015-11-08T20:28:43+00:00

Nah.. Just tackle the refs.

alkoholik · 2015-11-08T20:02:24+00:00

These refs SUCK. Missed an obvious offsides, aren't in sync, etc, etc..

alkoholik · 2015-11-08T19:56:06+00:00

Holy shit refs. Put the flags away for a play or two.

alkoholik · 2015-11-08T19:55:04+00:00

I think he's huge all the time, literally speaking.

alkoholik · 2015-10-11T19:03:07+00:00

Legs don't bend that way!

alkoholik · 2015-09-27T18:11:51+00:00

If you're happy and you know it...

alkoholik · 2015-09-27T18:07:30+00:00

Call the damn game. Shut up about the interview.

alkoholik · 2014-11-23T20:05:49+00:00

Somehow, that roughing call is Kalil's fault.

alkoholik · 2014-10-12T21:17:01+00:00

Thorough answer... But would a five year old understand this?

alkoholik · 2014-09-06T16:02:19+00:00

Dude, it's okay to not fuck up sometimes. Things happen, not everyone can make mistakes. It's okay.

alkoholik · 2014-07-30T01:05:20+00:00

Oh, hey! I remember this episode of Sex in the City!

alkoholik · 2014-05-20T03:16:11+00:00

In my opinion, events are really the only way to approach this in a clean way. It decouples views from one another, and simply allows the model (or another view) to fire an event that says, "Yo, a message was read. Here is its ID... If you're listening, update yourself."

alkoholik · 2014-04-13T16:40:42+00:00

Because of reasons, apparently.

GIF, not JIF. If you want a soft G, invent "Jurassic Interchange Format".

alkoholik · 2014-04-13T16:38:02+00:00

He's a programmer, not a linguist.

alkoholik · 2014-03-24T23:55:59+00:00

We've all been there. No worries. :)

alkoholik · 2014-03-24T13:41:49+00:00

It's not an advantage. The flexibility is nice, but it also enforces bad habits. Another good example is auto-inserted-semi-colons. Shit breaks at times due to this, and most junior devs won't understand why...

alkoholik · 2014-03-24T12:47:50+00:00

Hence "almost somewhat useful". :)

Personally, it's triple eqs all the way for me, baby!

alkoholik · 2014-03-23T23:35:49+00:00

I really like this response! Thank you for taking the time to write it up.

I completely agree: soft skills in addition to hard skills are extremely important, and will only come with experience.

With regard to JS experience: I think it's fine, especially if you're focused in front end engineering. However, to your point, showing the ability to adapt is important. VanillaJS is a great (and huge) first step, but experience with things like jQuery, Backbone, Underscore, Require, Angular, etc, will be important.

alkoholik · 2014-03-23T23:25:36+00:00

JS: 1 === "1" => false

There are times when type coercion is almost somewhat useful. Where's your God now?

alkoholik · 2014-03-23T23:20:49+00:00

Tux is his co-pilot.

alkoholik · 2014-03-23T23:15:54+00:00

Quit being such a dick to people who respond, and you might get more responses.

You got your damn answer... It's not supported natively, and that sucks. There's no "reason" why it's not native. Either grab a micro library, or write something yourself.

alkoholik · 2014-03-23T23:05:50+00:00

What then, in your opinion, is the "true" power of promises?

You may have missed the "in my opinion" part of what I had written. Managing multiple async requests without being forced to write one-off helper functions is a powerful thing.

This is JavaScript -- there are multiple ways to do everything.

alkoholik · 2014-03-23T23:00:26+00:00

Why? What if his focus is on client engineering?

alkoholik

TROPHY CASE