0
Challenge · 109Ship It
Portfolio & README
Shipused in ~80% of apps
A hiring manager gives your project about 30 seconds before deciding to open the live demo or close the tab. The README is that 30 seconds. The best code in the world still gets passed over if the README does not sell it.
Core idea. Your portfolio sells outcomes, not code: a few deep projects, each with a working live demo, a screenshot, and a README that says what it is, lets the manager try it, and explains the decisions you made.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
Build the README:
README.md0/6 sections strong
Tap a section to flip it. W = weak, S = strong.
github.com / you / pulseFIRST 30 SECONDS
my-project
// no live demo — manager has to clone and build it
(no screenshot)
Features (what it does)
- stuff - some features
Tech stack + decisions
made with react
What I learned / tradeoffs
(nothing)
Callback likelihood0%
Pass. A title that says nothing, no live demo, no screenshot, and no sense of what you did or why. The manager will not clone an unknown repo to find out. Even good code dies in a weak README.
↑ play a little first, then dig in