ok, I updated a few things. thanks for your feedback :
- a clear link in the landing to claim for a free review
- add that it's useful to review portfolio but also take home assignments and side projects.
I must confess that it analyzes the repos "the old way"... and I never agreed that too many tests are a problem anyways (too many bad tests are, ok) but I heard it from colleagues quite a lot when working in startups and that's what a candidate is likely to hear too
yeah, that's often the case it always felt important to me (but I can't say I never "mishired")
btw, I don't advertise it but junior devs can also use the tool for take home assignments (not sure if it would be a good or a bad thing as a recruiter)
I totally agree, and even if the results here can’t be perfect I developed the approach more by the way dev is approached in different context (I never really realized it before reading Simon Wardley book)
hehehe, yes that's the same one ;)
I must say I found it really cool too from the "super over-engineered" review in the startup context to "we can't imagine shipping such a hacky code" in regulated company context :D
Senior devs spot red flags in junior portfolios in seconds, but we (almost) never explain them.
After reviewing hundreds (thousands?) of junior developer portfolios, I realized two things:
Junior devs do their best but don’t know the red flags senior developers spot immediately
Nobody tells them
So I built https://yourlead.dev to automate myself : it analyzes GitHub repositories and:
- flags the issues a lead developer would raise during a real code review
- explains why they matter
- gives concrete tips on how to fix them
- and even helps prepare for technical interviews
I spent a lot of time fine-tuning it based on my experience across different contexts (because expectations are very different in an early startup, a scale-up, or a bank).
btw, I'm giving free reviews in exchange for feedback ;)