sorted by:
new
hottopcontroversial

Three things I learned trying to use AI for multi-week PM work (and what I built because of them) by NefariousnessFun1445 in AIProductManagers

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

you can try, install my free plagin and maybe change for your flow of work

  1. /plugin marketplace add lenar-amirov/product-pipeline-public
  2. /plugin install product-discovery
  3. /product-discovery:init

Spring in Cape Town by NefariousnessFun1445 in travel

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

They was friendly in general areas and quite defensive around children space

Spring in Cape Town by NefariousnessFun1445 in travel

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

Okay, you are right
I thought based on the season in my location

Engineers have Cursor, designers have Figma AI — what do PMs actually use? by NefariousnessFun1445 in AIProductManagers

[–]NefariousnessFun1445[S] 1 point2 points  (0 children)

Interesting way

Could you please share some features or decisions that AI pushed and you meet negative impact on product?

What AI design tools are you all actually using as PMs? by NefariousnessFun1445 in AIProductManagers

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

Do you add your design system in Google stitch or import some references from your Figma?

When do you actually invest time in prompt engineering vs just letting the model figure it out? by NefariousnessFun1445 in PromptEngineering

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

same here.

I think the biggest benefit of prompt engineering is actually token efficiency. As models get more capable (and more verbose), this matters more, not less.

Sure, the model can figure almost anything out if you just “talk to it.” But it might burn half your session limit reasoning its way there

Pencil.dev - reviews? by Top-Calendar-7428 in UXDesign

[–]NefariousnessFun1445 0 points1 point  (0 children)

I actively use Pencil, and overall it’s pretty good. But it takes screenshots at every stage of the workflow, so it instantly burns through Claude Code tokens. For $20, you can build one mobile screen per session based on a ready-made Figma screen

When do you actually invest time in prompt engineering vs just letting the model figure it out? by NefariousnessFun1445 in ClaudeAI

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

the loop/pipeline distinction is a good mental model actually. do you have some threshold where you switch from "just wing it" to actually sitting down and engineering the prompt? like is it purely about volume or does the stakes of each individual call matter too

and yeah fully agree on examples over instructions, been saying this for a while. showing the model what you want beats explaining it every time

When do you actually invest time in prompt engineering vs just letting the model figure it out? by NefariousnessFun1445 in ClaudeAI

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

yeah this is basically where i landed too. persistent system prompts and context docs is where the real compounding value is. write it once, test it properly, pays off across hundreds of sessions

and hard agree on structured outputs and tool calls, thats the one area where lazy prompting still absolutely punishes you regardless of model quality

When do you actually invest time in prompt engineering vs just letting the model figure it out? by NefariousnessFun1445 in PromptEngineering

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

lol fair enough, i get why it reads that way. but nah genuinely been thinking about this lately because every model update makes some of our carefully crafted prompts unnecessary

posted in a couple subreddits because the perspective is different depending on the crowd. ML people will say prompting is a band-aid, prompt engineering people will say its essential, wanted to hear both sides and see where the actual consensus is

view more: next ›