great for collaboration PlantUML - great for documentation Figma - for UI collaboration with designer Miro/FigJam - for group brainstorming ... use whatever works for you -
-> do you use -> yes -> review product page (not in stack) -> do you use -> no -> search (alternative) -> review product page (in stack) -> still using? -> yes -> ask for tip -> add tip product page (in stack) -> still using? -> no -> search (alternative) -> review . Showcase 1 (end to end test scenarios)
dirty code in empty file * Imagine a perfect world for this code 0 Delete file # If solution is 1 ➡ think of something else ➡ If solution is ✅ ➡ use ideas in project ✍ Code Sketch
using paper” “I can't draw, I don't have the skills.” 5 Paper is too small, I want infinite canvas 6 Paper is permanent, I want to re-arrange, update 7 I want to share with multiple people and collaborate
rather than at producing shippable product. Sometimes we can't estimate until the development team does some actual work to resolve a technical question or a design problem.” - WikipediA Spike (software development)
rather than at producing shippable product. Sometimes we can't estimate until the development team does some actual work to resolve a technical question or a design problem.” - WikipediA Spike (software development)
code in a Pull Request ) Review the solution * Close Pull Request without merging # If solution is 1 ➡ Discuss new solution ➡ If solution is ✅ ➡ Open new Pull Request & Spike
It will waste too much time.” “You don't need a "spike" to show that your solution isn't good.” “Why do you need to throw away the code?” “Isn't this a Prototype, MVP, PoC?”
It will waste too much time.” “You don't need a "spike" to show that your solution isn't good.” “Why do you need to throw away the code?” “Isn't this a Prototype, MVP, PoC?” Don't do it for every feature. Do it when you are not confident how to solve a problem. ;
It will waste too much time.” “You don't need a "spike" to show that your solution isn't good.” “Why do you need to throw away the code?” “Isn't this a Prototype, MVP, PoC?” Because of "Tunnel vision" and "sunk cost fallacy" ;
It will waste too much time.” “You don't need a "spike" to show that your solution isn't good.” “Why do you need to throw away the code?” “Isn't this a Prototype, MVP, PoC?” Because it is usually a mess. I don't delete it, I just copy parts I need into a clean new PR ;
It will waste too much time.” “You don't need a "spike" to show that your solution isn't good.” “Why do you need to throw away the code?” “Isn't this a Prototype, MVP, PoC?” Kinda - yes. The difference is in how big it is, who is meant for team or external, and do we ship it in production. -
It will waste too much time.” “You don't need a "spike" to show that your solution isn't good.” “Why do you need to throw away the code?” “Isn't this a Prototype, MVP, PoC?”
rstankov
ks91
cheng_wei_chen
ysuzuki
ezaki
findy_eventslides
stefafafan
personabb
gotok365
junki
kworkdev
sonic
kairim0
mraible
.png){kind=avatar}
helenjbeal
rkendrick25
eileencodes
moore
skoyamalab
letsgokoyo
tammyeverts
nwiizo
leimatthew05
aleyda
soudai
