dhruv_xyz
You never really know what someone will do after they’re onboarded, even if they ace the interviews. When people say he’s a good engineer, they mean he crushed pair programming and skill tests. When he actually showed up, he did good work. Problem was he was juggling so many jobs he was always making excuses as to why he wasn't available. And he wasn’t upfront as to why.
We do reference checks. But when someone kills your interviews, you have to move fast or risk losing them to another offer. Time kills deals - and the best candidates usually get multiple offers. Waiting for every reference isn’t always an option. Most people are ethical, so you trade some risk for speed. In Soham’s case, one reference checked out, the other never replied. A few unaffiliated references said they remembered him from previous stops on the resume but hadn't worked with him directly.
If someone starts making excuses right away or seems off, it’s your job to cut them loose fast. Most companies did just that.
More to come, but putting it out there for feedback that can help us prioritize what's next. What would you want to build if it were near automatic?
In terms of % generated vs. % human for larger projects we take on - yes, you're right it's very dependent on the app's complexity, but for basic functionality I'd estimate 70-80% generated; we use humans for hook up around edges.
We do a lot to enforce quality and making it seem "human written" since we also have humans writing code and quality matters for making that efficient
Show HN: Autodevs – Generate simple prototypes automatically
We've been working on this for a while and just put it up on our homepage.Generate simple app prototypes using text prompts. Iterate through refinements. Turn it into a live app. Get the code. Share it with others to let them make their own version. Add a (human) dev team if it needs to be more complex.More to come, but putting it out there for feedback that can help us prioritize what's next