Forem: Ashley B

The Creator Block Debugger: Still Fixing It But It Works

Ashley B — Tue, 21 Apr 2026 18:40:55 +0000

Creator block is usually not a talent problem. It is a starting problem.

I built a system that works when motivation is zero. Here is how:

Have a queue of 30 ready-to-post pieces
Use prompts instead of waiting for ideas
Batch create when feeling creative
Schedule and forget

The goal is to never face a blank page.

How I Turn One Idea Into 10 Posts Without AI Slop

Ashley B — Tue, 21 Apr 2026 18:40:12 +0000

The Problem

I used to treat ideas like single-use objects.

One idea -> one post -> done.

Then I'd sit there the next day like:

"cool... now what?"

Repeat that enough times and you end up doing one of two things:

overthinking everything
or not posting at all

Neither one scales.

Where My Ideas Actually Come From

Nothing fancy.

random thoughts
things I've built
frustrations
"this sucks, there should be a better way"

That last one is the goldmine.

If I feel friction, odds are someone else does too.

What Changed

I stopped treating ideas like finished products.

Now I treat them like raw input.

And instead of asking:

"is this a good post?"

I ask:

"how many angles can I squeeze out of this?"

The Actual System (Not Pretty, But It Works)

Step 1: Rant first

I don't start structured.

I just dump everything:

what's annoying me
what I think is broken
what I wish existed

No filter. No polish.

Step 2: Extract angles

From one rant, I usually get:

a blunt take
a practical tip
a story
a system
a question

Same idea. Different surfaces.

Step 3: Map to platforms

Each angle becomes a different format:

short punch -> social post
structured idea -> Dev.to
repeatable idea -> Pinterest
casual version -> Facebook

Same core idea, different packaging.

Step 4: Store everything (this is the real unlock)

The biggest change wasn't AI.

It was having a place to dump everything.

I built a simple system (DB + queue) where I can:

drop ideas
expand them later
schedule without thinking

That removed the "what do I post today?" problem entirely.

