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.
Who should attend JSFoo:
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
JSFoo 2019 sponsors:
For tickets and sponsorships, contact email@example.com or call +91-7676332020. For queries about proposing talks, write to firstname.lastname@example.org
Demystifying front-end tech stacks
“Should I go with React or Vue?”
“I want to use Elm in my company, it looks really interesting!”
“What library do you recommend for X?”
Sounds familiar? This talk is for you.
The front-end ecosystem evolves faster than most of us can keep up. When it comes to making architectural decisions, like choosing a tech stack, it is difficult to make informed, future-ready decisions. I’ll be talking about
- Why are these decisions difficult to make?
- Factors to consider along 3 axes
- How to approach decision making
- Case study from Quintype of choosing a tech stack for a major front-end rewrite, the whys, what worked, and what didn’t
Why are these decisions difficult to make?
- Cost of initial development vs. Cost of maintenance
- Definition of architecture - decisions that take significant costs/resources (time/money/business growth/people) to change
- Front-end fatigue
- Resume-driven development/attracted to shiny, new things
- Goal - to build confidence in the decision
Factors to consider along 3 axes
- Support 2-3 years of features/improvements
- Integration - will it play well with existing tech in the org?
- Enabling useful abstractions
- How do we prevent people from making mistakes?
- Fast feedback loop
- How to approach decision making
- Kitchen Sink
- Architecture Decision Record (ADR)
Case study - major front-end rewrite
- Quick introduction of the app’s major features
- Why do a rewrite?
Tech stack + what led to picking these (Popularity isn’t one of them)
- Typescript + strict mode
- Redux + Thunk
- React Router
- Enzyme’s shallow & mounting tests as rule & exception
- CSS modules
Write down all the questions you have about your tech stack decisions, and ask me before/after the talk.
Dheeraj has been working for about 10 years now, in the nexus of tech, people, product and process. Technically, he’s a full stack engineer because he can create issues in any layer of a system. He just says he is a specialist in being a generalist. Dheeraj loves bad jokes; others around him aren’t as… appreciative. He likes video games, and someday, to create his own.