https://github.com/anchore/grype
A vulnerability scanner for container images and filesystems. Easily install the binary to try it out. Works with Syft, the powerful SBOM (software bill of materials) tool for container images and filesystems.
Dependency-Track
Dependency-Track is an intelligent Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Dependency-Track takes a unique and highly beneficial approach by leveraging the capabilities of Software Bill of Materials (SBOM). This approach provides capabilities that traditional Software Composition Analysis (SCA) solutions cannot achieve.
Verteilung des Traffics im Deutschen Internet
Cursorless
Visualizing MBTA Data
37 agile metrics for development teams
Actionable Agile Metrics
Gitlab for agile Software Development
PRINCE2
The GRPI model – an approach for team development
ITIL4
V-Modell-XT 2.3
Projektmanagment im öffentlichen Dienst
Fünf agile KPI-Metriken
JobsToBeDone
Handbook First
The Gitlab Inc. Handbook and the “Handbook First” approach.
https://handbook.gitlab.com/handbook/
https://handbook.gitlab.com/handbook/handbook-usage/#handbook-guidelines
How platform teams get stuff done
B612 Font family
B612 is an highly legible open source font family designed and tested to be used on aircraft cockpit screens.
Linear code is more readable
Clean code again. This blog.separateconcerns.com post is a reply to this testing.googleblog.com post .
My opinion. I buy both! For me it is a matter of code maturity. During early development I like a to leave code in linear style like proposed by the commentor. Abstraction is expensive and sometimes I feel like I don’t need the extra step. But at some points I definitely like to clean code like proposed in the original post.