Unsurprisingly, when discussing take-home assignments for coding interviews, much of the focus is put on code. Can you code? Are you using "best practices?" What tools are you using?. There's lots of code-related things that people think about, or even stress about.
Unfortunately, non-coding tips for coding interview assignments don't get talked about nearly as much. And, in my experience, there are a lot of non-coding things we can do to put our best foot forward and impress a hiring committee with our take-home assignment.
Chapters
00:00 Teaser 00:46 Coding Gets All The Discussion 01:26 Non-Coding Tips For Takehome Assignments 01:46 Telling Your Story 02:28 A Unique Opportunity 03:06 Making A Positive First Impression 03:49 Leveraging Project Metadata 04:12 Filling Out GitHub Project Information 05:06 Include A Project README 05:59 Clearly Organize Your Project 07:01 Ensuring A Positive First Time User Experience 07:32 Make Sure Your Project Doesn't Crash 08:30 Impress With UI Polish 12:37 Use Consistent Styles & Conventions 13:52 Don't Skip The Basics 15:07 Documentation Is Key 16:12 Document Your Thought Process 17:38 Documentation Comes In Many Forms 19:46 Telling Your Story 20:59 Wrapping Up
Podden och tillhörande omslagsbild på den här sidan tillhör
Nate Ebel. Innehållet i podden är skapat av Nate Ebel och inte av,
eller tillsammans med, Poddtoppen.