Where AI Actually Helps (and Where It Doesn't)

I use AI a lot.

Probably too much.

Where it helps:

generating variations
breaking writer's block
speeding up structure

Where it fails hard:

When you try to force voice out of it.

What "AI Slop" Actually Is

AI slop isn't just bad writing.

It's this loop:

you ask -> it gives something generic -> you tweak -> it gets worse -> repeat

You end up with content that:

sounds like everyone else
says nothing new
feels safe and useless

Especially if you want something:

edgy
opinionated
slightly unhinged

AI struggles there.

The Fix

I stopped asking AI to create from scratch.

Now I:

start messy (my input)
use AI to expand, not invent
keep the tone mine

AI is a tool, not the source.

The Real Outcome

This changed two things:

1. Consistency

I don't rely on "feeling like posting" anymore.

I already have:

ideas
drafts
scheduled content

2. Output without burnout

Instead of forcing new ideas daily:

I reuse the same idea multiple times.

Which means:

less pressure
more content
better ideas over time

The Simple Version

If you do nothing else:

stop writing one post per idea
start extracting multiple angles
store everything

That alone will outpace most people.

Final Thought

You don't need more ideas.

You need to stop wasting the ones you already have.

https://fleurdevie.gumroad.com/l/100prompt-storm

What Building a Social Scheduler Taught Me About Reliability

Ashley B — Tue, 31 Mar 2026 21:15:43 +0000

Most automation tools feel impressive right up until you have to trust them.

It is easy to demo a scheduler.

It is much harder to build one that survives real life:

expired tokens
flaky platform APIs
posts that need review
queues that drift out of sync
failures that happen while you are asleep

That gap changed how I think about automation.

I have been building a project called PostPunk, and I thought the hard part would be generating content and wiring platform APIs together. That turned out to be the easy part.

The real work was operational trust.

A useful scheduler needs a few things that demos usually skip:

1. Approval states matter

Not every post should go straight from draft to published.

Some posts are written by you and are ready immediately. Some are AI-assisted and need a second look. If your system does not distinguish that clearly, you end up either babysitting everything or accidentally posting junk.

So I ended up treating post states as part of the core workflow, not just metadata:

draft
approved
posted
failed

That sounds simple, but it changes everything.

2. Failure is not an edge case

In scheduling systems, failure is normal.

A platform token expires.
An API rate-limits you.
A platform changes a field name.
An account is misconfigured.
A browser fallback stops matching the UI.

If the whole system falls apart the moment one target fails, you do not have automation. You have a fragile demo.

So the system needs:

retries
visible failure states
alerts
manual assist when automation is not trustworthy

3. Automatic is not the same as unattended

A lot of posting tools sell the dream of full autopilot. In practice, a better model is often:

automate what is stable
assist where platforms are hostile
keep the queue and schedule as the source of truth

That still saves a huge amount of time, and more importantly, it is honest.

4. Scheduling is really an operations problem

The UI part is not enough.

You also need:

a worker that checks for due posts
logs
retry logic
success and failure alerts
a clear what is due today view

Without those, the schedule is just decorative.

What I learned

The hardest part of automation is not getting software to do something once.

It is getting it to behave predictably enough that you stop worrying about it.

That is the part I care about now.

If you are building internal tools, creator tools, or any kind of scheduler, reliability is the actual feature. Everything else is packaging.

PostPunk is still a project I am actively working on, but building it has made me much less interested in shiny automation promises and much more interested in boring operational trust.

What Building a Social Scheduler Taught Me About Reliability

Ashley B — Mon, 30 Mar 2026 15:01:32 +0000

Most automation tools feel impressive right up until you have to trust them.

It is easy to demo a scheduler.

It is much harder to build one that survives real life:

expired tokens
flaky platform APIs
posts that need review
queues that drift out of sync
failures that happen while you are asleep

That gap changed how I think about automation.

I have been building a project called PostPunk, and I thought the hard part would be generating content and wiring platform APIs together. That turned out to be the easy part.

The real work was operational trust.

A useful scheduler needs a few things that demos usually skip:

1. Approval states matter

Not every post should go straight from draft to published.

So I ended up treating post states as part of the core workflow, not just metadata:

draft
approved
posted
failed

That sounds simple, but it changes everything.

2. Failure is not an edge case

In scheduling systems, failure is normal.

A platform token expires.
An API rate-limits you.
A platform changes a field name.
An account is misconfigured.
A browser fallback stops matching the UI.

If the whole system falls apart the moment one target fails, you do not have automation. You have a fragile demo.

So the system needs:

retries
visible failure states
alerts
manual assist when automation is not trustworthy

3. Automatic is not the same as unattended

A lot of posting tools sell the dream of full autopilot. In practice, a better model is often:

automate what is stable
assist where platforms are hostile
keep the queue and schedule as the source of truth

That still saves a huge amount of time, and more importantly, it is honest.

4. Scheduling is really an operations problem

The UI part is not enough.

You also need:

a worker that checks for due posts
logs
retry logic
success and failure alerts
a clear what is due today view

Without those, the schedule is just decorative.

What I learned

The hardest part of automation is not getting software to do something once.

It is getting it to behave predictably enough that you stop worrying about it.

That is the part I care about now.

If you are building internal tools, creator tools, or any kind of scheduler, reliability is the actual feature. Everything else is packaging.

PostPunk is still a project I am actively working on, but building it has made me much less interested in shiny automation promises and much more interested in boring operational trust.

Why I Stopped Overpolishing Side Projects

Ashley B — Tue, 17 Mar 2026 05:12:20 +0000

Most small projects die from overthinking, not lack of skill.

I’ve been shipping small creative products lately, including a kawaii coloring series.

What changed wasn’t tools.
It was lowering the bar to publish.

Instead of asking:
"Is this perfect?"

I ask:
"Is this usable and clear?"

That shift alone made me ship more in a month than I used to in six.

Curious how others approach this—do you optimize first or ship first?

Quick Build Note

Ashley B — Tue, 17 Mar 2026 05:08:29 +0000

Small creative products are underrated.

They don’t need complex systems.

Just:

clear idea
consistent style
actually shipping

This kawaii coloring series is basically that in practice.

Trying to keep things simple and repeatable.

Most automation tools feel impressive right up until you have to trust them.

Ashley B — Sun, 15 Mar 2026 08:11:07 +0000

The hard part is not making automation run once. The hard part is making it reliable enough that you stop babysitting it.

That is the whole point of PostPunk Core: queue it, schedule it, see what is due, and stop pretending chaos is a workflow.

PostPunk browser-profile test

Ashley B — Sun, 15 Mar 2026 00:26:56 +0000

Browser-profile fallback test from PostPunk/N8tiveFlow.

This checks whether X can post through the local Chrome session while Dev.to remains healthy.

PostPunk live credential test

Ashley B — Sun, 15 Mar 2026 00:06:44 +0000

Live test from PostPunk/N8tiveFlow.

Verifying that X and Dev.to posting are working with the current credential set.

If this appears, the platform integration is alive.

Test Post from PostPunk

Ashley B — Sat, 14 Mar 2026 23:26:19 +0000

This is a test post from PostPunk automation system.

Test Post from PostPunk

Ashley B — Wed, 04 Mar 2026 18:13:31 +0000

This is a test post from PostPunk automation system.

Test Post from PostPunk

Ashley B — Wed, 12 Nov 2025 18:39:23 +0000

This is a test post from PostPunk automation system.