jessegavin

Don't right-click on the input and inspect element

this! So fun to play with. Love that you can edit and reposition the strings.

Wonderful!

I _REALLY_ enjoyed reading this. Great story. Please write more stuff GrumpyOldDev!

NEAT is not focused on lie detection, truth detection, or assessing someone’s credibility but, rather, on aggregating preconscious brain signals to determine what someone believes to be true.

How is this NOT a lie detector?

This would definitely be useful when interrogating someone right?

So basically Zulip > Slack because it has nested channels?

Use a <tfoot> element (unless you're actually trying to show a sub-total of just the page you're looking at).

I have used knockout, angular, react for a while. When I used vue.js the first time, I smiled. It made me happy.

me three

This is really cool. Very intuitive. Very well executed in my opinion. I had trouble drawing walls though. Couldn't get it to work at all.

People still use Underscore?

I disagree. I spent nearly a year as a UI designer/engineer for a flight search/booking tool and evaluated all the major interfaces. The #1 killer feature google flights has which kills all other flight search tools (I have seen) is speed. They bought a company (ITA) for something close to a billion dollars which provides near realtime search results for flights.

Kayak (and others) do a good job of streaming search results, but you still have to wait seconds before you're able to make decisions.

I interviewed for a role on the website UI team in spring of 2013. I thought the interview process was one of the best I have experienced. My would-be manager initially reached out to me (not a recruiter) and we had a few nice phone conversations about what they were looking for. They flew me out for a two day interview. If they know it isn't a fit on the first day, they don't have you come back for the second.

I met with 3 developers, a hiring specialist and a development manager on the first day and they asked very domain-relevant questions within my area of expertise. No silly programmer brain teasers. I had plenty of time to ask questions of my own.

On day two I met with non-developers. Business, designers/UX, etc. I was able to get a very good idea of the people I would be working with and the types of problems I would be solving.

I ended up deciding to take another offer, but it was a very positive experience overall. I didn't encounter any jerks like some others have.

Very few R.E.M. albums? Sign me up!

Yeah, I was wondering how you drain/clean the desk from time to time. Could get very stinky and gross.

However, I LOVE the idea of working in a mini forest.

I'd buy it.

I think this is an excellent perspective that deserves broad consideration.

It would be super helpful to see a video of how the game is played. I am very interested in this project though.

Azure had this implemented and available a while ago actually. The "General Availability Release" happened 5 days ago.

You did a good job using Bootstrap. ;)

Was just about to write the same thing.

If you have a subscription (or don't mind spending money), the TekPub series on AngularJS is very good. http://tekpub.com/productions/angular

I got nauseous!

Very smart to link to jobs available via external sources too. Good luck!

I LOVE the points made in this post. I would two other observations:

1) Make sure your app has lightening fast response for touch events. Kids are smart, they expect that when they click a button, something should happen. If it takes over 250ms, my kid thinks it's broke and will start clicking it repeatedly.

2) Always use "onTouchDown" instead of "onTouchUp" when handling simple presses. My kid doesn't always release his finger after touching a button and when nothing happens, he thinks he needs to touch the button repeatedly. If the developers targeted the "Touch Down" event instead of "Touch Up" my kid wouldn't have learned this behavior.

My company uses JIRA (with Balsamiq integration) and it rocks! I am so glad to have this implemented on the UX.SE site. Thanks.

It makes sense if you're trying to stick with the window.location.search convention. https://developer.mozilla.org/en/DOM/window.location#section...

That's exactly my point. In order for me to want to use Dwolla (and pay the $3 set up) I would have to believe that enough merchants out there will let me pay with Dwolla that I would get some unique benefit for using it.

Dwolla is awesome for merchants and neutral for consumers.

I can't think of any reason a consumer would benefit from this over a credit or debit card. Except maybe if they regularly overdraft and prefer a $5 fee to whatever their bank charges.

I completely agree, especially for a wrist watch startup.