Ongelmakuvaus #3
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: MrTohtori/NepsyDay#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Karkeesti:
Phase 1 — Establish the Contract with Reality
This is where 90% of startups skip and later die.
You need four documents before meaningful coding begins.
1️⃣ Problem Definition (A3-style)
Not “what we’re building”, but what failure in the world we’re fixing.
Create a 1–2 page doc with:
Section Purpose
Who hurts Which users feel pain
What hurts The concrete failure they experience
How often Frequency
How severe Cost, risk, frustration
What they do now Workarounds
Why those fail Gaps
Example (bad):
“We’re building a productivity app.”
Example (good):
“Freelancers lose 3–6 billable hours per week because client communication is fragmented across email, WhatsApp, and Slack.”
Until you can write this with numbers, you don’t have a product — you have a vibe.
Tässä päiväämätön muistiinpano arviolta 8-10 vuoden takaa. Daily Checklist project.
Huomioitavia toiminta- ja tulkintatapojen prosesseja