Hacker News Reader

Exactly. FTA:

> Most of the "frontend work" I saw was via Rails ERB templates [puke emoji].

Okay, so ridiculous stack/language bias aside, he's doing frontend, but it's not the frontend he wants. He wants to be writing JavaScript. Which is fine, but he's implying Shopify messed up when it seems he just didn't have a clear understanding of what the role entailed and what the tech was he'd be working with.

View on HN

The puke emoji was especially unwarranted. Templating engines are templating engines.

Oh but you don't understand. This wasn't released within the last 30 days, therefore it's legacy and bad.

I don't know why but honestly I'd expect something a little more reasonable from someone coming from academia, but in the broader context of the piece as a whole it makes perfect sense.

> he's implying Shopify messed up when it seems he just didn't have a clear understanding of what the role entailed and what the tech was he'd be working with.

It seems extremely improbable to me that at no point in the hiring process, starting from the job advertisement on down, was this ever stated.

This can happen (speaking from personal experience). For a big/growing company you're interviewing for a position that's open in several teams which all can have different stacks. Which team you end up with depends on some internal priority.

Reply on news.ycombinator.com