2 ms·
1. Clean resume. Programming is 100% communication, both with yourself and others. If your resume doesn't communicate well, you probably don't code/design very
by muzani 6y ago
1. Clean resume. Programming is 100% communication, both with yourself and others. If your resume doesn't communicate well, you probably don't code/design very well. Emphasize important parts, and it matters what exactly about yourself you're emphasizing, and that you don't follow a "default" template.
2. Seniority. It's said that a person's second project will be their worst, overengineered and bound to fail. Someone who has done three projects can solo. Any less needs a mentor who has done at least three projects. Someone who's working on their first production project will underengineer it, but that's fixable by bringing a senior in later. There are people who have years of experience but never the opportunity to do a project from scratch - these will still go through those phases.
3. Fill in gaps. If they're a break, why? Many people are embarrassed of gaps, because they're a phase of experimentation and failure. But if you've taken a couple years off to become a monk or try a startup, say so. Dealing with burnout says a lot about your experience and how tough you've grown too.