JSFoo 2019

On component architecture, front-end engineering and Developer Experience (DX)


Is coding all we need to do? There's more to the story ...

Submitted by Navya Agarwal (@navyaagarwal) on Monday, 9 September 2019

Section: Crisp talk (20 mins) Technical level: Beginner Status: Rejected


“Good coding practices” is one of the most searched thing that most developers hit on any search engine today. But does it all stop there? Is developers job just limited to writing good code? What about the background work that eventually makes this code to run and be rendered on the browser? Which package manager, test framework or bundler should we use in our application?

This talk is all about the inevitable steps and the indispensable decisons we ought to make post coding. Many times we turn a blind eye towards them and undermine their importance. I will take an example from my personal experience, where we built a CI/CD pipeline to integrate these post-coding steps and did a lot of brainstorming to provide our teams with the best frameworks/solutions to assist to such decision making.

We started with an aim to provide one build solution in the form of CI/CD pipeline as a service, which in modern software development, is indeed a key pillar of moving fast. Our mantra was to push for standardization of build-time and run-time processes, thus eliminating redundancies and increasing development velocity. We intent to control the “blast radius” that an undesired defect can have while building and at the same time allow product teams to granularly control what new features/changes are to be rolled out.

In this talk I will go through the various build steps in the pipeline and how front-end developers can leverage the most optimal solutions for:
Package managers
Unit Test
Integration Tests

Developers no longer would have to be in a dilemma and can easily fight the Do’s and Don’ts of post coding features.
It’s Time to Enjoy optimal building. :)


I’ll start the talk by our motivation to develop a SPA CI/CD Pipeline and the hard decision-making and brain-storming our team had to do in order to standardize build configurations. Next, I will take a deep-drive into our Pipeline’s architecture and the various building-blocks of our one build solution. The journey was definitely not a smooth one… But, what is Success without hurdles and failures? I will be describing in detail the various Do’s and Don’t we experienced on our Build Journey.


Laptop and internet connection

Speaker bio

I am a polyglot developer working with Adobe Experience Cloud. I currently look after the authentication and orchestration part of the stack with the broad goal of optimizing the performance and scalability of the system. I have been an active speaker. My most recent talk was at GraphQL Asia this year: https://www.graphql-asia.org/speaker/navya-agarwal




  •   Zainab Bawa (@zainabbawa) Reviewer 6 months ago

    Thanks for submitting an interesting proposal, Navya. While the details of the implementation are important, the moot question is: what is the larger argument or point that your proposal is trying to drive home? What should a participant, who is not from Adobe’s context or who doesn’t have Adobe-like challenges yet, must know about SPA run-time pipeline?

    The abstraction will be critical, because we don’t want to present only organizational case studies, but extend the learnings such that these are generalizable for developer productivity in any org.

    Look forward to your response.

  •   Navya Agarwal (@navyaagarwal) Proposer 6 months ago

    Hi Zainab, let me explain the idea and how it can benefit the audience (org agnostic) as a whole.
    Generally we are only apprehensive about the best coding practices. What we neglect is the story and background work post coding. The idea here is to highlight the best practices which we should brainstorm on post writing the code and the effort spent on such activities. This is something we realized at Adobe, and came up with a common solution so that teams don’t have to waste their precious time, worrying about the same. The main aim here is to instill within the audience the various Do’s and Don’t while making such a decision. All the learnings are from personal experience.

Login with Twitter or Google to leave a comment