Same effort every time, same comment, just a different thread each time. The spread came entirely from which thread I picked, not from anything I changed about what I wrote.
That has changed how I think about distribution. It stopped being a channel decision and became a research step before I write anything: how fresh the thread is, how many replies it already has, whether the person asking is actually going to read what comes back.
I m Rosie Sherry and I ve been building communities for quite some time! I m here to answer anything and everything I can about community building. Here are some of the things I ve done: - I started back in 2006 with a local Girl Geek Dinner Meetup
- I founded Ministry of Testing, an indie, 7 figure revenue and profitable community of practice for software testers. I handed this community over for someone else to run (I did not sell it).
- I led the community at Indie Hackers for a couple of years
- I started Indiependent, a small community for indie founders where people get kicked for inactivity
- I ve been writing about community at Rosieland (covering community growth, flywheels, Minimum Viable Communities, Community Discovery, and much more!)
- I breathe, eat, sleep community Ask me anything about community, I can cover things like:
- Tools to use, or not
- Community on a budget
- Community as a business
- Minimum Viable Communities
- Community Discovery
- Community Growth & Flywheels
- Building a sustainable community
- Community trends
- Why so many people are getting community wrong! I'll be answering questions on the 7th of September!
Art = the expression or application of human creative skill and imagination, producing works to be appreciated primarily for their beauty or emotional power.
I was testing an app recently that relied almost entirely on text prompts to navigate and edit settings. While it made initial onboarding really fast I quickly lost track of what the tool could actually do because there were no menus to explore.
I feel like prompt bars are great for complex execution, but visual layouts are still essential for checking data accuracy and seeing your workflow at a glance.
Where do you draw the line when deciding which features belong in a chat box vs a standard screen layout?
I run multi-client creative work (video, ad scripts, photography) and feedback always ends up scattered across WhatsApp, email, and Figma comments. Half the time nobody's sure which version actually got approved. Curious how others handle this, especially freelancers and small agencies juggling several clients at once. Is your bottleneck getting clear feedback, keeping versions straight, or something else entirely?
Whenever I start a session in a large monorepo the agent automatically indexes or pulls in context from unrelated microservices. Suddenly, it starts suggesting patterns or types from a completely different service that shouldn't even be communicating with the current module.
The broader the context window gets, the more "cross-contamination" happens in the suggestions. How do you effectively curate or prune the file context before handing off a task to an agent?
Hello everyone! I often have a problem with the fact that my personal life is mixed with my work life. What kind of life hacks do you have for organizing your work from home?
