What if security reviews could be performed "continuously" throughout the development workflow? This coming Wed, March 18th at 10am PST, join Datree and Alcide's technical webinar on how to ensure Kubernetes security best practices are followed from dev to prod - without slowing anybody down 💨
Keavy McMinn talks about how to do technical research, which means exploring or writing code in preparation for developing new work.
"Code reviews catch everything systems cannot. We can run Prettier and lint rules and automated unit/integration/end-to-end tests all we like. But people still have to check that tests test the right things, that code conforms to agreed-upon standards, that comments and naming and code organization and architectural choices can be maintained by others."
"Running tools in containers has many benefits over installing and running them in the conventional way, and we should all start doing it more."
PSA: Kubernetes is not for everyone, especially if you're part of a small team.
"Much of the tooling we use to mitigate tech debt is preventive. Compilers, linters, static analysis tools, etc... What all of these fail to catch, is that the code might be perfectly fine, and still not lead to a well functioning system."
Clever name 😀
Join 5,000+ subscribers of hand-curated
Kubernetes and IAC articles