Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
They wanted to know how you'd go about solving X, but you didn't do it. Instead you focused on tests and other "production-grade" aspects that don't matter jack shit since nobody will ever touch that project after the interview is over.
The only thing you've proven is that you like to overengineer simple tasks, and that you prioritise "nice-to-have" features over what you were asked to do. The only companies that would hire you with that attitude are start-ups with too much money. -
Showing a knowledge of how to write a code that is easily extendable and testable is not nice to have, it is a must if anybody has any knowledge.
Showing somebody how to do X while somebody else is focusing on another stuff that IMO should be there is fixable. It's another interview with small pointers to see if the person understands.
That's why we have code reviews. It's one comment and 1 line changed.
Why it's 1 line change? Because everything is extendable, I made it like that for a reason.
Oh I didn't mention that the main X is already solved, they are just finding other stuff that is not the primary focus
Hiring process is fucking broken ok?
We all do have something else to do, nobody wants to do "homework" for 4 fucking hours. Which let's be real, isn't 4 hours. It's always more. I try to squeeze it in a least amount of time which means mistakes will be made. I always try to show my knowledge of the language and it's features. But, you didn't do X. That's it, that is a no from us.
Dude, I just wrote a high production grade small project with 90%+ test coverage and you are telling me that those 2 small shit I made is a big deal? Fuck off
Most companies I worked with have a code full of shit and here I present to you, with a poetry and it's a no because of X?
My bet is that if I ever started to work there I would find a code that isn't tested and is in shit state
\rant
rant
job work hiring