product1087

Vision what

To me, it's not the time - but the energy. I have about 4 solid "mentally productive" hours in a day that use up the majority of my mental brain energy. Trying to cultivate that energy to do a side hustle after kids are asleep is the real challenge.

Source: 2 kids, 4 and 6.

Product teams painstakingly craft their product specs to ensure they're building the right thing. Unfortunately, the pace of modern product development is so fast that the minute a product spec is written, it’s no longer relevant.

I think the missing insight is that while the final outcome is no longer relevant, the process of reaching the outcome is critical! When I am trying to understand a feature, I find myself spending most my time in the version history of Google Docs (something that team has treated as a secondary feature) – learning how the feature team's collective understanding has evolved. I think Decisions in Fable is a step closer, but not far enough.

One thing I would love to see is product spec editing / collaboration focused around version history. The real "work" of building product specs is building shared context between PM, Eng, UX through evolution of the requirements. However unlike devs who can see the diff of a code file, PM rarely "show their work" – and it makes it hard for everyone to see how the final requirements were reached. I still haven't seen any PM tool with this paradigm in mind.

Hi everyone! PM for Relay here.

Relay is like Zapier for DevOps teams. We're excited to launch our integration with PagerDuty to streamline incident response. Our goal is to make it super simple to compose automation workflows for automatically remediating issues while you figure out the root cause so you can prevent it from happening in the future.

Check it out here: https://relay.sh/blog/pagerduty-and-relay/

On-premises support is in progress. No release date yet. That said, would you need it to be fully self-hosted or would it be viable to have an on-premises agent?

Relay uses Tekton under the hood to run workflows and Knative to process triggers. What kinds of workflows are you thinking about running?

Yep! Relay uses Tekton under the hood to execute the workflows. It actually knative and ambassador to execute the triggers. You can read more about the trigger system here: https://blog.getambassador.io/user-defined-webhooks-in-puppe...

Hi everyone! PM for Relay here.

Relay is an event-driven DevOps platform. It listens to events from 3rd party services like AWS, Datadog, PagerDuty, Jira and more to trigger simpler, smarter workflows that automate tedious tasks. A lot of existing solutions either require a lot of upfront DIY work (AWS Lambda or running your own script) or they weren’t built for DevOps teams (Zapier, IFTTT).

Relay provides out-of-the-box workflows for common use cases like cloud cost optimization, security, incident response and more. If those don't work for you, you can write your own workflow using integrations with dozens of cloud provider services, open source tools and APIs that can be composed together in a YAML-based workflow (yes, I know, more YAML).

Some features we think are interesting:

- Visual execution graph shows exactly what's happening in your workflow run.

- Connections make it simple to authenticate to other services.

- Audit log shows who initiated every workflow run, whether manual or by an external service.

- Human in the loop approvals give you full confidence in your automation.

- Growing community of 30+ open source integrations with AWS, Azure, GCP, Datadog, PagerDuty, VictorOps, Jira, Terraform, Helm, and more.

We also just recently put out a blog post about some pretty novel uses of Knative and Ambassador to create user-generated triggers: https://blog.getambassador.io/user-defined-webhooks-in-puppe...

“Because we want to use it as a database layer. Quite risky ah.”

Singapore represent!

How much, if at all, has the investment from Google in open source projects like Tekton changed at all with the post-Diane Greene leadership?

Senior PM at [Open Source Enterprise Software Company]

Degree in EE --> Internship as Program Manager at Microsoft --> Moved into enterprise products --> Moved to smaller company for larger scope.

Unlike development, it's quite difficult to create small assignments for product managers that is not trivial except at large companies. A key skill in PM is being able to see the complete picture (i.e. Market, Industry, Company, Organization, Team, Person and the interactions between all these different groups) in order to make the right trade-offs for a product.

The best advice I got was from a panel done by Scott Wiltamuth (then PM director of VS) who mentioned that PM is an apprentice discipline. The only way to learn is by sitting and watching someone else who is very good at it and learn from them.