Skip to content
View alexandreLamarre's full-sized avatar
💭
I may be slow to respond.
💭
I may be slow to respond.
  • SUSE
  • Montreal, Canada
  • 02:01 (UTC -04:00)

Block or report alexandreLamarre

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 250 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
alexandreLamarre/README.md

It seems to be the designer's responsibility to construct his mechanism in such a way--i.e, so effectively structured--that at each stage of the testing procedure the number of relevant test cases will be so small that he can try them all and that what is being tested will be so perspicuous that he will not have overlooked any situation

  • Dijkstra, 1968, The Structure of the "THE"-Multiprogramming System

Pinned Loading

  1. rancher/rancher rancher/rancher Public

    Complete container management platform

    Go 24.7k 3.1k

  2. rancher/opni rancher/opni Public archive

    Multi Cluster Observability with AIOps

    Go 357 63

  3. otelcol-bpf otelcol-bpf Public

    Open telemetry collector that integrates eBPF scripts for observability

    C 5

  4. dlock dlock Public

    Reliable & scalable distributed locking, scheduling and process synchronization

    Go 5

  5. pomerium/pomerium pomerium/pomerium Public

    Pomerium is an identity and context-aware access proxy.

    Go 4.4k 311

  6. open-telemetry/opentelemetry-collector open-telemetry/opentelemetry-collector Public

    OpenTelemetry Collector

    Go 5.8k 1.7k