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.

Inclusive Architecture - Introducing the PAMstack - [Refactr.tech]

661 views

Published on

Introducing a new framework for building sustainable development teams - the PAMstack focuses on process, abstractions, and mentorship.

Published in: Technology
  • This sounds pretty innovative, and will look through now!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • DOWNLOAD FULL BOOKS, INTO AVAILABLE FORMAT ......................................................................................................................... ......................................................................................................................... 1.DOWNLOAD FULL. PDF EBOOK here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. EPUB Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. doc Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. PDF EBOOK here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. EPUB Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. doc Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... ......................................................................................................................... ......................................................................................................................... .............. Browse by Genre Available eBooks ......................................................................................................................... Art, Biography, Business, Chick Lit, Children's, Christian, Classics, Comics, Contemporary, Cookbooks, Crime, Ebooks, Fantasy, Fiction, Graphic Novels, Historical Fiction, History, Horror, Humor And Comedy, Manga, Memoir, Music, Mystery, Non Fiction, Paranormal, Philosophy, Poetry, Psychology, Religion, Romance, Science, Science Fiction, Self Help, Suspense, Spirituality, Sports, Thriller, Travel, Young Adult,
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Inclusive Architecture - Introducing the PAMstack - [Refactr.tech]

  1. 1. INTRODUCING THE PAMSTACK A NEW FRAMEWORK FOR CREATING SUSTAINABLE DEVELOPMENT TEAMS INCLUSIVE ARCHITECTURE
  2. 2. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  3. 3. WHAT DOES INCLUSIVE ARCHITECTURE ENABLE? ● Less project maintenance ● Less overall stress ● More cooperation ● Lower cost of developers ● Lower cost of project ● Greater diversity
  4. 4. ROB OCEL @robocell Senior Software Engineer at This Dot Host, Modern Web Podcast Host, This Dot Labs Podcast
  5. 5. TRACY LEE @ladyleet Lead, This Dot Labs, JS consulting (Angular, React, Vue, Node, Polymer) Google Developer Expert, Angular Microsoft MVP RxJS Core Team
  6. 6. Juniors take too much time
  7. 7. WHY AREN’T JUNIORS SUCCESSFUL ON OUR TEAMS?
  8. 8. People believe that the reason juniors don’t succeed in their teams is due to a deficiency of the juniors. They don’t realize it’s actually a fault of their own.
  9. 9. How non-inclusive projects hurt juniors: ● Poor onboarding documentation ● Rely on individual excellence ● The superiority complex ● No review or mentorship
  10. 10. How non-inclusivity actually hurts everyone ● Harder to onboard and hire ● “Hit by a bus” fears ● Lack of inclusion ● Lack of advancement & stagnant careers
  11. 11. WHAT YOUR PROJECT COULD BE WITH AN INCLUSIVE VISION
  12. 12. Success is person-independent, but team-dependent Constant stream of developers across the spectrum of experience Less burnout, less panic hiring More innovation, more excitement, more learning THE INCLUSIVE VISION
  13. 13. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  14. 14. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  15. 15. “Processes are usually ad hoc and chaotic. The organization usually does not provide a stable environment to support processes...”
  16. 16. “... Success in these organizations depends on the competence and heroics of the people in the organization and not on the use of proven processes...”
  17. 17. “...In spite of this chaos, these organizations often produce products and services that work, but they frequently exceed the budget and schedule documented in their plans...”
  18. 18. “...These organizations are characterized by a tendency to overcommit, abandon their processes in a time of crisis, and be unable to repeat their successes.”
  19. 19. Process doesn’t have to be...
  20. 20. Process doesn’t have to be...
  21. 21. �� STORYTIME ����♀����
  22. 22. ● Clear expectations ● Greater team engagement and cooperation ● No single-points-of-failure ● Less stress during the crazy ● Reduced conflicts and fewer power struggles THE BENEFITS OF PROCESS DONE RIGHT
  23. 23. TRAINPLAN EXECUTEREVIEW MEASURE PROCESS
  24. 24. TRAINPLAN EXECUTEREVIEW MEASURE PROCESS
  25. 25. ● What needs to be done? ● Who will do those things? ● How should it be done? ● When should it be done? HOW TO CREATE PLANS
  26. 26. The person who makes the initial changes to the code, makes the review in CodeCollaborator and revises the Verification Items based on the results of the peer review. Responsible for reviewing Verification Items. Can be any developer except the author. At least one Peer Reviewer is required. Responsible for reviewing code. Can be any Project 4 team member. Unlike Peer Reviewers, they are not required to approve a review before it concludes. Having an observer is not required either. They take the role of Authors, Peer Reviewers or Observers. AUTHOR PEER REVIEWERS OBSERVERS DEVELOPERS ROLES AND RESPONSIBILITIES
  27. 27. The purpose of code peer review is to ensure that changes to source code Verification Items are correct, appropriate and follow style guidelines. The goal of the code peer review process is to discover and correct defects in code before they can be observed by testers or customers. CODE PEER REVIEW Once all Peer Reviewers have completed the review, the author responds to comments and corrects defects. If there is a disagreement about how to resolve an issue, the parties involved should work together to reach compromise. If an agreement is not reached, the Development Manager will arbitrate the dispute. If a review defect cannot be resolved in the scope of the peer review, it will be marked as Track Externally and a defect will be created in the Quality Center for the issue and the defect number is added on the peer review for traceability.
  28. 28. TRAINPLAN EXECUTEREVIEW MEASURE PROCESS
  29. 29. ● Minimize errors ● Teach new team members ● Reduce cognitive load CREATE CHECKLISTS
  30. 30. ● (Author) All relevant requirements are met ● (Author) Relevant documentation is updated ● (Author) All unit tests pass ● (Author) Code has been developer-tested ● (Author) Completed a self-review of the code, ● (Author) The code compiles without error CODE REVIEW CHECKLIST
  31. 31. ● Algorithms used in the code are correct ● Code is commented usefully ● All relevant documentation is updated ● New code conforms to the Coding Standards ● No files are missing from the review ● The code addresses all use cases and edge cases ● The code compiles and all unit tests pass ● The code validates input parameters CODE REVIEW CHECKLIST
  32. 32. TRAINPLAN EXECUTEREVIEW MEASURE PROCESS
  33. 33. ALWAYS GOT YOUR BACK
  34. 34. EFFECTS OF REVIEWS ● Improved Quality ● Cross-Pollination of Ideas ● Redundant Learning ● Reduced Stress ● Eliminating the Fear of Making Mistakes
  35. 35. TYPES OF REVIEWS ● Meeting Notes ● Designs ● Requirements ● Tests ● Code ● Plans ● Email to Clients
  36. 36. TRAINPLAN EXECUTEREVIEW MEASURE PROCESS
  37. 37. RECORD RESULTS
  38. 38. TRAINPLAN EXECUTEREVIEW MEASURE PROCESS
  39. 39. 1. How did we do? 2. Can we improve our execution? 3. Can we improve our processes? 4. Is the data we captured useful? Should it change? REVIEW, REVISE, ITERATE
  40. 40. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  41. 41. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  42. 42. WEB DEVELOPMENT IS HARD Performance Security Accessibility Responsive Design Progressive Enhancement Browser Compatibility Progressive Web Apps
  43. 43. WEB DEVELOPMENT IS HARD Performance Security Accessibility Responsive Design Progressive Enhancement Browser Compatibility Progressive Web Apps
  44. 44. COMPLEXITY IS A BARRIER TO ENTRY IN OUR INDUSTRY
  45. 45. FRAMEWORKS CAN HELP! THEY MAKE IT EASY TO DO THE RIGHT THING
  46. 46. LET A FRAMEWORK DEAL WITH BASIC PERFORMANCE & SCALABILITY
  47. 47. AMP provides all this for <amp-img> ● Image resize based on the size of the user’s viewport ● Images efficiently loaded or pre-loaded ● Automatically calculate reasonable values for the sizes attribute ● Content can be displayed as a placeholder while the image loads ● Content can be shown as a fallback if the image fails to load ● Images can be automatically converted to more efficient image formats like WebP in the AMP cache ● Images in the cache might also be resized and automatically built into a srcset in your document
  48. 48. QUICK START DEVELOPMENT - CLIS FTW!
  49. 49. ● Scaffolding a new project ● Zero-config environment ● Smart defaults ● Out of the box performance using automatic differential serving, lazy loading, tree shaking, AoT compilation ● Actively maintained and kept up-to-date with core libraries CLIS FTW! ● Reduce the risk of defects due to out-of-date or misconfigured technologies ● Easy migration between major versions of libraries ● Documentation readily available ● Low risk - ejecting always a possibility
  50. 50. FRAMEWORK GUIS
  51. 51. ● Goal is to isolate the construction of the interface from the business logic and the complicated tech integrations ● This could be done by separating the application into layers ● The senior engineers can implement the most critical sections and provide hooks for juniors to wire the interface together ARCHITECTURE
  52. 52. STATE MANAGEMENT
  53. 53. STATE MANAGEMENT
  54. 54. STATE MACHINES
  55. 55. DESIGN AND USER EXPERIENCE
  56. 56. ● Shared visual language for your team ● Focus and constrain the set of options when building interfaces ● Contain: ○ Design purpose and guidelines ○ Designer resources (ex: Sketch files) ○ Content guidelines ○ Patterns ○ CSS Classes DESIGN SYSTEMS
  57. 57. ● Set of basic reusable components ● Implement the requirements of a design system ● Help tackle accessibility, responsiveness, etc. ● API is usually more complete and thoughtful COMPONENT LIBRARIES
  58. 58. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  59. 59. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  60. 60. If developers aren’t growing, they’re much more likely to look for a new job. 35% of employees who are not regularly mentored look for a new job within 12 months. - Spherion Emerging Workforce Study -
  61. 61. ● Costs up to double a developer’s salary to recruit / train someone ○ Applicant screeners and interviewers ○ Recruiters ○ Trainers and lost productivity ● Hiring can take 6-8 weeks; ramp-up can take 2-6 months ● In contrast, even spending a lot to mentor employees can pay off ● Mentorship dollars now can pay off in improved productivity later COSTS OF HIRING
  62. 62. 2x 0x 0x 5x 0x 1x 2x 3x 1x 5x 1x 2x 3x 1x 5x MENTORSHIP OUTPACES INDIVIDUAL EXCELLENCE - THE MYTH OF THE 10X DEVELOPER - 4x 4x 6x 7x 10x INDIVIDUAL MENTOR MENTOR INDIVIDUAL MENTOR
  63. 63. ● Accelerates learning & growth ● Increases confidence ● Decreases fear of contribution/collaboration/idea sharing ● Increases communication skills ● Mentees feel more invested-in and valued ● Improves upward mobility (5x more likely to be promoted) ● Mentees become mentors and pass all these benefits on Eric Elliott https://medium.com/javascript-scene/struggling-to-find-great-senior-javascript-developers-mentorship-is-the-answer-d352ea3574eb WHAT’S IN IT FOR MENTEES
  64. 64. ● Great perk for recruiting ● Increases developer productivity & retention (~70% more likely) ● Reduces knowledge silos ● Improves the bus factor — reduces succession risks ● Creates a more positive, helpful, collaborative team culture ● Increases loyalty ● Increases employee engagement and motivation ● Improves leader identification and promotion pipeline — mentors are 6 times more likely to be promoted (Sun Microsystems) WHAT’S IN IT FOR OTHERS Eric Elliott https://medium.com/javascript-scene/struggling-to-find-great-senior-javascript-developers-mentorship-is-the-answer-d352ea3574eb
  65. 65. ● Fostering a culture of teaching and sharing ● Formal 1:1 Sessions ● Code Reviews ● Pair Programming ● “Tech Talks” ● Chat Channels SHIFTING THE ROLE OF THE SENIOR DEV
  66. 66. MENTORSHIP INCLUDES Technical Challenges Professional Instruction Non Technical Skills Career Development Radical Candor Feedback
  67. 67. WHAT IS THE PAMSTACK? PROCESS MENTORSHIPABSTRACTIONS
  68. 68. HOW JUNIORS CAN HELP THEIR TEAM USE THE PAMSTACK ● Bootstrap process by writing things down, sharing with the team ● Mentor and help your peers who are being onboarded ● Ask questions about the project, code, or process. Document the answers and share with others. ● Do and ask for code reviews proactively as a way to understand, get feedback, and create a culture of mentorship. ● If team loves your process or ideas, ask for it to be formally incorporated into process
  69. 69. hi@thisdot.co THANK YOU!

×