In recent weeks, I used AI to build a dashboard I’d have typically requested and would need to be prioritized by our data analytics team.

I woke up to multiple messages that it was down this morning from people who’re now using it for their work.

So I’m now oncall for a dashboard as a PM lead. 🤔

This touches on two themes from my recent posts

1. PMs vibe coding production features means you have to decide what’s your on call strategy when it goes down. Is the PM being woken up by PagerDuty?

2. Is working on dashboards as a PM a side quest or part of the main quest of my role? Do the boundaries of my role still make sense in an AI native world?

@carnage4life these are interesting questions indeed.

As an IC and on call for production, I would be very annoyed to be on call for vibe coded feature that I haven't seen/reviewed in any way.

Currently, we limit the vibe-coding to prototyping. if the prototype passed the bar (answer the specific questions we had or confirm the feature value) it goes back to dev to either be done "right" (with coding assistant but not vibe coding). It might be slightly slower but ensure we control the prod.

@gdupont @carnage4life that is a good approach
@antonio @carnage4life
;-)
Too soon to tell
But that's the approach that allows to keep my sanity levels on check (I'm no more or less 🤪 than before)
@carnage4life with great power comes great responsibility. Be careful how many jobs you take on just because you can.
@carnage4life Very much the same vibe as open source development. A gift inadvertently becomes a responsibility. I think the same rules apply — set boundaries and stick to them.
@carnage4life The vibe support question.
@carnage4life I wonder if we start to move to sharing prompts instead of code/url and software becomes more personal?
@carnage4life just like when the word processor entered the workplace, in which the company managing director became the typing pool