Earlier quoted context omitted.
If you can speak to the processes involved and have demonstrable knowledge about how to implement things learned from side-projects, what's the difference between having done it at work versus personal time? None in my opinion.
> If you can speak to the processes involved and have demonstrable knowledge about how to implement things learned from side-projects As I mentioned in my comment, no difference if the person is starting out or if the project gets traction. But for experienced positions like the post author was talking about. You don't get additional signals on the developer, like did the product scale well, how was the uptime, the p…
You know my hypothesis why, because they don't have side projects. They have silo'd themselves into whatever niche project or have been on maintenance mode on a piece of software for years and never evolve. Sometimes it's not their fault, their company has pigeon-holed them into whatever software and they can't escape for whatever reason.
They should have side projects (if they care to keep learning) or lest be left behind those in more dynamic companies or those that have side projects to evolve.