upvote
He's got 15 years of real experience shipping features in companies. What's a toy project really going to do? Especially when build something is mostly unrelated to the skill set you get hired for. A usable thing needs a ton of time spent on things like ui and design when someone else with that speciality would do that.

I'm in a similar situation, no one asks about my toy projects

We're also asked to lie. You ever apply to a b2b finance company and get asked why you want to work here or what the company stands out to you.

reply
Maybe lots of HN folks work at companies where everyone is actually working hard on challenging things and learning, but many people know that someone building things on their own time that you can look at is a much stronger signal of their competence than that they were employed.

So many employees are bad, and often all you have to go on is the employee’s word that they did good and their verified dates of employment.

reply
No i don't think most people are working on anything technically challenging. Interviews don't even check for that. You go through a toy system design challenge and coding challenges. that's the extent of real technical knowledge needed. Interviews then ask about problems in the workplace, how you influence, how you plan and ship projects. None of that is challenging or requires learning.
reply
>What's a toy project really going to do?

Who said anything about building a toy project?

Build something real.

reply
Once you work in a real corporation anything you build solo is a toy. My experience is working on systems handling 100m qps, anything solo is a toy compared to anything I've done. There's no interesting technical decisions because they're all inconsequential at solo developer size.
reply