Logan Sullivan's profile on Product Hunt

About

I’m a Junior at the University of Oregon, pursuing a B.S. in Business Administration from the Lundquist College of Business with a concentration in Marketing. My studies allow me to combine my passion for analytics and problem-solving with my love for sports, teamwork, and brand storytelling. This past summer, I had the opportunity to gain experience with Nike Korea, where I was hands on in an international marketing strategy, localization, and consumer insights across the South Korean market. I’ve also been fortunate to work with the University of Oregon Athletic Department, supporting operations that directly impact student-athletes and fans, deepening my understanding of how business and sports connect on and off the field.

Links

Linkdin

Badges

Tastemaker

Gone streaking

Forums

•

1d ago

How do you catch schema drift before it breaks your production database?

There is a mini heart attack moment when you realize your code review says one thing, your migration history says another, and the actual live database is doing something completely different. A single silent failure in a database trigger can take down your whole sign up flow with a vague error message that s impossible to debug on launch day.

Keeping code and production in sync feels like a constant juggling act. What s your go to method for keeping schemas honest automated diffs in the pipeline or just strict pre deployment checks?

p/murror

•

3d ago

What did AI make too easy for you, and what do you wish you'd kept doing by hand?

Every shortcut removes a bit of friction, and some of that friction was doing a job. I'd like to hear which parts of your workflow you handed over and which you took back.

When a tool makes something easy, you rarely notice what the difficulty used to give you. Writing a first draft by hand forced me to decide what I actually thought. Reading user feedback line by line made me notice phrasing that a summary flattens. Writing a spec from scratch was slow, and the slowness was where I found the holes.

•

14d ago

Do churned users actually know why they left, or are they just giving us polite excuses?

Whenever a customer cancels their subscription, our automated exit survey spits out the same reason: Too expensive or Just don't need it right now. For a long time, we took those answers at face value and tried discounting our plans.

It wasn't until a few former users casually admitted on Twitter (after we built a friendly rapport) that the real reason was a lack of a specific integration that we understood the truth. The price wasn't the issue; the missing utility was.

It made me realize that standard churn surveys rarely capture the real psychological barrier to staying.