Many times, software engineers want to look through a window at the state of a product within the computer code. For example, if the item in question is a blouse, on the computer end, an engineer might want to test the software on it to ensure that status updates are allowed. After all, he wrote the program to process the ordering, shipping, and receiving of each garment for a particular department store that used his programming services.

Let’s say our software engineer is a typical guy named Mike. His supervisor, a guy named Cesar, wants to know at what points in the journey that he undertakes that blouse in question, starting from the store’s inventory and ending at the customer’s house, what is the status of it. Mike has a particular programming style where he will organize that input/state value into a particular memory space.

In other words, through the Internet, the customer will be able to access the program to order the garment they want and, at the same time, a behind-the-scenes manager can access that same program to complete a status report on any particular garment. the system.

When people talk about front-end code in relation to the main body of code, they are referring to software that accesses the main software program to get products. The back-end code links to the same body of the main code (exactly the same) for inventory tracking and analysis purposes.

For example, let’s make memory point 0x20f60 ​​our staging memory location. We would simply start with a list of state option labels. They would include: Color of Garment; Garment size; Quantity of the Pledge in question; Name of the buyer; Purchaser’s address; Garment Price. Given these six initial parameters, César, Mike’s boss, would choose one to know the status of one of them.

It would have a dropdown menu titled Status Parameters. Then each of those six parameters would appear in that dropdown, and by choosing one of them, Caesar would get the status regarding that particular parameter. For example, if he chose the Color of the garment, the status return could be PURPLE. For the size of the garment, the status return can be EXTRA LARGE. The magic of this programming is that each status word will be organized at memory point 0x20f60, making it easy to add more parameters at any point.

This programming style of having a dedicated memory point to represent state values ​​is not only convenient for our software engineer Mike, but also useful for designing the behind-the-scenes code for our supervisor Cesar.