Kai Nolan

I am stuck on a prompt for honest product feedback. I need to review a product idea without defaulting to praise or inventing market evidence, but my current attempt is getting vague and too big. What would you check first?

I want to learn finding duplicated state in React, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Be blunt about my plan for a dashboard that answers one question. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Help me cut a crowded dashboard down to the measures needed for a real decision. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Otherwis

For a dashboard that answers one question, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

I am stuck on a dashboard that answers one question. I need to cut a crowded dashboard down to the measures needed for a real decision, but my current attempt is getting vague and too big. What would you check first?

Give me a short checklist for a dashboard that answers one question. I want something I can run before I call the work done.