PinnedInCode Like A GirlbyHanna Kamyshanska·Mar 6Technical DebtWhat Pipes Behind the Wall Taught Me About CodeA response icon2A response icon2
InBootcampbyHanna Kamyshanska·16h agoHow I decided what my app wouldn’t doA raven, a lost video and a garden bed can teach us about two frameworks: Jobs to Be Done and the 5 WhysA response icon1A response icon1
InNo TimebyHanna Kamyshanska·Oct 20What Houseflies Know About Getting Unstuck in Your CareerOn saccades, professional pivots, and the courage to finally jump
InCode Like A GirlbyHanna Kamyshanska·Oct 12I told my mom not to touch her phoneA story about trust, data, and a clock tickingA response icon2A response icon2
InShare Your CreativitybyHanna Kamyshanska·Jun 28Freshman EyeWhy your brain lies to you mid-drawing — and three ways to force the truth outA response icon3A response icon3
InCode Like A GirlbyHanna Kamyshanska·Jun 5What Nobody Tells PhDs About AgileConsider This Your Babel Fish
InCode Like A GirlbyHanna Kamyshanska·May 13I ran design sprint solo, replacing the team with AIIt’s a sophisticated form of Rubber DuckingA response icon1A response icon1
InNo TimebyHanna Kamyshanska·May 2Why your TODO tasks won’t die (and how to kill them)Borrowing computer algorithms to fix procrastination
InBootcampbyHanna Kamyshanska·Mar 18Defining “Good Enough” Is a Million Dollar ProblemWhy ML models never feel done
InBootcampbyHanna Kamyshanska·Mar 5The thing that isn’t a threatHow disruption kills companies that do everything right