Explore >> Select a destination
|
You are here 
|
tech.michaelaltfield.net | ||
| | | | |
securitylab.github.com
|
|
| | | | | In this article, well discuss some common security malpractices for GitHub Actions and workflows, and how to best avoid them. Our examples are based on real-world GitHub workflow implementation vulnerabilities the GitHub Security Lab has reported to maintainers. | |
| | | | |
xvnpw.github.io
|
|
| | | | | Introducing the Fabric Agent Action - a GitHub Action that automates complex workflows using AI-powered agents and Fabric Patterns. | |
| | | | |
werat.dev
|
|
| | | | | Benchmarks are often underestimated and don't get the same attention as tests. However "performance is a feature" and when something is not tested it might as well be just broken. If the performance is not measured/tracked regressions are inevitable. Modern tooling makes it really easy to write benchmarks. Some languages have built-in support, for example, Rust comes with cargo bench (docs) and Go has go test -bench (docs). For C++ there is google/benchmark - not as streamlined as having it built into the language infrastructure, but still definitely worth the effort. | |
| | | | |
williamdurand.fr
|
|
| | | This is Part 2 of a malware analysis I did last week. This time, it was not an exercise! | ||
