3 ms·

Location of data, policies, cross-cutting concerns, latency/performance requirements, etc. “Much later” is probably an exaggeration. You get to types “soon af

• qayxc 2y ago
  Types are a useful design tool to explore the problem domain first, while the rest are details that emerge from that. Sure, if one starts with architecture, you're right. The software architect needs to consider these first. The programmer on the other hand ideally expects those as inputs. When tasked with wearing on multiple hats (architect, programmer, user), I agree with your point. From a programmer's point of view, however, (abstract) types are IMHO indeed a much more useful tool as they cover many of the other concerns (policies, performance, etc.), too.
  • acchow 2y ago
    In my experience, a software engineer wears all the hats nowadays. Even crossing into product design and user experience.
• nightski 2y ago
  It's interesting that you think about those things without even understanding how you are going to solve the user's problem first. Aka functional requirements.