![]() Second, believe it or not, this is very useful for you. Some will handle internet requests, some will house the ‘business logic’, others still will hold the data that is saved (cylinders). ![]() ![]() Ask them to walk you through what each component (box) in the system does. “Why are there only two of the thing called triple store?”įirst, don’t panic. Whereas the stack is mostly about raw technical capability, the architecture of a product incorporates the customer’s intended behaviour in its design.įastest way to learn - Ask an engineer to draw you the architecture. If the stack represents what technologies are being used, system architecture represents how those technologies are structured to work together to deliver the product. Knowing this may push you to re-consider a different way to solve the problem. Generally, the more layers in the stack they need to touch, or the deeper the layer, the more complicated and risky a change will be. Knowing the stack means you can at least follow along, and over time you’ll begin to understand what depth in the stack they’re referring to. How does this make you a better PM? - When engineers are discussing how to build something, terminology flies around the room. Stay at a high level because you can fall into the rabbit hole easily (add “trade offs + benefits + vs” to your search query) Quick Googling of those terms will teach you some of the high level benefits and trade-offs of each technology chosen, and how they work in harmony together. From the moment a customer loads your landing page to when they delete their account, the technologies in the stack handle everything.įastest way to learn - Ask an engineer to take you through the stack at a high level. When engineers refer to ‘the stack’, they’re talking about the layers of technologies that are used to provide functionality to your product (i.e.
0 Comments
Leave a Reply. |