Fullstack Motherfucker

About me, becoming a fullstack developer, and what it takes

Transcript

1. Fullstack Motherfucker Ran Tavory @rantav @reversim
2. About Me On average day I deal with:
3. About Me On average day I deal with:
4. About Me On average day I deal with:
5. About Me On average day I deal with:
6. About Me On average day I deal with:
7. About Me On average day I deal with:
8. And I like it! L I K E
9. What am I? W H A T
10. FullStacker! F U L L
11. What does it take?
12. How to become a Fullstacker?
13. Grow into it. It takes time!!!
14. Do one thing thoroughly
15. Do one thing thoroughly
16. Do one thing thoroughly
17. Do something less thorough
18. Do something less thorough
19. Do something less thorough
20. OOB Projects
21. Move your cheese
22. And finally Realize • You can be an expert at one field or two. • Maybe three. • But you cannot be an expert in all. • Accept it
23. Things I like • Understanding the whole picture • Shipping • Code • Products that work • Getting recognized for my work
24. Things I dislike • Throwing code at someone else to run it • Having heard from someone else that • Hey dude, your code just fucked up • Push and run out
25. Conclusion • I just had to be a fullstacker
26. My story
27. My story • Started as desktop dev in low-tech
28. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS)
29. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript)
30. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript) • Then web frontend at a startup (prototype.js)
31. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript) • Then web frontend at a startup (prototype.js) • Then web frontend at google. (Closure JS)
32. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript) • Then web frontend at a startup (prototype.js) • Then web frontend at google. (Closure JS) • Then backend at google
33. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript) • Then web frontend at a startup (prototype.js) • Then web frontend at google. (Closure JS) • Then backend at google • Then backend at outbrain.
34. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript) • Then web frontend at a startup (prototype.js) • Then web frontend at google. (Closure JS) • Then backend at google • Then backend at outbrain. • Then frontend at outbrain (Jquery, ext)
35. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript) • Then web frontend at a startup (prototype.js) • Then web frontend at google. (Closure JS) • Then backend at google • Then backend at outbrain. • Then frontend at outbrain (Jquery, ext) • Then infrastructure at outbrain
36. My story • Started as desktop dev in low-tech • Then web dev in a startup (Cache-Script and JS) • Then security at Microsoft (JScript) • Then web frontend at a startup (prototype.js) • Then web frontend at google. (Closure JS) • Then backend at google • Then backend at outbrain. • Then frontend at outbrain (Jquery, ext) • Then infrastructure at outbrain • Then infrastructure. And dev. All sorts. In many other companies...
37. T o d a y What I do Today
38. T o d a y What I do Today
39. What are you? Y O U
40. What are you? • Are you a Raccoon? Y O U
41. What are you? • Or a Koala? • Are you a Raccoon? Y O U
42. P l u g Shameless Plug summit2014.reversim.com Feb 24-25