Amazon recruits from all over. If you just do a phone call with them and then pass the tech phone screen they'd pay to fly you out. I don't think an in person interview with a recruiter is a win at all.

Let?s say you fly in and then miss the interview because you?re sick. Do they still reimburse you?

I don't have a traditional CS degree which I think is probably leading me to getting automatically rejected for a non-insignificant amount of roles. This is probably even more true for the big tech companies (Amazon, Microsoft, etc) so any time I can get an interview at those kinds of places is a win for me.

If we are going to play a game of what-if's then we might be here for a while.

Maybe I'm way more trusting than y'all, or maybe the industry is way more cutthroat than I think. Given, I've only been in a position to get reimbursed for an interview twice, but, it never occurred to me they wouldn't pay. And they did, both times.

Suzzer, step away from the stack overflow. Forget it, it's chinatown.

Sorry I wasn't trying to make light of getting an interview with Amazon. I was just saying that I don't think an interview with their recruiter in person is much better than over the phone.

I just submit multiple times if I know it was a simple bug or the solution is simple enough that I know I covered edge cases. I don't care about my score or rep. Also I subscribed to premium and enjoying the much faster judge times

A valid question. Is there a better solution than going Select 1?

Just finished my 2nd technical interview w/ what I assume is the UI manager @ Oracle Cloud Infrastructure team [couldn't find him on LinkedIn]. Listening to all their processes, workflow, etc they have setup and comparing it to what Kochava has makes me super jelly. He sheepishly admitted to one bad merge in a year. One! If UI team @ Kochava had only one bad merge in a month they'd be kicking serious ass.

I'm about to write a small SPA backed by Node. Any reason I shouldn't pick Vue? I have experience with Angular but not React. Like the look of Vue quite a bit.

I love Vue, no reason to not give it a shot and make your own opinion. Some day I will give Angular a fair shake

I'm not a fan of the way React mixes js and html together. Angular seems to have a nasty reputation for completely breaking between major releases. Explaining to management that you have to spend resources to rewrite your app if you want to use the latest version of Angular isn't really the sort of thing that goes over well. Vue is the winner for me.

Also, the UI team I was on started out in knockout. Between Vue and React, Vue was a much more natural transition based on what we had grown accustomed to doing.

Yeah I like the fact that Vue isn't all-or-nothing, so you can gradually convert a codebase over. That doesn't matter to me right now, but makes it a better tool generally. I think both other major frameworks have issues with this (Angular because it's so opinionated, React because it doesn't allow HTML templates).

What do you mean by react doesn't allow HTML templates?

JSX is not HTML, and it's use is not required.

hot front end takes ITT today.

Well like I said I have no experience with React, but my understanding is it wants you to do everything with JSX and render methods. I know it will accept static HTML, but there's no like ng-if equivalent, if you follow.

Sick gotcha, but in reality JSX is mutant HTML being jammed into my script and the use of JSX is very strongly encouraged if not required.

I'm a newb, but JSX is more javascript pretending to be html than really html in javascript. There's plenty of space for regular html outside of the <div id="root"></div> or whatever tag.

I liked React (JSX and all) more than Angular, come at me

Fundamentally if web pages are going to be mostly dynamic one-page client side apps that render any kind of components or sections of pages separately it's going to be nearly impossible to separate HTML from javascript. I think.

I prefer the old days idea of servers doing the work and spitting out super simple flat pages that load virtually instantly. But, I had a convo about this with a friend in IT who feels the same way personally, but we talked about his kids who are 10-14 and they will not abide new pages loading even if it is barely noticeable. I don't remember the hardware exactly, but between kindle and some other reader they could not stand to use one of them because it loads a new page instead of fluidly moving from one to another - and that's on a local app that will be almost instantaneous.

Dumb question from someone who's done precisely one interview in the last ten years: what do people wear on interviews these days? Does it matter as long as you don't look like a slob?

I've been ridiculed for wearing a suit. Most people seem to do business casual.

I really haven't been interviewed in a long time, but I'm sure there's a big difference here between industry/employer and East vs. West Coast.

IMO 1 increment above what you wear on the job is solid - unless it's already a suit job.

Based on all the interviews I just went on - I think my Bonobo pants/dress shoes/button down shirt was a little stodgy. But if you look young it probably won't matter.

If I had it to do over I'd wear some nice skinny-ish jeans (not drop waist stupid - just nice tapered lower leg), dressy sneakers and a button down shirt. Sneakers is key - find something nice that pops a little.

Angular4lyf. lol at that react crap.