Thanos
@thanos-in-matrix.bsky.social
🐛I know nothing🦋
🐸Notes and thoughts 🌿
🐸Notes and thoughts 🌿
- Story estimates are guesses — don’t count on them. Count on feedback
- Know yourself to serve better
- Leadership: contribute, influence, take responsibility, be available
- Architecture supports agility
- Architecture is a living set of decisions
- Know yourself to serve better
- Leadership: contribute, influence, take responsibility, be available
- Architecture supports agility
- Architecture is a living set of decisions
August 5, 2025 at 4:46 PM
- Story estimates are guesses — don’t count on them. Count on feedback
- Know yourself to serve better
- Leadership: contribute, influence, take responsibility, be available
- Architecture supports agility
- Architecture is a living set of decisions
- Know yourself to serve better
- Leadership: contribute, influence, take responsibility, be available
- Architecture supports agility
- Architecture is a living set of decisions
- Architecture guides energy towards useful outcomes
- We reach autonomy when our work is aligned with our values
- Generalists are amplified with AI
- One diagram, one message
- We reach autonomy when our work is aligned with our values
- Generalists are amplified with AI
- One diagram, one message
August 5, 2025 at 4:46 PM
- Architecture guides energy towards useful outcomes
- We reach autonomy when our work is aligned with our values
- Generalists are amplified with AI
- One diagram, one message
- We reach autonomy when our work is aligned with our values
- Generalists are amplified with AI
- One diagram, one message
Traffic patterns considerations
- Request-based billing is recommended when incoming traffic is sporadic, bursty or spiky.
- Instance-based billing is recommended when incoming traffic is steady, slowly varying.
cloud.google.com/run/docs/con...
- Request-based billing is recommended when incoming traffic is sporadic, bursty or spiky.
- Instance-based billing is recommended when incoming traffic is steady, slowly varying.
cloud.google.com/run/docs/con...
Billing settings for services | Cloud Run Documentation | Google Cloud
cloud.google.com
August 2, 2025 at 6:50 AM
Traffic patterns considerations
- Request-based billing is recommended when incoming traffic is sporadic, bursty or spiky.
- Instance-based billing is recommended when incoming traffic is steady, slowly varying.
cloud.google.com/run/docs/con...
- Request-based billing is recommended when incoming traffic is sporadic, bursty or spiky.
- Instance-based billing is recommended when incoming traffic is steady, slowly varying.
cloud.google.com/run/docs/con...
Eventually, you prove the bug is on the vendor’s side. They acknowledge it and take months to ship a firmware fix that might solve it.
Meanwhile, your team owns the problem and your users have a bad experience.
Meanwhile, your team owns the problem and your users have a bad experience.
July 14, 2025 at 4:18 PM
Eventually, you prove the bug is on the vendor’s side. They acknowledge it and take months to ship a firmware fix that might solve it.
Meanwhile, your team owns the problem and your users have a bad experience.
Meanwhile, your team owns the problem and your users have a bad experience.
Consider an integration with a poor hardware vendor, the pain spreads. Users face issues and contact support. Support escalates to engineering, who go through logs, build dashboards, and gather evidence.
July 14, 2025 at 4:18 PM
Consider an integration with a poor hardware vendor, the pain spreads. Users face issues and contact support. Support escalates to engineering, who go through logs, build dashboards, and gather evidence.
> Given the global nature of quota management, this metadata was replicated globally within seconds. This policy data contained unintended blank fields.
status.cloud.google.com/incidents/ow...
status.cloud.google.com/incidents/ow...
Google Cloud Service Health
status.cloud.google.com
June 16, 2025 at 9:08 AM
> Given the global nature of quota management, this metadata was replicated globally within seconds. This policy data contained unintended blank fields.
status.cloud.google.com/incidents/ow...
status.cloud.google.com/incidents/ow...
> The issue with this change was that it did not have appropriate error handling nor was it feature flag protected. Without the appropriate error handling, the null pointer caused the binary to crash.
> If this had been flag protected, the issue would have been caught in staging.
> If this had been flag protected, the issue would have been caught in staging.
June 16, 2025 at 9:08 AM
> The issue with this change was that it did not have appropriate error handling nor was it feature flag protected. Without the appropriate error handling, the null pointer caused the binary to crash.
> If this had been flag protected, the issue would have been caught in staging.
> If this had been flag protected, the issue would have been caught in staging.
Control plane components can be run on any machine in the cluster. However, for simplicity, setup scripts typically start all control plane components on the same machine, and do not run user containers on this machine
June 3, 2025 at 8:53 PM
Control plane components can be run on any machine in the cluster. However, for simplicity, setup scripts typically start all control plane components on the same machine, and do not run user containers on this machine