| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| We Learn Systems by Changing Them |
| |
| |
Michael C. Jackson, a systems scientist, contrasts action research with old-style hard science, which tries to study a system from the outside. In the social world, there is no outside: we participate in the systems we study.
Jackson continues: To ensure scientific rigor, this demands a close analysis of the initial situation, clearly documented action to bring about desired change and continuous monitoring of effects, and careful analysis of the end results of the action.
This is also noticeable in code: when it comes to an existing codebase, we get a handle on it by changing stuff. |
|
| |
|
| |
|
| |
| Notes on an Observability Team |
| |
| |
An Observability Team should be a compliment to, not a replacement for, a strong Observability culture with an engineering team.
It's also an easily misunderstood team within a company. Not every company is going to need an Observability team, but at a certain scale it becomes a reasonable investment or full time focus.
The goal should be that the benefits of Observability tools get out of the box and get useful to your organization . |
|
| |
|
| |
|
| |
| Using the Alpine Docker image |
| |
| |
| A detailed look at how to use the Alpine Docker image |
|
| |
|
| |
|
| |
| Prometheus Monitoring. Easy Explained. 🔰 |
| |
| |
| An introduction to Prometheus for those who want to start learning it. |
|
| |
|
| |
|
| |
| Can writing code be emotional? Google Cloud’s Kelsey Hightower says yes |
| |
| |
| “Creating good software is very emotional.” Googler Kelsey Hightower, Google Cloud's Principal Developer Advocate, shares how he champions a rarely-noticed aspect of engineering to build trust and help customers succeed. |
|
| |
|
| |
