3 ms·
Perhaps another slant that has long seemed apt: choosing the dependencies and steering the organization of the software and its stack. Minimizing the dependenci
by quantified 5y ago
Perhaps another slant that has long seemed apt: choosing the dependencies and steering the organization of the software and its stack. Minimizing the dependencies to those strictly necessary, treating as many as plausible as an implementation detail, and judiciously leveraging the strategic ones, all flow from that.
- relaunched 5y agoif you are thinking in terms of dependencies and a singular "stack", the organization is probably not complex enough for architecture as a function. When you are running 5 different types of messaging queues, including 2 that were grown in-house, you need architecture.