architecture-decision
exploring-the-testing-hyperpyramid
architecture-decision | exploring-the-testing-hyperpyramid | |
---|---|---|
5 | 2 | |
- | 11 | |
- | - | |
- | 5.4 | |
- | about 1 month ago | |
Kotlin | ||
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
architecture-decision
-
Show HN: Architecture Decision Record – Spanish Tranlsations
Link is https://github.com/joelparkerhenderson/architecture-decision...
-
Architecture diagrams enable better conversations
Hi, article author here, we supplement our architecture diagrams with Architectural Decision Records (ADRs) https://github.com/joelparkerhenderson/architecture-decision... in the ADR we capture:
-
Polar v1.0: Let’s Fix Open Source Funding
If anyone wants to see Polar in action on a GitHub issue, I'm experimenting with Polar on my Architecture Decision Record repo:
https://github.com/joelparkerhenderson/architecture-decision...
(I'm on the fence about the value of Polar for this kind of issue... see what you think)
-
A Simple Framework for Architectural Decisions
Architecture Decision Records are a big help for teamwork. I have a bunch of notes and examples here, including from my time at ThoughtWorks with technology radars.
https://github.com/joelparkerhenderson/architecture-decision...
-
How boring should your team be
The article mentions Architectural Design Records (ADR) which can be included as a folder in the git repo for the project, as a means of documenting the historical decisions that led to the project's current structure. Some of that seems overly complex or formalized (i.e. reinventing UML and all the problems that came with it), but having that history in some kind of constant format would likely help overcome any novelty issues and help people grasp what's going on. The simplest format discussed seems the best for most cases:
https://github.com/joelparkerhenderson/architecture-decision...
exploring-the-testing-hyperpyramid
-
Architecture diagrams enable better conversations
Http4k, a http library for Kotlin, has an, in my opinion, great way of generating documentation for you [0]. They explain it in more detail in their talk [1] and also have an example repository [2], if you favor to look at code.
[0] https://www.http4k.org/blog/http4k_v5/#tracerbullet_a_brand_...
[1] https://www.youtube.com/watch?v=CrslqbMbaD8
[2] https://github.com/http4k/exploring-the-testing-hyperpyramid
-
http4k at KotlinConf '23: Exploring the Testing Hyperpyramid. aka: Auto-generation of visual documentation from tests
There is also a companion GitHub repo where you can find all of the code.
What are some alternatives?
structurizr-site-generatr - Static site generator for architecture models created with Structurizr DSL
arc42.org-site - (jekyll-based) website for arc42.org - the template for communicating software architectures.
architecture_decision_record - Architecture decision record (ADR) examples for software planning, IT leadership, and template documentation
java - Structurizr for Java
d2 - D2 is a modern diagram scripting language that turns text to diagrams.
polar - Polar is the creator platform for developers & the open source ecosystem.
rfcs - Specifications for Interledger and related protocols
Diagon - Interactive ASCII art diagram generators. :star2: