Recommended
Recommended
More Related Content
Similar to New developer talk culture foundry - 0519
Similar to New developer talk culture foundry - 0519 (20)
More from Dan Moore
More from Dan Moore (9)
Recently uploaded
Recently uploaded (20)
New developer talk culture foundry - 0519
- 1. 10 Things I Wish I Knew As a New Developer Dan Moore
- 2. Thank you
- 3. What I wish I’d known as a new developer
- 6. How to find a job
- 7. Been a long time for me
- 8. Only had four “real” jobs
- 9. Go to your peers
- 11. Jeff C Video
- 12. So, what do I wish I’d known
- 13. Exciting Times
- 14. So much more than slinging code
- 15. Tools
- 16. Risk
- 17. Networks
- 18. Why
- 20. Tools
- 21. Version Control
- 22. Use it
- 23. Study git
- 24. Command Line & Unix CLI Tools
- 25. Open your editor Add an alias
- 26. Write a script set –o vi Awk/sed
- 27. Editor/Debugger
- 33. Risk
- 34. Save $$
- 36. FIRE
- 37. Take risks
- 39. Startup Book
- 40. Runways
- 41. Money O/S = M(r)
- 42. Opportunity Cost
- 43. Networks
- 44. Online Network
- 45. Join a network
- 46. Participate
- 47. Work network
- 48. Join LinkedIn
- 49. Engage folks on LinkedIn Join a meetup
- 50. Why
- 53. That’s All
- 54. Not really
- 56. Where do you go from here?
- 57. Thanks to: • Culture Foundry – we do websites • Technical Integrity • You
- 58. Where to find out more: • https://letterstoanewdeveloper.com/ • Your job is not advertised (Jeff C video): https://www.youtube.com/watch?v=AqbfYxBEQyY • The deployment age: http://reactionwheel.net/2015/10/the-deployment- age.html • Oh shit git ebook: https://ohshitgit.com/ • On glue: https://noidea.dog/glue • Exercism.io (for learning): https://exercism.io/ • https://blog.ycombinator.com/why-you-should-or- should-not-work-at-a-startup-by-justin-kan/ • Hear That Lonesome Whistle Blow
- 59. Dan Moore @mooreds www.mooreds.com/weblog mooreds@culturefoundry.com linkedin.com/in/mooreds Director of Engineering www.culturefoundry.com
Editor's Notes
- The hard part of ML is not the infrastructure, it is cleaning data and building intuition.
- Level 1: use version control Level 2: read about git, understand the index, remotes, branching, rebasing
- Level 1: use version control Level 2: read about git, understand the index, remotes, branching, rebasing
- Level 1: use version control Level 2: read about git, understand the index, remotes, branching, rebasing
- Level 1: drop into the CLI to open your editor, add an alias Level 2: write a script, set the shell to use same movement keys as your editor, explore awk and sed next time you need to edit a file
- Level 1: drop into the CLI to open your editor, add an alias Level 2: write a script, set the shell to use same movement keys as your editor, explore awk and sed next time you need to edit a file
- Level 1: drop into the CLI to open your editor, add an alias Level 2: write a script, set the shell to use same movement keys as your editor, explore awk and sed next time you need to edit a file
- Level 1: settle on an editor, read the editor documentation Level 2: learn to move in your editor without the mouse. Use a debugger.
- Level 1: settle on an editor, read the editor documentation Level 2: learn to move in your editor without the mouse. Use a debugger.
- Level 1: settle on an editor, read the editor documentation Level 2: learn to move in your editor without the mouse. Use a debugger.
- Level 1: learn a different language Level 2: learn a different framework for the same language
- Level 1: learn a different language Level 2: learn a different framework for the same language
- Level 1: learn a different language Level 2: learn a different framework for the same language
- Level 1: Sign up for your 401k, pay yourself first Level 2: read MMM, think about financial independence
- Level 1: side project, open source contribution, blog Level 2: startup, book
- But be conscious of being “glue”
- Level 1: pick a network and read it for 6 months Level 2: pick a network and comment and submit for 6 months
- Level 1: pick a network and read it for 6 months Level 2: pick a network and comment and submit for 6 months
- Level 1: pick a network and read it for 6 months Level 2: pick a network and comment and submit for 6 months
- Level 1: join linkedin and keep your profile up to date Level 2: join linkedin and connect to every person you interact with at work
- Level 1: ask a senior developer on your team about the why Level 2: ask your project manager/product owner to coffee once a month