arrow_back Deploying and Managing CSP: the Browser-side Firewall
Building for developer experience arrow_forward
If you are going to transpile JS, why not use ClojureScript?
Submitted by Shivek Khurana via Zainab Bawa (@zainabbawa) on Tuesday, 10 September 2019
Section: Full talk (40 mins) Technical level: Intermediate
This talk is philosophical in the sense that it focuses on the larger problems of the JS ecosystem and finds an objective solution to a subjective problem.
[Alpha Version] A rough outline is as follows:
- Build Up/ Problems: Situations that led me to question my toolkit & introduced me to Clojure/Script
- Pain on Learning: Understanding the Clojure (functional) model and problems faced
- Rewards: How the Clojure model solved my Problems
- Growth Phase: How adopting the new model accelrated my thought process and my dev workflow
- Conclusion: The current state of affairs and what you can do to get started
A general understanding of the JS ecosystem. Some experience in shipping/ maintaing a web application, API, or a mobile app.
Shivek has been building (and breaking) enterprise applications for more than a decade. His carrier began at a young age of 14 and largely consisted of unpaid work at Startups & SMEs. Over the years, he was lucky to find exceptional teachers, who helped him mature as a system architect. In this long journey, he has touched all parts of the stack, from Frontend to Backend, Data Pipelines to DevOps.
Since 2013, his focus has been on Frontend Development using React. He has built systems that are used by 0 to over 12 million users. This experience has shaped his ideas about how to grow and maintain complex applications and his preference for Clojure/Script.
When it comes to software, he’s an expert at avoiding shiny new things, and focusing on the old and boring. He firmly believes that all code is liability and the best piece of code is the one that was never written.