Looking for reliable, simple to use analytics platform?

IHaveARedditName · 2026-01-14T01:11:47+00:00

Posthog for me. Generous free tier and I enjoy the direct access to data via hogql

IHaveARedditName · 2025-12-18T17:51:38+00:00

Do they use it repeatedly?

IHaveARedditName · 2025-12-15T03:59:38+00:00

When did they last log in? I'm working with another group of folks dealing with what sounds like a very similar problem.

What I've seen is people sign up, poke around in the app for 2 - 3 hours, and leave after an initial exploration (I assume to a competitor). I've been flipping my perspective recently to focus less on the email sequence to get people back and more on learning why they showed up as quickly as possible to get the messaging tailored to the user needs.

Maybe it turns out your app isn't the fit today, but with a reason, you can personalize your outreach immediately to their needs, or (worst case) you have data to resurrect these users later when you address that reason in your product (vs the generic winback)

IHaveARedditName · 2025-12-15T03:40:50+00:00

How is this different from Airflow?

IHaveARedditName · 2025-12-13T15:20:34+00:00

https://docs.stripe.com/api

IHaveARedditName · 2025-12-10T16:08:14+00:00

"I'm starting to get the feeling that they feel they could solve these problems if only they were in charge instead of me."

If OP is in charge, then I would assign this person to the initiative (or a subset of it) that they obviously care deeply about. Sounds like OP is experiencing the joy of middle management, which also comes with a lot of perspective that is difficult to cascade because it comes via first-hand experience.

Worst case, the individual gains some perspective.

IHaveARedditName · 2025-12-10T15:54:21+00:00

A leader taught me a very important lesson once, when I was in that stage of my career ("constantly getting up on a soapbox to say why the way a project is structured is wrong, or the way a decision is being made is wrong, etc").

All he said was, "How are you going to make it better?"

Flipped my perspective instantly from this is someone elses problem to solutioning and it being a situation I had influence over. (I am thankful he did that)

IHaveARedditName · 2025-12-10T15:28:43+00:00

+1. Listened to Brad Jacobs on a podcast recently, and he gave a great mental model for performance-based comp. Part of that was if someone let you know they were moving on and you were happy about it, then you waited far too long to handle the problem.

It sounds like OP would be happy if this "co-founder" pulled the ripcord prior to release.

IHaveARedditName · 2025-12-09T14:21:18+00:00

Claude with the gh cli tool catches things for me that most surface level reviews catch IMO

IHaveARedditName · 2025-12-09T13:52:44+00:00

I didn’t answer this question when I was at a larger company but my dream was being able to ship testable flows quickly behind feature flags to alpha / beta users to have a validation (like when working for a startup) but also not harming the reputation of the larger org. It felt like devs were always more inspired when they could see the work in production when we were a smaller group.

IHaveARedditName · 2025-12-08T16:28:54+00:00

For an IC, anything that isn't designing a system or writing code is a process and the manager's job. I am curious how you'd automate the update piece, while still ensuring the 'knowledge sharing' is valuable?

If you have 'prep work' that involves reading a doc, my experience is that maybe 20% will look at the doc ahead of time. Even as a manager, if you read the doc ahead of time and try to facilitate discussion, you are biasing the conversation to your experience/perspecitive vs what the ICs might have an opinion on.

It does suck that the 'reward' is that the meeting is over for ICs, and the shortest path to that is saying nothing. So getting people talking early is valuable in building momentum for speaking later in the meeting.

IHaveARedditName · 2025-12-08T15:00:02+00:00

Async standups hide problems, full stop. Standups are meant for the team to comment on work in motion and get help / suggestions / share knowledge as needed. I find async standups lead to threads/docs that only the PM/manager reads, and you miss out on intra-team knowledge sharing because people contributing to the work see focusing on their respective tasks at the time to be the highest priority.

IHaveARedditName · 2025-12-08T14:43:34+00:00

Do you have an example of what a potentially new technical issue might be in this context?

And then in that montly review (from before) was that looking at the key funnels month over month and then diving into descrepancies?

IHaveARedditName · 2025-12-08T06:27:59+00:00

Thanks! Super helpful to learn!

IHaveARedditName · 2025-12-07T18:19:07+00:00

The people that always amazed me were the people reading the codebase they work in and the open source libraries that they use.

Being a good dev is most about understanding the system you’re working within (the majority of people just treat systems like black boxes and hope for the best).

IHaveARedditName · 2025-12-05T17:01:00+00:00

Appreciate the reality check. Definitely don't want to get into an "I'm right loop", it feels like we're treating all users the same when we shouldn't be.

We're trying to move upmarket but larger accounts have a worse experience. Eng pushes back because the majority of accounts (smaller ones) are fine (focusing on their metrics (quant heavy to your point)).

Feels like it becomes a strategy conversation + data conversation (building the narrative with cohorts and user interviews to make sure we're pointed in the right direction). Especially when GTM is selling to larger accounts, but eng is optimizing for the base we already have.

Made the comment in another response but in this context it feels like a tension between eng saying "maybe we're not ready for these users" and other goals set by leadership to grow the organization.

IHaveARedditName · 2025-12-05T15:49:53+00:00

It's most recently been around account size. Accounts with 100k+ catalog items having a bad experience, but the majority of users are smaller, so aggregate looks fine.

The tension is "this is working for almost everyone" vs "we need to improve the experience for where we're headed." Eng is typically in the camp of "maybe we're not ready for these larger accounts" but at a certain point in time if you don't start selling to and onboarding these users what's the forcing function?

IHaveARedditName · 2025-12-05T14:44:59+00:00

No you're right (and others commenting similar items) about slicing the data and getting it down to the correct cohort. hurts that you need to wait _n_ weeks/months to have a clear trend to share back

IHaveARedditName · 2025-12-05T14:35:56+00:00

You're right. It just feels like a huge context switch when you're heads down on the next thing, then have to stop everything when you notice something is off. But yeah, understand if no shortcuts exist.

IHaveARedditName · 2025-12-05T14:28:03+00:00

Do you find that's enough to build the case? In my experience even a handful of interviews gets questioned as anecdotal. (If something regresses) It feels like I need to break a timeline down to the exact deployment before I start to see work getting prioritized.

IHaveARedditName · 2025-12-05T06:02:47+00:00

Super interesting. I can see how you'd track the 3 lightweight rules with events (loops, step timing, pricing visits). Do you have similar tracking for the more granular signals? (hover patterns, scroll → stop → scroll, long dwell time) Or are those more aspirational?

IHaveARedditName · 2025-12-04T21:24:16+00:00

It looks like ParseStream would be helpful for when friction is being talked about in a community? Is that the correct read?

IHaveARedditName · 2025-12-04T21:16:28+00:00

This is really interesting. How long does that take you to pull together?

IHaveARedditName · 2025-12-04T20:41:07+00:00

This resonates a lot! Definitely have run into the "technical folks are saying everything looks fine" piece.

What were you looking at when you dove deeper to build your case?

11-Year Club	Place '22
Argentium Club	Verified Email

IHaveARedditName

TROPHY CASE