Skip to main content

Turn your counter program into a post that lands

You built the counter. You tested the happy path. You proved the wrong wallet gets blocked. Today, you turn that private progress into something people can actually see, share, and remember.
Turn your counter program into a post that lands background
View Your Submissions
Challenge

Turn your counter program into a post that lands

ode in a private folder counts for nothing to anyone except you. For the last week you have built an Anchor program, taught your tests to refuse, broken your own code on purpose to prove the suite catches bugs, and written a long-form post that explains it. The work is real. The reach is minimal outside your network. Today you fix that.

The Scenario

You are seven days into Anchor. Your counter program initializes, increments, refuses to be incremented by the wrong wallet, and has a green test suite that you have personally tried to make red. Most Web2 developers who follow you on social media have no idea what any of that means, and the ones who would understand have no idea you did it. The point is not to brag. The point is to leave a public artifact that future you, future collaborators, and future employers can find. People hire and refer the developers they remember seeing build.

The audience you are writing for is split. Some followers know nothing about Solana and need one line that tells them why a counter on a blockchain is interesting. Others write Rust or Anchor every day and will scroll past anything that reads like a tutorial summary. The post that works for both groups is concrete, short, and shows the thing rather than describing it.

The Challenge

What you’ll need

  • Your counter program from Days 57 through 61
  • Your test suite, including the failure-path tests from Day 60
  • The dev.to post you published on Day 62
  • An account on at least one of X, LinkedIn, Bluesky, or Farcaster
  • A screenshot tool (macOS Screenshot, Windows Snipping Tool, ShareX, or CleanShot)
  • Optional: Carbon or ray.so for nicer code screenshots

Steps

  1. Open your cargo test -p counter output from a clean run and take a screenshot showing the four passing tests: initialize, increment, the unauthorized-increment refusal, and the second failure test. Crop tightly. Nobody needs to see your terminal prompt or your wallpaper.
  2. Open the failure-path test that asserts your program refuses the wrong wallet. Take a second screenshot of just that test block, ideally pasted into Carbon or ray.so with a readable font. This is the part of your code that does the persuading: it shows you wrote a test that expects failure and got it.
  3. Write the post. Keep it to one short paragraph plus the two images. A working template:
Day 63 of #100DaysOfSolana.

Built my first Anchor program this week: a counter
that only the wallet that created it can increment.

The interesting bit isn't that it works. It's that
I wrote tests that expect it to refuse the wrong
signer, then broke the program on purpose to prove
the tests catch real bugs.

Read the full write-up: [link to your dev.to post]

Rewrite it in your own voice. The two non-negotiables: the #100DaysOfSolana hashtag and a link to your Day 62 post. Everything else is yours.

  1. Attach both screenshots. The test-run screenshot first (the proof), the code screenshot second (the substance). Most timelines display the first image largest, so put the most attention-grabbing one there.
  2. Cross-post. If you wrote it for X, paste the same text and images into LinkedIn with one or two sentence tweaks (LinkedIn rewards slightly longer captions and full sentences). If you have a GitHub profile, push your programs/counter directory and your tests directory to a public repo and link it from the post or from your bio.
  3. Reply to one other #100DaysOfSolana post with something specific. Not “nice work” or a flame emoji. Ask a question about a design choice or share what you tried that didn’t work. The algorithm rewards conversations more than broadcasts, and you are also building a network of people who are exactly as deep into this material as you are.

What Just Happened

You converted private work into public surface area. The counter program itself has not changed. What changed is that there is now a searchable, linkable artifact tying your name to a concrete on-chain skill, and it is sitting somewhere a recruiter, a teammate, or a future collaborator can stumble across it.

Resources

Submission

Share your post on the social platform of your choice using the #100DaysOfSolana hashtag, then drop the link below. And why not share it in the 100 Days of Solana Discord, too?

Submit your project