-
There should be a way to enforce maximum number of dependencies: both module dependencies and injected services. It may be used to enforce architectural decisions when a module grows.
-
Too many people nowadays have lost sight of the fact that architecture - be it software, solution, enterprise, system, database or whatever architecture - is really a process, and not an artifact.
…
-
At a minimum:
- Add a detection table entry, which following the pattern of other games, will have a puny-encoded unicode filename for the Obsidian Installer. (`Common::punycode_decodefilename` can d…
-
we should create (and maintain!) documentation on how to run the application locally. additional points may be architectural decisions and how the application should be maintained.
this should be l…
-
Add a markdown doc in the repo with our architectural guidelines and decisions.
This will be a living doc that we use to make sure all devs understand the high level direction.
-
### Problem to solve
Often, designing software developers are creating documents called ADRs (Architectural Decision Record) which let's you to see decision making proces for given change. We have …
-
* Beyond #12
* update repos → generate table(s) → write table(s)
* What are the design decisions hard to change later on?
* Design patterns? https://techbeacon.com/top-5-software-archite…
-
We are no longer time limited, one of the things we should be doing is gradually be refactoring the code base so it's no longer full of dumb decisions. This means encapsulation and a sane architecture…
-
As a team member working on this product I want to have one point of reference of agreed architectural decisions and full solution in one place
-
We need to identify the individuals responsible for architectural decisions around feature sets. @CarBar could be responsible for everything but I think it would be more sustainable if we subdivided t…