Timeline for How to add a small project contribution to my resume
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 2, 2020 at 21:00 | history | tweeted | twitter.com/StackWorkplace/status/1212841156335288320 | ||
| Jan 2, 2020 at 16:47 | comment | added | Matt Webber | @MatthewGaiser Definitely for a developer / IT engineer gig. Something where technical creativity / resourcefulness would be a valued asset. | |
| Jan 2, 2020 at 16:46 | comment | added | Matt Webber | @iLuvLogix I completely agree. I definitely meant to say "brag about" my code rather than use it explicity (which the accepted answer provided clarity to my question and set me straight on). Your suggestion to link GitHub in my resume is something I've done in the past and that may better accomplish the end I was looking for rather than using a bullet point. Thank you for your time. | |
| Jan 2, 2020 at 16:42 | vote | accept | Matt Webber | ||
| Jan 2, 2020 at 16:21 | answer | added | O. Jones | timeline score: 1 | |
| Jan 2, 2020 at 15:51 | comment | added | iLuvLogix | Personally I wouldn't add just a code snippet to my resume.. First it belongs most-likely to the company you previously worked for, second it's just unrelevant if you don't explain the project as a whole and the part your snippet plays in the whole orchestra. Solid projects on GitHub might look better than just a snippet containing a couple of lines (even 60).. | |
| Jan 2, 2020 at 15:49 | comment | added | Matthew Gaiser | What do you want to obtain by adding this to your resume? A developer job? Proof of a side skill? Proof of initiative? | |
| Jan 2, 2020 at 15:45 | review | First posts | |||
| Jan 2, 2020 at 18:57 | |||||
| Jan 2, 2020 at 15:44 | history | asked | Matt Webber | CC BY-SA 4.0 |