JSFoo 2019

Annual conference of 800+ front-end, backend and fullstack engineers

Participate

Sharing Code Across UI Teams, Frameworks are 9/10 work done. Finding the missing 1/10

Submitted by saurabh.sh (@saurabh-sh) on Thursday, 23 May 2019

Section: Full talk (40 mins) Technical level: Advanced

Abstract

Why it is vital as a big tech setup to be investing into internal core teams and following standards to maximise code reuse with components driven design. How setups like AirBnB, Uber, ING all have followed and benifitted from investing in core tech processes.

Outline

  • Having a core development methodology team. Why it matters ?
  • CDD (component drivent design) for faster execution and deliveries
  • Vue, React, Angular, Polymer etc can co-exist. F/W agnostic
  • Components save time , only if used rightly
  • How developing UI components needs commandments
  • Learning curve and discipline(of the methodology) needed across teams
  • Tools of help - lerna, storybook, styled-components, gitlab pipelines
  • A mix of storybook based platform for components sharing
  • tests and continuous integration a must carry-along
  • Speed it up with web-components

Speaker bio

  • Web Developer since 2004
  • Corporate life 1 (2004-2013)
  • Founder, Prokriya (Web Consultancy)
  • Founder, Appler (Web based Product Development)
  • Corporate life 2 (2019-Present)
  • Working with same challenges with a 70+ people team at IBM India
  • https://www.linkedin.com/in/saurshaz/

Comments

  • Abhishek Balaji (@booleanbalaji) Reviewer a month ago

    Hi Saurabh,

    Thank you for submitting a proposal. We need to see detailed slides and a preview video to evaluate your proposal. Your slides must cover the following:

    • Problem statement/context, which the audience can relate to and understand. The problem statement has to be a problem (based on this context) that can be generalized for all.
    • What were the tools/frameworks/approaches available in the market to solve this problem? How did you evaluate these, and what metrics did you use for the evaluation? Why did you pick the option that you did?
    • Explain how the situation was before the solution you picked/built and how it changed after implementing the solution you picked and built? Show before-after scenario comparisons & metrics.
    • What compromises/trade-offs did you have to make in this process?
    • What is the one takeaway that you want participants to go back with at the end of this talk? What is it that participants should learn/be cautious about when solving similar problems?

    We need your updated slides and preview video by 5 June to evaluate your proposal. If we do not receive an update, we’d be moving your proposal for evaluation under a future event.

  • Abhishek Balaji (@booleanbalaji) Reviewer 10 days ago

    Marked as rejected since proposer hasnt responded to comments/updated content before deadline. Will be considered for a future event if content is updated.

Login with Twitter or Google to leave a comment