thinking! ❖ Blogging is a great practice and helps you build community awareness! ❖ It’s not something many people do! ❖ Include at least two substantial posts in your portfolio! ❖ Proofreed. Better, ﬁnd yourself an accommodating editor! ❖ But, this is about writing code…
stand behind is better than no code! ❖ Many applicants provide no code samples at all(!)! ❖ But, not everything! ❖ One or two complete or near complete projects representing recent work are likely sufﬁcient! ❖ Direct attention to ﬁles or methods you want to highlight
“go bag” for your career! ❖ Start now, iterate and reﬁne before you need it! ❖ Key promotion opportunity! ❖ End-of-year reviews! ❖ Job opportunity at a dream company! ❖ Treat it as a personal kanban project! ❖ Start tonight!
❖ More opportunity to work on pure-Ruby, challenging your understanding of the language vs. a framework! ❖ You’re learning and expressing your own opinions! ❖ Gems can be published to RubyGems or just to a repository and then installed locally! ❖ You can ship a CLI application as a gem
you genuinely believe would be useful to others, publish to RubyGems! ❖ If you’re just building “practice” code in gem format, I recommend keeping the gem in a Git repository and sharing the repository link or a tarball
you understand in full or most of! ❖ Host it where others can see it! ❖ GitHub! ❖ BitBucket! ❖ DIY GitLab! ❖ For the portfolio itself, up to you, but static sites with Jekyll or MiddleMan are nice! ❖ GitHub pages
your control, but keep it sustainable against other interests and commitments! ❖ Aim for two, two-hour sessions per week! ❖ Build a habit! ❖ Aim to complete an initial iteration in six to eight weeks (24 to 32 hours)! ❖ Take a break, iterate again