Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for describe (0.15 sec)

  1. architecture/standards/0002-avoid-using-java-serialization.md

    Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors.
    
    ## Decision
    
    We do not use Java serialization.
    Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized.
    
    For internal purposes, we use binary formats for their brevity.
    We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu Feb 29 22:32:18 GMT 2024
    - 2.3K bytes
    - Viewed (0)
  2. architecture/standards/0001-use-architectural-decision-records.md

    ## Decision
    
    The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.
    
    The main logic with ADRs is to describe (architectural) decisions made:
    
    * To provide best practices and solutions we (as the *build tool* team) want to promote.
    * To avoid asking the same thing multiple times during code review.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sat Mar 02 21:54:40 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  3. architecture/README.md

    # Gradle architecture documentation
    
    This directory contains documentation that describes Gradle's architecture and how the various pieces fit together and work.
    
    ## Architecture decision records (ADRs)
    
    The Gradle team uses ADRs to record architectural decisions that the team has made.
    
    See [Architecture decisions records](standards) for the list of ADRs.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 06:42:46 GMT 2024
    - 2.4K bytes
    - Viewed (0)
Back to top