Funnily enough, I was recruiting for a Python/Flask engineer not long ago. The best applicant didn't have side projects, but had a blog with over 150 articles o

Funnily enough, I was recruiting for a Python/Flask engineer not long ago. The best applicant didn't have side projects, but had a blog with over 150 articles on Python and Flask. He was rejected because they couldn't afford him. I've written about side projects, and two best ideas are usually: - Contribute to open source. I would contribute to the Flask project if that's what you want to use professionally. Either improve the framework directly, or write a useful extension. - Make something that people will use, and preferably makes you money. People want to see evidence of production quality, not hobby projects. If that means shrinking the scope, do it.