3 ms·

Senior devs spot red flags in junior portfolios in seconds, but we (almost) never explain them. After reviewing hundreds (thousands?) of junior developer portf

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 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 ;)

milarepa7 9mo ago
super nice ! ...but how do we get in touch for the free review ? :D
- err0r500 9mo ago
  hahaha, good catch ! Does sending a message on the linkedin page seem right ? https://www.linkedin.com/company/yourlead-dev/ https://www.linkedin.com/company/yourlead-dev/
kl3ist 9mo ago
is it the same codebase analyzed in the samples ? If so, I love how it gets destroyed in every possible way depending on the analysis context !
- err0r500 9mo ago
  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
hahahahhaah 9mo ago
Is this AI aware? E.g. I read on your examples a complaint ahout too many tests for a fast moving startup. That maybe used to be true but with AI you can go for more coverage and may be faster and more agile with it.
- err0r500 9mo ago
  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
  - hahahahhaah 9mo ago
    Yeah it is a nuanced topic. Maybe the response should be "think about..." rather than prescriptive. I have worked places where the sacred test suite slows people down to a grinding halt but it is hard politically (as in convincing 20 people with different concerns) to get that changed without being CTO yourself. But also I am thinking if tests feel "throwaway" and cheap to make then adding them is no big deal. If CI becomes too long just prune it up again.
morcus 9mo ago
It would be nice to be able to select / deselect folders in the file selector. note: I'm not a junior dev and the repo I'm trying to analyze is more of a side project than a portfolio piece. This may or may not be a feature relevant to your actual target audience.
- err0r500 9mo ago
  thank your for the feedback, you're right : I'll add that ! in the meantime you can click and drag for multiple toggle ;)
- err0r500 9mo ago
  btw, you can open a chat on the linkedin page so I can give you a cheat code to bypass the payment ;) https://www.linkedin.com/company/yourlead-dev/ https://www.linkedin.com/company/yourlead-dev/

milarepa7 9mo ago

super nice ! ...but how do we get in touch for the free review ? :D

err0r500 9mo ago
hahaha, good catch ! Does sending a message on the linkedin page seem right ? https://www.linkedin.com/company/yourlead-dev/ https://www.linkedin.com/company/yourlead-dev/

kl3ist 9mo ago

is it the same codebase analyzed in the samples ? If so, I love how it gets destroyed in every possible way depending on the analysis context !

err0r500 9mo ago
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

hahahahhaah 9mo ago

Is this AI aware? E.g. I read on your examples a complaint ahout too many tests for a fast moving startup. That maybe used to be true but with AI you can go for more coverage and may be faster and more agile with it.

err0r500 9mo ago
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
- hahahahhaah 9mo ago
  Yeah it is a nuanced topic. Maybe the response should be "think about..." rather than prescriptive. I have worked places where the sacred test suite slows people down to a grinding halt but it is hard politically (as in convincing 20 people with different concerns) to get that changed without being CTO yourself. But also I am thinking if tests feel "throwaway" and cheap to make then adding them is no big deal. If CI becomes too long just prune it up again.

morcus 9mo ago

It would be nice to be able to select / deselect folders in the file selector. note: I'm not a junior dev and the repo I'm trying to analyze is more of a side project than a portfolio piece. This may or may not be a feature relevant to your actual target audience.

err0r500 9mo ago
thank your for the feedback, you're right : I'll add that ! in the meantime you can click and drag for multiple toggle ;)
err0r500 9mo ago
btw, you can open a chat on the linkedin page so I can give you a cheat code to bypass the payment ;) https://www.linkedin.com/company/yourlead-dev/ https://www.linkedin.com/company/yourlead-dev/