Santosh Yadav

The default templates provided by React or Next can be a great starting point for most projects, but as soon as your app grows, you may want to customize the workspace to fit your needs. But the question is how to do it; also, what if you want to introduce new tooling to your workspace like Cypress or Playwright? How about keeping your workspace evergreen? It's manual work. The current answer for your team must be a custom script. Adding more tools means increasing your build time. Does it all sound relatable to you? Join me in this talk to see how you can give superpowers to your React/Next or Remix workspace and make your team more productive. Key Takeaways: - Customizing your workspace - Nx generators - Nx Executors - Adding your own tooling

Maintaining a huge codebase is always a challenge, you need to ship features, run the business as usual, and introduce new tools, and it becomes more challenging when you have many teams contributing to the code base. At Celonis we use Angular and Nx for monorepo and ship updates to more than 40+ apps, which have 2 million lines of code, and we are adding more apps and libraries as we go. Nx is a build tool, with the support for mono-repos and provides the flexibility to bring any tools/framework/technology to the mono-repo and helps to reduce build time by providing the ability to cache builds. Maintaining this huge codebase is a challenge, especially when you need to ship updates to them every week. More challenges come with a codebase this big; you may need new tools in your codebase, and new tools are released every week. What if you need to do a Proof of Concept, add a new Angular App, or update a new version of Angular or tooling like Cypress, Playwright, or Jest? But we also get around 100 PRs per day from more than 30 teams contributing to the codebase; for each PR, we need to Run Unit Test, build, Component Test, User Journey test, and lint. A new feature can break your application: how do you plan your release rollback shipping new features with confidence? But it can cause new features/ bug fixes to be rolled back from other apps; feature flags are an answer, but how can it be done in a codebase this big? In this talk, we explore the world of Nx, where we can build, test, and deploy 40+ apps every week with the help of Nx. You will learn about: Maintaining a huge Angular code base CI/CD, GitHub Actions, Merge Queue Release strategy Feature Flags Introducing new tools to the codebase

Maintaining a huge codebase is always a challenge. You need to ship features, run the business as usual, and introduce new tools, and it becomes more challenging when you have many teams contributing to the code base. At Celonis, we use Angular and Nx for monorepo and ship updates to more than 40+ apps, which have 2 million lines of code. We are adding more apps and libraries as we go. Nx is a build tool that supports mono-repos and allows users to bring any tools/framework/technology to the mono-repo. It also helps reduce build time by allowing users to cache builds. Maintaining this huge codebase is a challenge, especially when you must ship updates to them weekly. More challenges come with a codebase this big; you may need new tools in your codebase, and new tools are released every week. What if you need to do a Proof of Concept, add a new Angular App, or update a new version of Angular or tooling like Cypress, Playwright, or Jest? However, we also receive around 100 PRs per day from more than 30 teams contributing to the codebase; for each PR, we need to Run a Unit Test, build, Component Test, User Journey test, and lint. A new feature can break your application. How do you confidently plan your release rollback to ship new features? However, it can also cause new features/ bug fixes to be rolled back from other apps. Feature flags are an answer, but how can they be done in a codebase this big? In this talk, we explore the world of Nx, where we can build, test, and deploy 40+ apps every week with the help of Nx. You will learn about: Maintaining a huge Angular code base CI/CD, GitHub Actions, Merge Queue Release strategy Feature Flags Introducing new tools to the codebase

GitHub Actions has become an integral part of any organization today, developers are using it for CI/CD every day at work and even in personal projects, thanks to generous free tier by GitHub.But with great power comes great responsibility, there are external entities waiting for you to make a mistake so that they can get access to your infrastructure. In this talk we will learn about: GitHub Actions Best Practices Securing your GitHub Actions This will be an interesting topic for everyone using GitHub Actions daily.

I spoke about how teams can use Nx to improve everyone's developer experience.

I spoke about Angular and Google Bard to generate GitHub Actions

After working on many enterprise apps, one common thing is the challenge of using strict mode. Most apps start without strict mode or divert from strict mode at some point. Once the code base becomes more extensive, it becomes hard to adopt strict mode. At Celonis, we have more than 26 apps and close to 100 libs, with more than 100k lines of code, and we had the same challenge. Strict mode brings more type-checking to the code base, which means delivering apps with more confidence. In this talk, I will share how we incrementally planned our migration so we don't block the entire team, only doing the strict mode migration and delivering once they have a resource. So join me in this lightning talk and move your apps towards strict mode.

GitHub Actions has become an integral part of any organization today, developers are using it for CI/CD every day at work and even in personal projects, thanks to the generous free tier by GitHub. But with great power comes great responsibility, there are external entities waiting for you to make a mistake and they can get access to your infrastructure. In this talk, we will learn about: - GitHub Actions Best Practices - Securing your GitHub Actions I am sure this will be an interesting topic for everyone using GitHub Actions daily.