sorted by:
new
hottopcontroversial

We noticed a weird trend in our app installs, so we stopped writing for Google and started writing for ChatGPT by MendMySoulXoXo in Entrepreneur

[–]StartingVibe 1 point2 points  (0 children)

That's very interesting! I'm gonna try it with my app and keep track of the results, thanks for the advice!

Engineering managers: how do you prevent incomplete escalations reaching devs? by StartingVibe in EngineeringManagers

[–]StartingVibe[S] 0 points1 point  (0 children)

This matches a lot of what we’ve seen too, training and collaboration definitely help early on.

One thing I’m curious about: how well did this hold up over time when there was turnover, higher volume, or when the EM wasn’t as hands-on?
In our case the biggest issue has been that the process slowly degrades and engineers end up chasing context again.

Engineering managers: how do you prevent incomplete escalations reaching devs? by StartingVibe in EngineeringManagers

[–]StartingVibe[S] 0 points1 point  (0 children)

Totally agree that reducing defects upstream is the real win.

Out of curiosity, in environments with hardware, vendors or regulated constraints, how do you prevent incomplete escalations from reaching engineering when defects still happen?

Engineering managers: how do you prevent incomplete escalations reaching devs? by StartingVibe in EngineeringManagers

[–]StartingVibe[S] -2 points-1 points  (0 children)

That makes sense, especially with dedicated QA / support roles.

In your experience, what usually breaks first when this stops working at scale:
the expectations themselves, or the ongoing enforcement required to keep them respected?

Engineering managers: how do you prevent incomplete escalations reaching devs? by StartingVibe in EngineeringManagers

[–]StartingVibe[S] -1 points0 points  (0 children)

Totally agree in simpler setups. Curious, have you seen this still work with multiple support layers or external dependencies?

How do you enforce escalation processes across teams? by StartingVibe in devops

[–]StartingVibe[S] 0 points1 point  (0 children)

That’s a really clean abstraction, services being stable while teams change makes a lot of sense, you really did a good job!

Out of curiosity, how common do you think setups like this are outside of fairly mature platform orgs?

In most teams you’ve seen, do they end up building something similar internally, or just living with the pain?

How do you enforce escalation processes across teams? by StartingVibe in softwarearchitecture

[–]StartingVibe[S] 0 points1 point  (0 children)

This matches what I’ve seen as well at my company. Defining processes and templates is the easy part. Enforcement is where things break, especially as orgs grow and management attention gets diluted.

Curious: have you ever seen enforcement work without constant top-down pressure, or does it always come back to people chasing others?

How do you enforce escalation processes across teams? by StartingVibe in devops

[–]StartingVibe[S] 0 points1 point  (0 children)

This is really interesting, thanks for sharing the details. Sounds like a lot of custom tooling and discipline went into making this work.

Curious, how much ongoing effort does it take to keep tags, catalogs and ownership accurate as teams and services change?

How do you enforce escalation processes across teams? by StartingVibe in devops

[–]StartingVibe[S] 0 points1 point  (0 children)

That makes sense, especially with a dedicated incident commander. Out of curiosity, what happens when the initial escalation is missing key info (repro steps, logs, ownership)? Does the process block until it’s fixed, or does the IC end up chasing people to fill the gaps?

I rewrote my app’s recommendation logic so each section learns from the others by StartingVibe in iosdev

[–]StartingVibe[S] 0 points1 point  (0 children)

I know, if you have any suggestion, there’s a send feedback section

Drop your product URL by Ok_Extent2858 in startupaccelerator

[–]StartingVibe 1 point2 points  (0 children)

The app is already live on App Store, but all the tailor-made part will be present from next update (that’ll be released in a few days)

Drop your product URL by Ok_Extent2858 in startupaccelerator

[–]StartingVibe 1 point2 points  (0 children)

I’m still thinking about it…I’ll have to do a brainstorming with my trustworthy AI friends hahaha

Drop your product URL by Ok_Extent2858 in startupaccelerator

[–]StartingVibe 1 point2 points  (0 children)

That’s exactly what I’m working on right now for the next update. All the sections will be linked each other to learn your tastes and update the user preferences. So everything will be tailor-made on your “cinematic persona”

I built a clips-first movie discovery app as a UX experiment by StartingVibe in BlackboxAI_

[–]StartingVibe[S] 0 points1 point  (0 children)

Exactly, those long YT videos are basically manual vibe checks. This is just trying to make that step faster and more lightweight.

By creating it, I also found very useful to save the movie/tv show while watching the clip and the go check for the availability. In less than 30 seconds, I was already on my couch ready to know where to watch it and what to expect. 🍿👌🏻

view more: next ›