Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Full Stack Engineering - April 29th, 2014 @ Full Stack Engineering Meetup NYC

432 views

Published on

Discussing the nature of Full Stack Engineering practices and standards at Huge. This presentation is focused on web engineers at all points of the spectrum. From seasoned developers through to new comers. Hopefully this provides some interesting insights into how to manage many stacks in an agency world.

Published in: Internet, Technology
  • Be the first to comment

Full Stack Engineering - April 29th, 2014 @ Full Stack Engineering Meetup NYC

  1. 1. April 29, 2014 Full Stack Engineering 45 Main St #220 BKLN / 718 625 4843 / hugeinc.com
  2. 2. Full Stack Engineering. @ MeetUp! April 29, 2014
  3. 3. 1. Huge & Me. 2. Things I’ve noticed. 3.Acronyms Don’t Matter. 4. Choosing Tools. 5. HugeBrewsApp. Agenda
  4. 4. Huge.
  5. 5. We make stuff...
  6. 6. We build Huge TV’s...
  7. 7. And we brew beer…
  8. 8. Karl Stanton, Director Front-End Engineering Australian, started coding in early 90’s, have been a full stack developer since early 2000’s @karlstanton
  9. 9. (Photo credit: Ovidiu Ocnaru) This is how I feel…
  10. 10. Things I’ve noticed.
  11. 11. Some things I have noticed over the past few years: 1. There will soon be no “sides”. 2. Server-side JavaScript is paving the way. 3. JSON is the dominant data format. 4. DevOps is not a career, it is a skill.
  12. 12. Some things I have noticed over the past few years: 1. There will soon be no “sides”. 2. Server-side JavaScript is paving the way. 3. JSON is the dominant data format. 4. DevOps is not a career, it is a skill.
  13. 13. Some things I have noticed over the past few years: 1. There will soon be no “sides”. 2. Server-side JavaScript is paving the way. 3. JSON is the dominant data format. 4. DevOps is not a career, it is a skill.
  14. 14. Some things I have noticed over the past few years: 1. There will soon be no “sides”. 2. Server-side JavaScript is paving the way. 3. JSON is the dominant data format. 4. DevOps is not a career, it is a skill.
  15. 15. 15 Atypical interview question: It’s the world cup. Architect a single page application that shows the top most tweets with the hashtag #GER & #BRZ
  16. 16. There’s no such thing as: “that’s not my job”.
  17. 17. 17 Don’t be a letter in an acronym…
  18. 18. Acronyms don’t matter.
  19. 19. Process does. Acronyms don’t matter:
  20. 20. Each stack at Huge must: 1. Have a standard. 2. Contain unit tests. 3. Be deployable at any time. 4. Be reusable. 5. Be automated.
  21. 21. Each stack at Huge must: 1. Have a standard. 2. Contain unit tests. 3. Be deployable at any time. 4. Be reusable. 5. Be automated.
  22. 22. Each stack at Huge must: 1. Have a standard. 2. Contain unit tests. 3. Be deployable at any time. 4. Be reusable. 5. Be automated.
  23. 23. Each stack at Huge must: 1. Have a standard. 2. Contain unit tests. 3. Be deployable at any time. 4. Be reusable. 5. Be automated.
  24. 24. Each stack at Huge must: 1. Have a standard. 2. Contain unit tests. 3. Be deployable at any time. 4. Be reusable. 5. Be automated.
  25. 25. Choosing Tools.
  26. 26. Learningisthepoint(andchallenge). ChoosingTools:
  27. 27. Understandhowthingswork. ChoosingTools:
  28. 28. Identifyyourgapsearly. ChoosingTools:
  29. 29. Prototypeyourwaytovictory. ChoosingTools:
  30. 30. (Photo credit: Ovidiu Ocnaru) Remember this?
  31. 31. Client Express NodeJS Client JavaScript .NET/HTML SiteCore 7.0 JavaScript Linux Prototyping Stack vs. Development Stack Windows * JavaScript including jQuery Compass CSS CSS HugeInc.com Hogan/HTML Compass
  32. 32. Client Express NodeJS Client JavaScript .NET/HTML SiteCore 7.0 JavaScript Linux Prototyping Stack vs. Production Stack Windows * JavaScript including jQuery Compass CSS CSS HugeInc.com Hogan/HTML delivery1 author1 delivery2 Compass
  33. 33. Demo.
  34. 34. HugeBrews Demo:
  35. 35. 35 Objectives. • Collect beer rating data in Google docs • Check each rating into Untappd API • Store reference of beer data in local database • Display results
  36. 36. Client PHP/HTML Apache MongoDB Client Express NodeJS Mongoose MongoDB JavaScript Linux Prototyping Stack vs Production Stack Linux * JavaScript including jQuery Hogan/HTML HugeBrews Backbone Bootstrap
  37. 37. Questions?

×