awesome-cloudnative-trainings
Awesome Trainings from Cloud Native Computing Foundation Projects and Kubernetes related software (by joseadanof)
guides
By readme
Our great sponsors
| awesome-cloudnative-trainings | guides | |
|---|---|---|
| 2 | 112 | |
| 1,515 | - | |
| - | - | |
| 3.9 | - | |
| 7 months ago | - | |
| - | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-cloudnative-trainings
Posts with mentions or reviews of awesome-cloudnative-trainings.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-16.
- Collection of free cloud training resources
-
Episode 93: myNewsWrap – SAP and Microsoft
Awesome Cloud Native Trainings
guides
Posts with mentions or reviews of guides.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-28.
- What we talk about when we talk about 'root cause'
- The case for using Rust in MLOps
- Using code as documentation to save time and share context
- Publishing your work increases your luck
-
Pest-Driven Development: Learning, Iterating and Project Planning
Write a more complicated test later. Or refactor the test later. When you're in the moment, you want a test that works. Avoid hard coded values in completed tests, but use them when you're making sure your test doesn't break the very time you write it. A failing test is the starting point of the last decision you made, not the final product. Even if the imaginary people who are going to make fun of your code and call you stupid (ignore this if you're not relating, but if you are read this or watch it) are looking at your public github repo, they're not going to your test suites first. That would be insane. So you can be clunky at first.
- Formatters, linters, and compilers: Oh my
- Two years into this career and already frustrated and burnt out (rant)
- Treat accessibility issues as bugs, not feature requests · GitHub