121–130 of 188 posts
You were interviewed by back-end engineers. That's what they knew. My question is why didn't you leave the interview upon seeing it was a waste of time?
Earlier quoted context omitted.
Now, hold on there. These "anyone who" statements chafe me; like the junior dev who exclaimed "anyone who doesn't write unit tests shouldn't call themselves an engineer" in a meeting filled with people 15 years his senior who had collectively shipped far, far more successful software than him, without writing tests. Several years ago, I led two different front-end web teams at a large, well-known company. I wrote a l…
That's cool. But don't write JS if you don't know what this does, because it will bite you.
Earlier quoted context omitted.
Now, hold on there. These "anyone who" statements chafe me; like the junior dev who exclaimed "anyone who doesn't write unit tests shouldn't call themselves an engineer" in a meeting filled with people 15 years his senior who had collectively shipped far, far more successful software than him, without writing tests. Several years ago, I led two different front-end web teams at a large, well-known company. I wrote a l…
That's cool. But don't write JS if you don't know what this does, because it will bite you.
Earlier quoted context omitted.
I always assumed that the term "engineer" in "front-end engineer" implied software engineering capability. Although, like usual, it's dangerous to make assumptions.
In the context of software "engineering"/programming, the term engineer has been bastardized to the point of losing all meaning. To call someone who programs at all an engineer is, in my opiinion, embarrassing, especially when juxtaposed with actual engineers (e.g. mechanical, acoustical, aerospace etc.) who went through a hell of a lot more to be able to be called an engineer than a 4 year CS program. People like Jo…
Next thing we'll see front-end doctors?
I know it's a bit off-topic, but I'm a student so anything about interviews interests me a lot. For the Bacon Number question, I'm struggling a bit to get my head around a good way to do it. My immediate idea is to derive a graph where nodes are actors and an edge between 2 actors means they've been in 1 or more films together. I believe the shortest path between them and Bacon could then be found by breadth-first se…
This image from Norvig's AI may help explain it better than the wiki page: http://www.massey.ac.nz/~a159302/lesson3/fig03_17.gif
We were hiring a non-senior full-stack developer recently and I noticed there were no "frontend" questions on the list, so I added what I thought would be a question that any developer with frontend experience could answer, and would also pave the way for some more interested discussions for an advanced candidate. The question was something to the effect of "In JavaScript, what is the value of 'this' in a method?" I…
Earlier quoted context omitted.
I always assumed that the term "engineer" in "front-end engineer" implied software engineering capability. Although, like usual, it's dangerous to make assumptions.
In the context of software "engineering"/programming, the term engineer has been bastardized to the point of losing all meaning. To call someone who programs at all an engineer is, in my opiinion, embarrassing, especially when juxtaposed with actual engineers (e.g. mechanical, acoustical, aerospace etc.) who went through a hell of a lot more to be able to be called an engineer than a 4 year CS program. People like Jo…
"People like John Resig, Jeremy Ashkenas can lay claim to being software engineers..."
Hahahaha. You have got to be kidding me. A couple of 20-something JavaScript hackers who became somewhat well known by memorizing browser quirks and writing tacky, amateurish compilers? If we're going to talk about Software Engineers as compared to Aerospace Engineers, you're going to have to raise the bar quite a bit further than that. Rob Pike is a Software Engineer, Jeremy Ashkenas is the Rasmus Lerdorf of CoffeeScript.
It just goes to show, you can read and agree with hyperbole in principle, right up until the authors of it embarrass themselves by demonstrating just how low their standards are and just how unlikely they are to appreciate the substance of what they're saying.
Earlier quoted context omitted.
In the context of software "engineering"/programming, the term engineer has been bastardized to the point of losing all meaning. To call someone who programs at all an engineer is, in my opiinion, embarrassing, especially when juxtaposed with actual engineers (e.g. mechanical, acoustical, aerospace etc.) who went through a hell of a lot more to be able to be called an engineer than a 4 year CS program. People like Jo…
I think people just like to be called engineers because they think it entitles them somehow. Next thing we'll see front-end doctors?
Earlier quoted context omitted.
In the context of software "engineering"/programming, the term engineer has been bastardized to the point of losing all meaning. To call someone who programs at all an engineer is, in my opiinion, embarrassing, especially when juxtaposed with actual engineers (e.g. mechanical, acoustical, aerospace etc.) who went through a hell of a lot more to be able to be called an engineer than a 4 year CS program. People like Jo…
How about your average moron with an engineering degree like me? In Canada, there's a very strict definition for engineer. If you don't have an engineering degree from an accredited university, and a professional designation, you cannot call yourself an engineer. They take it very seriously since it's a regulated profession. Obviously everyone is free to draw their own lines (outside of Canada at least). I always tho…
100% agree. In the US I don't think it's as strict as Canada (may be wrong) but I know one has to take an FE to be called one. People in the software field, however, running around themselves engineers are more often than not, not putting any theories into practice but instead using the tools that actual software engineers (those that create software packages/tools/languages/compilers etc) make, essentially making them a journeyman of sorts.
We were hiring a non-senior full-stack developer recently and I noticed there were no "frontend" questions on the list, so I added what I thought would be a question that any developer with frontend experience could answer, and would also pave the way for some more interested discussions for an advanced candidate. The question was something to the effect of "In JavaScript, what is the value of 'this' in a method?" I…
Can I ask where (location) was this? I have trouble understanding how someone would call himself a JS developer and not knowing it. I'm not at all a JS developer (even though lately I've been knees deep in nodeJS code) and most of my experience is away from the browser, but even I knew this. I was responsible for hiring at a previous company and I did see some people passing as Senior SQL developers without knowing h…
