Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update scaling.Rmd #459

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update scaling.Rmd #459

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions scaling.Rmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ This will include problems like:

- "I haven't worked on this code in 6 months and I'm afraid I'm going to break it if I make any changes."

- "Someone else started working with me on the application and we keep standing on each others toes."
- "Someone else started working with me on the application and we keep stepping on each others toes."

- "The app works on my computer but doesn't work on my collaborator's or in production."

Expand All @@ -23,9 +23,9 @@ In this, the "best practices", part of the book, you'll learn some key concepts

- In Chapter \@ref(scaling-modules), you'll learn about Shiny's module system, which allows you to extract coupled UI and server code into isolated and reusable components.

- In Chapter \@ref(scaling-packaging), I'll show you how to turn your app in R package, and motivate why that investment will pay off for bigger apps.
- In Chapter \@ref(scaling-packaging), I'll show you how to turn your app into an R package, and explain why that investment will pay off for bigger apps.

- In Chapter \@ref(scaling-testing), you'll learn how to turn your existing informal tests into automated test that can easily be re-run whenever your app changes.
- In Chapter \@ref(scaling-testing), you'll learn how to turn your existing informal tests into automated tests that can easily be re-run whenever your app changes.

- In Chapter \@ref(performance), you'll learn how to identify and resolve performance bottlenecks in your apps, ensuring they remain speedy even when used by hundreds of users.

Expand Down