An introduction to blogging and why we do it

• Show technical knowledge
• For you (the student); For your peers; For community; For employers
• Build community
• Build credibility
• Track progress
• Make contributions to others’ development, even as an early developer

Tracy Lum maintained a technical blog while she was a student and TA at Flatiron. When Tracy applied to be a developer at Rent the Runway, her future employers checked out her awesome blog and were like, 'Wow--awesome blog! No need to give her a code challenge; Let's hire this way smart person!!'

• A student from 062617 had their blog post picked up by a Medium publication.
• A student from 0217 had received a job offer from an employer who found him through his blog.

• Write a blog once per module and present it on your scheduled day
• The topic of your post can be something we've covered in class or a technical topic not covered in class
• The blog post should be written on your own time outside of class.
• Use whichever platform you prefer: Medium, Wordpress, Jekyll
• The presentation will be less than 5 minutes with followup questions from your classmates

• A bug you ran into
• A new package, feature, or update
• How-to guides
• How-I-made-this
• Deep dives on topics you’re currently studying

• Spelling and grammar check!
• Test your code in console before publishing
• Cite your sources
• Include quotes
• Include code snippets
• Include gifs

• Anything not related to programming

• Plagiarize = expelled
• Put out code without testing it first
• Present on a topic you actually haven’t studied
• Include offensive material (kid- and grandparent-proof)
• Spend more than 5 minutes presenting
• Read your blog out. Loud. Word. For. Word.

Okay, you're ready! Go forth and blog.