Noodleface
A Mod Real Quick
Can't install ANYTHING on government machines.... which is pretty comfy once you install some plugins.
Not even custom color schemes, unless you make it.
- 1
- 1
Can't install ANYTHING on government machines.... which is pretty comfy once you install some plugins.
I understand what you're saying but htat's just not realistic.In regards to interviews, have you guys considered just pointing them to your Github account? "Check out my repos if you want to see my code", and dispense with the stupid code challenges.
Ya I mean I feel like it's standard for them to ask for your GitHub. Whether they view it or not who knows. You kinda have to play by their dumb games.In regards to interviews, have you guys considered just pointing them to your Github account? "Check out my repos if you want to see my code", and dispense with the stupid code challenges.
I forget I'm in a different industry than most of the guys in this thread. We employee full stack web developers, so interview questions revolving around algorithms and such aren't that important. For us, it's mostly about whether you have experience with a particular language + framework, and are familiar with common design patterns. We couldn't care less about white boarding a hash collision algorithm.Ya I mean I feel like it's standard for them to ask for your GitHub. Whether they view it or not who knows. You kinda have to play by their dumb games.
I forget I'm in a different industry than most of the guys in this thread. We employee full stack web developers, so interview questions revolving around algorithms and such aren't that important. For us, it's mostly about whether you have experience with a particular language + framework, and are familiar with common design patterns. We couldn't care less about white boarding a hash collision algorithm.
We're not that strict. Honestly, all the client-side frameworks follow similar concepts -- such as data binding, HTML templating, communicating with an web API, etc. We never say you HAVE to have experience with Angular, for example. If someone applied that had extensive experience with ReactJS, even though we use Angular, that would be fine since both, conceptually, are very similar.Yeah but that strategy has its own pitfalls and retardation. There are so many tools out there for any conceivable purpose. Lots of them are put into the workflow at any given company. It is outright impossible to have encountered and used all of them. One of my friends here wasn't taken on for a senior performance engineering role just because he was not familiar with their monitoring platform. Although he had a ton of experience with three other similar platforms.
I forget I'm in a different industry than most of the guys in this thread. We employee full stack web developers, so interview questions revolving around algorithms and such aren't that important. For us, it's mostly about whether you have experience with a particular language + framework, and are familiar with common design patterns. We couldn't care less about white boarding a hash collision algorithm.
All I'm saying is, we're not white boarding algorithms during our development. So it's not something we focus on during an interview.Full Stack without understanding algorithms? You must be hiring low end people with broad shallow knowledge.
){:|: & };:I just remembered my (not) favorite interview question
Write down your most impressive Linux command
We have code blocks here I think?){:|: & };:
Stupid smiley face, fml
can you do an implementation of the hanoi algorithm on a white board.Not even a tree traversal or reverse a linked list?
If someone threw me something like a towers of hanoi I'd be a little offended. "I've worked for 7 years and you want me to solve a dumbass puzzle.."