Great OSS projects today; product diversity one would say. Great ideas, and tastes, come to life. Some are left with few stars, unnotarized apps. How do you safely run these? The least one can do is an LLM security reddit on a fork, and then adapt it to their taste.

Having agents pulling a base OSS software and tailoring it to your needs will be the most efficient way to solve your software need. We don’t need to reinvent the wheel each time. Inference costs in time and energy; retrieval is cheap.

LLMs bring the greatest era in DIY, until the DIY becomes another prompt materializing itself

I've recently taken the Product Owner role. Stop bringing me solutions. Bring me problems! My job isn't to enrich endpoints. It's to filter noise, expose real pain, and align effort with impact. No problem statement ➡️ No work.

Probation works both ways. The company assesses your performance, and you assess the company.

Agile Meets Architecture, Berlin 2025 TL;DR from my notes

Wisdom from the BODY WORLDS exhibition bodyworlds.com/city/munich/

If you have Cloud Run workloads, consider the pricing model too. For high req rate, and consistent load -> instance base pricing. For occasional workload -> request based pricing.

A common thinking pattern I see with more junior developers is focusing on the latest tools or standards to make an impact. A senior starts with the organization's needs and identifies real problems, evaluates tools, and chooses the right one for the job. Focus on problems, not solutions!

Every external system you integrate with, hardware/software, becomes a point of risk. One unreliable/problematic partner means worse customer experience and more internal workarounds, monitoring, and communication. This doesn’t scale linearly.

SLI = What you measure (e.g., % of 5XX errors) SLO = The target (e.g., <5% errors in 900s) SLA = The promise to others (e.g., 99% uptime) You set SLOs stricter than SLAs to stay safe. You set alerts to catch drift before you fail the target.

tldr; Google updated their API quota with an invalid config, the change was propagated in different locations and customers were getting 503s. status.cloud.google.com/incidents/ow...

Things I want to write about but currently lack the time: - GCP Log Explorer Optimization - Manual Blue/Green GKE Node Pool Update - Elevation of Privilege Game - Exercise: Build your own Product Owner - Balancing Documentation vs Code as Documentation

In Kubernetes, control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new pod when a Deployment's replicas field is unsatisfied).

Don’t ask people what they expect from a presentation. They don’t know. A story is more powerful than pictures alone.

The certificate chain must start with the sender's certificate (server/client cert). Each subsequent certificate must directly certify the one preceding it. Server/Client Certificate → Intermediate CA(s) → Root CA ( omitted if it's part of the trust store) datatracker.ietf.org/doc/html/rfc...

If I can recommend storytelling to you for any reason at all, it would be that storytelling helps you realize that the biggest, scariest, most painful or regretful things in your head get small and surmountable when you share them with two, or three, or twenty, or three thousand people.Matthew Dicks

The best engineers aren’t the ones who know everything but rather the ones that know how to learn anything.

“To hone your craft is to honor creation. It doesn’t matter if you become the best in your field. By practicing to improve, you are fulfilling your ultimate purpose on this planet.” — Rick Rubin, The Creative Act

The `compact()` function in Terraform is handy when iterating over potentially null resources — e.g., if you’ve removed a resource that another depends on. `compact()` removes any nulls from a list. developer.hashicorp.com/terraform/la...

compact - Functions - Configuration Language | Terraform | HashiCorp Developer

The compact function removes null or empty string elements from a list.

developer.hashicorp.com

Deleting secrets from a secret store is a common root cause of incidents. To ensure that secrets are not in use, enable audit logs and check whether they have been accessed recently. In Google Cloud, Data Access Audit Logs are disable by default due to the logging amount that they can produce.

show, don't tell

After a database migration, check that hardware utilization stay within reasonable limits. Watch for spikes or high average CPU — could mean you forgot an index. Assuming an SQL DB, and proper alerting for resource utilization!

When a Terraform-managed resource is modified outside of Terraform, it may try to replace it on the next run. The ignore_changes meta-argument tells Terraform to ignore specific attributes of the resource. developer.hashicorp.com/terraform/la...

The lifecycle Meta-Argument - Configuration Language | Terraform | HashiCorp Developer

The meta-arguments in a lifecycle block allow you to customize resource behavior.

developer.hashicorp.com

If you need to rename a resource in Terraform, it will try to recreate it by default. But with the `terraform state mv` command, you can map the new name to the existing remote object in the state. developer.hashicorp.com/terraform/cl...

terraform state mv command reference | Terraform | HashiCorp Developer

The `terraform state mv` command changes bindings in Terraform state so that existing remote objects bind to new resource instances.

developer.hashicorp.com

In tech teams, as in other constellations of collaboration, juniors bring new perspectives — untainted by the complacency of long-term expertise. They see problems in ways that experts might overlook.

@gerritbeine.bsky.social on Self-organisation at @amaconf.bsky.social ⏳ A couple of takeaways 👇🏼

Michael Mahlberg on Leadership at @amaconf.bsky.social 🌱 A couple of takeaways 👇🏼