-
Create some wiki pages that describe (maybe also with a couple of graphics) the concept of the HeAT design, assumptions made in tensor and MPI handling and architectural decisions.
-
If you introduce ADRs into a project (or organisation), then the decision to introduce ADRs should be recorded as an ADR.
This ADR context should explain:
- WHY documenation of architectural deci…
-
Initial setup for our future components:
- Rollup setup
- Tests setup with [jest](https://jestjs.io/) and [enzyme](https://enzymejs.github.io/enzyme/docs/api/#)
- SCSS architecture for global an…
-
This issue will track the discussion around potentially adding Architectural Decision Records (ADRs) to the BDK repository.
I personally learned about them for the first time last year when reading…
-
Although intent is not an architectural language, it may make a lot of design and architecture work easier if it facilitates talking about high-level concepts such as those that often make their way o…
-
I think the monorepo hype can result in bad architectural decisions if not properly evaluated.
-
I googled for architectural decisions and found https://github.com/joelparkerhenderson/architecture_decision_record. The README.md is pretty good, maybe the ideas can also be resued for a README.md he…
-
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.
-
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…
-
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…