DEV Community

Cover image for 30 days, 30 posts: what I set out to do, and what's next
Suraj Nandan
Suraj Nandan

Posted on

30 days, 30 posts: what I set out to do, and what's next

Thirty posts in thirty days. Rather than grade myself, here's what I set out to do, a distilled version of the whole series, and a plan you can copy for your own.

What I set out to do

  • Publish one honest note a day, so the decision to write was already made.
  • Stick to things I'd actually built or believed.
  • Mix technical walkthroughs with plain career notes.
  • Show the limits next to the achievements.

You've read the posts, so you can judge better than I can which ones landed and which didn't.

The whole series in ten lines

  1. Put rules where they can't be bypassed. The database is the referee.
  2. An optional step must never block a deploy. And verify the live site yourself.
  3. Choose by what already exists. Package what you've built.
  4. Instruction is not control. Enforce in code what code can enforce.
  5. A design system is a list of decisions you refuse to remake.
  6. Tutorial hell ends when you're blocked by something you care about.
  7. Split team work by interface, and credit everyone.
  8. Name your limits publicly. It builds trust and makes gaps harder to ignore.
  9. Make the safe path the default path. Habits, systems and prompts alike.
  10. Learn privately, publish what you've verified, and invite correction.

What I want to do next

  1. Finish tests for CardBridge and write up what they find (Day 20's plan).
  2. Run the Whiteboard.ai eval against a real key and publish the real catch rate.
  3. Publish the template once payouts are set up, and report honestly how it goes.
  4. Keep writing at a pace I can sustain, probably weekly.
  5. Read and comment on other writers' work. Writing in public is a conversation, and I've mostly been talking.
  6. Open a small pull request on a project I use.

A 30-day plan you can copy

You don't need to publish daily to benefit. Here's a gentler version.

Week 1: Collect. Keep a note of things you build, fix or learn. Don't write posts yet. Just capture.

Week 2: Draft. Turn your three best notes into drafts. Use the structure from Day 24: problem, idea, example, cost, takeaway, question.

Week 3: Publish two. Pick the two you'd be least embarrassed to be corrected on. Publish them and ask a real question at the end.

Week 4: Respond and reflect. Reply to every comment. Fix anything wrong. Write down what you'd do differently.

Repeat. The compounding comes from repetition, not from any single post.

Rules worth stealing

  • Label opinions as opinions.
  • If you didn't measure it, don't claim it.
  • Say what's stubbed, simulated or unfinished.
  • Credit teammates by name.
  • Fix mistakes publicly and say what changed.

One thing to take away

You don't need permission or a big audience to start. Pick a small, honest habit, do it publicly, and let it compound.

Thank you

To everyone who read, reacted or commented, and to the people who write in public and made it easier for me to try: thank you.

A six-month roadmap template

If you'd like to turn the series into a plan for yourself, here's a shape that works for many students. Fill in your own specifics.

Month Focus Concrete outputs
1 Foundations One small project deployed; a README; an honest list of gaps
2 Depth One project with a real database, auth and permissions; tests for the riskiest part
3 Writing Three short posts from what you built; ask for feedback
4 Collaboration One team project or one open-source contribution
5 Polish A portfolio with case studies and limits; accessibility pass
6 Reach out Apply to internships or roles; share your work with five people

You can compress or stretch it. The point is that each month ends with things that exist, not hours spent.

Frequently asked questions

Do I need to write every day? No. Thirty days was an experiment. A sustainable weekly pace builds more than a burst you can't keep.

What if nobody reads it? Early on, few will. The value is the clarity you gain and the record you build. Readers arrive slowly, often from search months later.

What if I'm wrong in public? You will be, occasionally. Correct it visibly and move on. People trust writers who fix mistakes.

Isn't it risky to admit gaps? There's a cost, but most people read honesty about limits as maturity. Don't confess things that would harm you; do avoid claiming things that aren't true.

How do I find topics? Keep a "stuff" file of problems you hit and questions people ask you. Topics usually appear on their own.

How do I deal with feeling like I'm not expert enough? Write for the person one step behind you. You know things they don't, and you remember what it was like not to.

A checklist before you publish anything

  • [ ] Is every claim something I can back up?
  • [ ] Have I said what's simulated, stubbed or unfinished?
  • [ ] Are teammates credited by name?
  • [ ] Did I check for secrets or private details in code and screenshots?
  • [ ] Is there one clear takeaway?
  • [ ] Does it end with something useful (a limit, a question, a next step)?

A last bit of perspective

Thirty days of posts won't change a career by itself. What changes things is the pile of small, honest, visible work that builds up when you do this for a long time: projects, case studies, posts, corrections, conversations.

If this series nudged you to start your own, tell me where to find it.

Key takeaways from day 30

If you wrote something during these 30 days, or you're about to start your own, drop the link below. I'd like to read it.


☕ Enjoyed this post? You can support my writing on Ko-fi.

Support me on Ko-fi

Top comments (1)

Collapse
 
alexcodebytes profile image
Oleksandr •

"tutorial hell ends when you're blocked by something you care about" — this is the most accurate sentence i've read all week. i needed the reminder that you don't have to be an expert to start writing, you just have to be one step ahead of the person reading it. congrats on finishing 30 days, that's a massive flex. definitely saving that 4-week plan!