![]() It is common for beginners to have automatic financial calculations that will run when the user visits the list view. With the application growing in complexity, with more users, and more records, the application will suffer grow-ing pains.įor example, a solution may have a screen that allows users to see a list of invoices. This, in turn, leads to more records being added to the solution. If your application is successfully received by your coworkers, then they will want access themselves. This problem becomes increasingly obvious as time passes. This is ***ESPECIALLY*** noticeable if there are large numbers of records, say more than 100,000, and the solution is running across the internet to multiple remote users. This automatic activation of calculations is appropriate for beginners but has the negative effect of dramatically slowing their application’s performance. To achieve this level, you begin to realize that FileMaker has a habit of automatically running processes in the background. Intermediate developers are defined by their use of scripting to precisely control their FileMaker application. This is totally okay! It’s a rare developer that doesn’t cringe at their beginner attempts to make FileMaker apps. After all, you didn’t initially need it! You also might, as time goes on, cringe at your beginner solutions. Developers tend to only pursue security and speed as their application suffers growing pains, which is perfectly understandable. other aspects must be taken into consideration. In summary, as a beginner, you were concerned with making an application work! Now, because your application is being shared (we assume it “Just Works”). To continue our table metaphor, your friends came to visit and eat at your table! At this point, you begin to realize the table has a few problems - because John’s bowl at the other end slid off and hit the floor, Wanda suggested a different finish, and at some point, you realized that you needed different wood for the legs. In other cases, it might require that the application be rebuilt entirely. In some cases, this means minor fiddling and adjustments. As a result, you are likely to focus on performance optimization and reworking parts of the solution, so it runs more quickly. You might receive a lot of complaints about speed. It used to be fast but slowed as more features got tacked on and more people used it concurrently. With time, something else will make itself apparent - your database’s performance is slowing. These requests will likely incentivize you to improve your skill set. People will begin to request features, point out flaws - real or imagined - and pester you with requests. What you might not realize is that by sharing, you have opened your-self up to user feedback – BRACE FOR IMPACT.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |