JSFoo is in its ninth edition this year. Talks at JSFoo 2019 will cover the following topics:
- Component architecture -- how different web components have been stitched together to build apps; outcomes on UI and performance as a result of architecture choices
- Deployment practices for front-end and how Kubernetes and CI/CD fall into this picture
- Developer experience (DX)
- Functional programming paradigms: ReasonML and ClojureScript
- Privacy and Content Security Policy (CSP)
- New developments such as SvelteJS
Speakers from Razorpay, CloudCherry, Myntra, Innovaccer, GitLab, Microsoft, Atlassian and Gramener will share their work and learnings on these topics.
JSFoo is a conference for practitioners, by practitioners. JSFoo 2019 is a conference for:
- Front-end engineers
- Senior software developers
- Team leaders and engineering managers
- Fullstack developers
- InfoSec professionals
##JSFoo 2019 details:
Dates: 27 and 28 September
Venue: NIMHANS Convention Centre, Bangalore
The following workshops have been curated for before and after the conference:
For inquiries about conference tickets, workshop tickets and any other details, call JSFoo on 7676332020 or email firstname.lastname@example.org
For tickets and sponsorships, contact email@example.com or call +91-7676332020. For queries about proposing talks, write to firstname.lastname@example.org
Is coding all we need to do? There's more to the story ...
“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:
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
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