mgbmgb

4 ms·

1. 1.▲
   Kubernetes Pod Doctor(codereliant.io)

   2 points by mgbmgb 3y ago|0 comments
2. 2.▲
   The Tragic Race Condition(codereliant.io)

   2 points by mgbmgb 3y ago|0 comments
3. 3.▲
   Problem is just 14 years away(codereliant.io)

   4 points by mgbmgb 3y ago|1 comments
4. 4.▲
   Chat with Your Kubernetes Cluster(codereliant.io)

   3 points by mgbmgb 3y ago|0 comments
5. 5.▲
   by mgbmgb 3y ago

   There is also handy ripgrep-all, which wraps ripgrep and works with things like sqlite, docx, etc
6. 6.▲
   by mgbmgb 3y ago

   from his wiki "now generally identifies himself as a composer rather than a software developer or engineer" - that's the goal!
7. 7.▲
   by mgbmgb 3y ago

   Sys Admins -> DevOps -> SREs -> Platform engineers -> ? What's next?
8. 8.▲
   by mgbmgb 3y ago

   This is the way to go. With the recent push towards "more nimble teams" and high output / high velocity there is no place for QA teams to take days to review the releases, so you'd have to bake testability in. Recent exa
9. 9.▲
   by mgbmgb 3y ago

   I wouldn't dismiss the value of automated testing altogether, I think it really depends on the domain. I haven't seen a dedicated QA team in any of my recent companies and all the projects do just fine. With that said, if I were t
10. 10.▲
    by mgbmgb 3y ago

    > Many teams are stuck in the outdated releases You didn't have to call us out like that