tchocky · HackerTrans

قبل 3 سنواتdiscuss

Yes, I am completely with you. I always hated these arbitrary algorithm tasks that have nothing to do with the actual job. With the experience of hosting multiple job interviews I prefer to do a task that is close to the job, but keep it open enough for the applicant to do it their way. And making sure to the applicant that asking questions is desired. If they go in a wrong direction without asking questions, it's a good sign. If they ask good questions it's a strong plus point. Also I can see if they can apply learned knowledge quickly.

Why should I do algorithm or math related tasks as a frontend developer for example. Soft skills are way more important than preparing for potential interview questions.

tchocky

قبل 3 سنواتdiscuss

Yeah, Europe is different here, as we have social security from the state. In Germany you get continued pay by your health insurance (a certain percentage of your usual salary). It's far easier to do things like this when the state helps you with this.

tchocky

قبل 3 سنواتdiscuss

It's not the same as tuples and records. You can do the following with them:

  const first = #{a: 'b', c: 'd'};
  const second = #{a: 'b', c: 'd'};
  first === second // true

So no more deep comparing of objects if they have the same properties.

comments