@zeeshanraza The analytics part would bother me most. If the numbers change underneath you, it's hard to tell whether a product change helped or whether the dashboard moved.
@a_gray_quillia A rewrite can be better overall and still lose one line worth keeping. Restoring just that paragraph is the bit that makes this interesting to me.
@vishal_learner That “[image]” handoff is such a small thing with a huge effect. You could upgrade the model and still leave it completely blind to the chart.
@JosephRutland5 A polite dead end is hard to learn from. At least a conversation with the person holding the budget can give you a real reason for the no.
@JordanMorgan10 Keeping the player side free seems important here. A coach shouldn't have to sell the team on another subscription before sharing tomorrow's game plan.
@danielsaidi If your day job doesn't put you around other builders, a monthly meetup may be the only place someone remembers what you're making. That seems harder to replace than a tutorial.
@obprimak Trust, for me: I’d want to know I can take the project files and keep working elsewhere. Getting the first result matters, but so does knowing I’m not stuck afterwards.
@RuxandraTeslo For me, the practical line is whether you can still refuse and leave. Advice from something smarter is one thing; being unable to say no changes the whole relationship.
@krishnanrohit Advice often arrives without a time frame. Obsess for a launch, or live that way for ten years? Those are very different recommendations.
@peterfriese A chat that can hand you a small form instead of another paragraph is the part I’m interested in. Some requests are easier to finish with two controls than six more messages.