![]() To start with, we can scale it across the many processes that comprise our application - and then, it’s automatically scaled across the iterations in our development process, resulting in a large overall improvement. Live reload can have a dramatic effect on our performance - not just because it automates the boring and tedious manual reload, but also because it can be scaled up. Figure 2: The coding cycle expanded to include multiple iterations Scaling live reload for improved performance Any improvements that we can make to each small iteration of coding will have an amplified effect on our overall development process. Through this process, we take our code from working state to working state, accumulating working code and minimizing the build up of bugs. This is a birds-eye view of the ongoing process of development. This might sound like a lot of windows to have open (I mostly use a desktop computer with three screens), but it’s incredibly useful to be able to edit code across your stack and see the results almost instantly without having to manually restart or synchronize anything.īelow, Figure 2 shows the coding cycle unraveled over multiple iterations. Another terminal (or maybe two!) running automated testsĪs soon as I change any code, I can watch as live reload kicks in across my multiple terminals and browser windows.One terminal for a particular microservice on which I’m focusing.One terminal running a microservices application (under Docker Compose).Often, as a full-stack developer, I take this to the extreme. This automation delivers the fastest feedback possible. (If I’m working on a frontend, I’ll have it open in a web browser.)Īs I edit my code and save the file, the application (backend or frontend) automatically reloads to pick up the latest code changes - each tiny code change triggers a reload. I also have a terminal open - let’s say it’s running my backend with live reload. I have my IDE open (I use VS Code), and I’m editing the code for my application. If you haven’t used live reload before, let me paint a picture for you. Figure 1: Where live reload lives in the coding cycle Setting up for live reload ![]() Note the part of the diagram that says “This part can be automated” - this is where live reload fits. It’s quite typical for developers to use live reload when creating a webpage, but we can also apply this technique across our whole stack.įigure 1, below, shows where live reload fits in our coding cycle. Enabling this saves you countless manual and tedious restarts. It enables our app to automatically and simultaneously pick up code changes while we are coding. Live reload is an automated approach to restarting our application during development. The topics in this post increase in difficulty as you move through it, and we’ll go back and forth between backend and frontend experiences as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |