currently: replying more than posting
how i grow my network
not by posting more. i ship things, show them working, and talk to the people building right next to me. most of what's below comes from studying what worked for builders a step ahead of me.
the rules i run:
- show it working. a demo with numbers beats an announcement. $41.09 vs $42.32, with 80 lines of python against 900, says more than any launch post.
- build where the team reposts builders. i pick tools whose teams share what people make with them. a good demo on their stack reaches everyone already using it.
- test new models on day one. when a model drops, i run it on something real that day and post what broke. a week later it's just another take.
- give the work away. the code, the prompts, the repo behind the demo. people remember who handed them something useful.
- tell my own story. what i built, where it broke, what i'd do differently, in first person. reposting company news doesn't make anyone know you.
- fewer, stronger posts. one post with a real result beats a week of daily filler. if i can't say it in one line, it isn't ready.
- reply like a peer, then dm. substantive replies to people at my level, 100 to 10k followers: a repo, a counterexample, a number. after a few real replies, a dm isn't cold.