From One Comment to a CreatorCon Submission: What Learning in Public Taught Me

Sreeram Nair · 17m ago

A single comment on a Community blog post led, in about a week, to a conversation with the team behind it, two posts of my own and my first CreatorCon session proposal. None of it was planned.

I'm a ServiceNow architect at a partner in New Zealand, working mostly with public sector clients. I'd never submitted a conference session or written a series of Community posts before. What changed wasn't my expertise. It was deciding to think out loud in public, and to treat every reply as a chance to learn rather than a verdict.

This post is about what that taught me, in case it's useful to anyone wondering whether it's worth speaking up.

What happened

Each step came from responding to the one before it, not from a plan.

A comment with real questions. ServiceNow published a detailed post on benchmarking AI coding agents. I left a comment on what I found useful and asked three specific questions, including whether the method could work for platform configuration rather than code.
A thoughtful answer. The authors replied to each question in detail, including why platform work is harder to test.
A follow-up post. Their answer made me want to try. I wrote up how a platform team could run a small version on its own instance, and linked it in the thread.
Expert feedback. The authors reviewed it and told me exactly where the method would break. Another reader challenged the original conclusion, and the discussion got better for it.
A session proposal. When the CreatorCon call for content opened, I had a topic, a point of view and a public trail of work. I submitted a proposal; decisions come in January.
A series. I turned the feedback into Part 1 of a series, so others can use it before I've even presented anything.

Whatever happens with the proposal, I've already got more out of the last week than from months of only reading.

Ask a real question, not a compliment

A "great post, thanks" comment ends a conversation. A specific question starts one.

Authors get plenty of praise and very few questions that show someone has actually worked through their ideas. The comments that got the most thoughtful replies were the ones that:

quoted a specific result and said why it mattered to my own work
asked something the post didn't answer, rather than something it did
connected the topic to a different audience, in my case partners and customers rather than ServiceNow's own engineers

You don't need to be an expert to ask a good question. You need to have read carefully and thought about how it applies to you.

Being corrected in public is the point

The most valuable replies I got were the ones that told me I was wrong.

When I asked the authors where my method would break down, they gave me three clear problems I hadn't thought of. Later, I put a cost increase down to slow builds on one codebase. The author pointed out, politely and with numbers, that costs had risen on other codebases too, so my explanation didn't hold.

It's tempting to go quiet after that, or to defend the original point. I thanked them, said what I'd got wrong, and updated my thinking in the thread. That did more for my credibility than being right the first time would have, because everyone reading could see that I listen.

If you're worried about posting because someone might correct you: that's the best outcome. You get expert review for free, in front of an audience.

AI can help you write, but you own every claim

I used an AI assistant throughout: to draft replies, structure posts and turn rough notes into something readable. It made me much faster. It also made mistakes I'd have published if I hadn't checked.

Two examples from the same week:

Links that looked right but weren't. Several documentation links it found opened German-language pages for some readers, and one pointed to an older release. They only came to light because I asked it to open and check every link before I posted.
A claim that went further than the source. It summarised a licensing change more strongly than the official document actually said. Reading the source directly caught it.

The lesson for anyone driving AI adoption is the same one I'd give a team: AI is a great first draft and a poor final word. Your name is on the post, so every number, link and claim is yours to verify. Asking "did you check that?" is a habit worth building early.

Turn the conversation into something others can use

A good thread disappears into the archive. A post that turns it into steps, with credit to the people who shaped it, keeps working.

After the authors pointed out the weaknesses in my method, I wrote Part 1 of a series that built their feedback in directly and credited them for it. That did three things:

It made the advice usable by people who would never read a long comment thread.
It gave the authors a reason to come back, because their input had turned into something concrete.
It gave me a body of work to point to, which made the CreatorCon proposal far easier to write.

You don't need original research to do this. Summarising what you learned from a discussion, clearly and with credit, is valuable on its own.

How to start this week

Pick one post in your area this week and leave one comment with a specific question. That's the whole first step.

Choose a post you've actually read to the end, ideally on something you work with every day.
Ask one question it doesn't answer, and say briefly why it matters to you.
Reply when someone answers. Thank them, and say what you'll do with it.
If you try something, write it up, even if it's small and even if it didn't work. Link back to where the idea came from.
If someone corrects you, thank them first and update your post.

If you'd like to see how the thread unfolded, it started on Benchmarking Coding Agents on the Now Platform Codebase and continued in Before You Pick a Coding Agent for ServiceNow and Part 1 of the series.

I'd love to hear from others who've done this.

What's the most useful thing someone has taught you in reply to a comment? Share in the comments.