DEV Community: Chad Dyar

HEADLINE: Build Real Connections at Work

Chad Dyar — Fri, 22 May 2026 07:23:01 +0000

HEADLINE: Build Real Connections at Work

In today's work environments, conversations often feel like performances. But what if they didn't have to? "How to Talk to Humans" offers a map to genuine communication. Discover how trust and real relationships can transform your work life.

CTA: Read more about the book

TITLE: Authentic Communication for Developers

Chad Dyar — Fri, 22 May 2026 07:23:00 +0000

TITLE: Authentic Communication for Developers

Communication as Code: Like clean code, clear communication is essential in tech. It's about being straightforward and honest.
From Performance to Connection: Shift from performing in meetings to forming real connections. "How to Talk to Humans" can guide you.
Trust Building in Teams: Communication isn't just exchanging information. It's about building trust within your team.
Tools to Enhance Your Message: Consider tools like ContentF

Tony had to help me get dressed last Tuesday morning.

Chad Dyar — Fri, 22 May 2026 06:11:10 +0000

Tony had to help me get dressed last Tuesday morning.

I have rheumatoid arthritis. When it flares, it goes for the hands. By the time I made it to my laptop, the content system had already posted to LinkedIn and Mastodon. Nine items published over three days while I was mostly down.

This is the architecture behind that.

The Stack

The pipeline runs on three components: a Supabase marketing_queue table, a local Python publisher process called Clawbot, and a weekly Sunday approval workflow I run in a Cowork session.

The queue table is the central object. Every piece of content lives there as a row with these key columns: platform, title, body, status, week_of, day_of_week, source.

The Status Flow

Items move through these statuses: pending, ready, approved, published.

The publisher only touches items with status = approved or ready_to_publish. It never touches pending, ready, or human_required. This is the key architectural decision. Approved is the gate. Nothing publishes without my explicit sign-off.

The Validation Layer

Before any content goes into the queue as ready, it passes two database functions:

SELECT public.is_publishable_content(body, title) as passes,
public.content_validation_reason(body, title) as reason;

The validation catches: body under 200 characters, metadata prefixes in the body field, brief-format content that was never expanded into finished copy, and a biographical accuracy check that rejects content with specific phrases that would be factually wrong for my situation.

Last week I had 22 items rejected. The failure mode: batch content submitted as planning briefs instead of finished copy. The system caught it. I still have to clean it up manually.

The Sunday Workflow

Sunday evenings I run a content batch process. It generates fresh content for the current week, validates it, and inserts it with status ready. Then I do a manual approval pass: reading each item, improving anything that needs work, and updating to approved. Clawbot clears the approved queue on its schedule throughout the week.

When I cannot do the Sunday review, the prior week's approved queue continues clearing. The gap is visible in the metrics but the output does not completely stop.

What I Would Do Differently

The biggest gap right now: the 22 rejected items represent a failure in the content generation step. The validator caught them correctly. But they represent wasted generation cost and manual cleanup work. I am adding a stricter pre-validation pass to the Sunday generation workflow so rejected items never make it into the queue in the first place.

Second gap: long-form content has no automated path to published. It parks at ready and waits for me to manually post it. That is intentional for quality reasons, but it means long-form has a higher abandonment rate. Working on a simpler handoff that reduces friction without removing human review.

The thing that surprised me most: the system does not know it is impressive. It just runs. Tuesday morning when the arthritis was bad, it published at 8:47 AM the same as any other Tuesday. No acknowledgment, no notice. Just the work.

I find that oddly reassuring.

Three days of an arthritis flare. Forty accounts. Zero intervention from me. That was the test. I did not design the test. I jus

Chad Dyar — Fri, 22 May 2026 06:11:08 +0000

Three days of an arthritis flare. Forty accounts. Zero intervention from me. That was the test. I did not design the test. I just ended up in it. Here is what I built in February that made the May test passable, and the technical decisions that mattered. The stack: Supabase (PostgreSQL) with a marketing_queue table. Key columns are platform, body, title, week_of, day_of_week, status, content_type, and source. Status flow runs from pending (failed validation or needs review) to ready (validated, queued) to approved (cleared for publishing) to ready_to_publish (execution target) to published or rejected. Validation uses two database functions. is_publishable_content(body, title) returns boolean. content_validation_reason(body, title) returns the failure reason. Every insert runs validation before touching the table. The functions check for metadata prefixes in body, minimum length of 200 characters, biographical accuracy triggers, and brief-format field patterns. Two DB triggers rewrite bad status values on every insert and update: normalize_publish_status on marketing_queue and normalize_publish_status_comet on comet_posts. These catch any status value outside the valid set and rewrite it automatically. Upstream mistakes cannot persist in the queue. The publishing agent is Comet, a local Python process. It reads from marketing_queue where status is in approved or ready_to_publish and drives publication platform by platform on a schedule. Content generation runs as a scheduled Cowork task. It calls Claude with a documented story bank and voice rules, generates the full content batch across nine platforms, validates each piece against the DB functions, and inserts clean rows. What worked: the validation functions before every insert, the status normalization triggers, and the story bank documentation. What I would change: the queue depth (7 to 10 days is the right target, not 3 to 5) and adding a dead man's switch for the Comet process since it runs locally with no uptime monitoring. Current queue state: 41 published, 8 human_required, 8 pending, 14 rejected. No stuck items. If you are building a similar content pipeline and want to compare notes, I am at chadtdyar.com or in the comments below.

TITLE: The Art of Asking Questions in Leadership

Chad Dyar — Fri, 22 May 2026 04:12:40 +0000

TITLE: The Art of Asking Questions in Leadership

The Power of Questions: Leadership is not about having all the answers. It's about asking the right questions to unlock potential.
From Opera to Tech: My journey from the world of opera to tech has shown me that coaching is guiding someone to find their own path.
Emotional Intelligence Meets Resilience: In 'Performance Whisperer', I discuss how these elements bridge together to foster growth without burnout.
Aligning Leadership: Al

TITLE: Finding Courage in Everyday Moments

Chad Dyar — Fri, 08 May 2026 22:29:04 +0000

TITLE: Finding Courage in Everyday Moments

The Everyday Battle with Fear
We face fear daily, whether it's a new project or a career change. My transition from opera to sales taught me this firsthand.
Courage in the Corporate World
Standing on a stage, real or metaphorical, demands courage. It's about believing your voice will carry.
Lessons from Benny, Maya, and Wick
'In The Spiderhands, the Bag Monster, and the Blanket Snakes,' three dogs guide us through what courage looks like.
Teaching Kids About Bravery
This children's book shows kids that bravery isn't about size. It's about facing fears with a steady heart.
Courage Leads to Growth
By embracing our fears, whether in boardrooms or classrooms, we build resilience and grow.
More About the Book
Learn more about how this book can teach courage to children.

https://www.chadtdyar.com/books/the-spiderhands-bag-monster-blanket-snakes

leadership #courage

TITLE: Navigating Faith and Identity in Complex Environments

Chad Dyar — Fri, 08 May 2026 03:02:06 +0000

TITLE: Navigating Faith and Identity in Complex Environments

The Tension Between Faith and Identity
- Explore how faith and identity often clash, especially in high-pressure environments.
A Preacher's Kid's Journey
- Discuss the personal journey from a South Carolina parsonage to a recital hall, and finally to a bar that becomes a sanctuary.
The Role of Chosen Families
- Highlight the freedom found when chosen families form as inherited ones fracture.
Lessons in Personal Growth
- Share how understanding where you come from and where you choose to go can be worlds apart.
The Gospel Trilogy's Impact
- Discuss how the trilogy brings these struggles to life on stage.
Conclusion
- Connect readers to "The Gospel Trilogy" for a deeper exploration of these themes.

https://www.chadtdyar.com/books/the-gospel-trilogy

TITLE: How Dogs Teach Kids Self-Awareness: A Practical Insight

Chad Dyar — Fri, 08 May 2026 03:02:05 +0000

TITLE: How Dogs Teach Kids Self-Awareness: A Practical Insight

The Challenge of Self-Awareness: Kids struggle to understand their own actions. Dogs, with their simple, honest interactions, offer a unique way to teach this skill.
The Role of Wick, Maya, and Benny: In "The Sparkle, the Snuggle, and the Song," these dogs aren't just characters. They're guides, showing kids the impact of their daily choices.
Practical Lessons from Play: The book uses playful scenarios to demonstrate how different decisions affect feelings and group dynamics.
Empowering Children's Independence: The story offers a framework for helping kids learn to reflect on their choices, promoting independence without adult interference.
Tools for Parents and Educators: With scripts for tricky moments, the book provides a practical tool for teaching self-awareness.
Conclusion: Discover how Wick, Maya, and Benny can help teach kids self-awareness.

https://www.chadtdyar.com/books/the-sparkle-the-snuggle-and-the-song

ChildDevelopment #Learning

Hey friends,

Chad Dyar — Fri, 01 May 2026 18:53:47 +0000

Hey friends,

Do you ever find yourself staring at a blank screen, wondering where your next big idea is going to come from? I’ve been there too. Some days, the creativity flows like a river, and on others, it feels like I’m trying to squeeze water from a stone.

This Thursday, I want to share a few techniques that have helped me break through those creative blocks. Whether you’re a developer, writer, or just someone who loves to create, these tips might resonate with you.

First off, changing your environment can make a world of difference. Sometimes a simple shift, like working from a different room or heading to a café, can ignite fresh thoughts. It’s all about finding a space that inspires you.

Next, don’t underestimate the power of conversation. Talking things through with a friend or colleague can spark new ideas. Often, simply verbalizing your thoughts helps you see them from a different angle.

Lastly, give yourself permission to explore without pressure. Set aside some time to play with ideas—no matter how wild they may seem. You might be surprised at what you discover when you allow yourself to wander creatively.

Let’s embrace those moments of uncertainty together. Creativity isn’t just about the end result; it’s about the journey and the connections we make along the way. What strategies do you use to keep your creative juices flowing? Share your thoughts below!

TITLE: Mastering Sales Improvisation: A Systematic Approach

Chad Dyar — Fri, 01 May 2026 18:53:46 +0000

TITLE: Mastering Sales Improvisation: A Systematic Approach

The Art of the Pivot: Understand why sales is more than just numbers. It's about handling unexpected turns like a pro.
Improv as a Sales Tool: Discover how sales can be approached like an improv performance, focusing on genuine responses.
Breaking Down Improvisation: Learn the four core components: status, listening, offer/accept, and framing.
Building Your Skills: Each component is a muscle you can train. Find out how these skills help in handling objections.
Turning Losses into Wins: Explore how being prepared to adapt ensures you land where you need to be in sales.
The Role of Visual Consistency: For brand builders, Palette Pro helps maintain visual consistency, complementing the adaptability mindset.

https://www.chadtdyar.com/books/think-on-your-feet-land-on-your-numbers

TITLE: Embrace Authenticity in the Workplace

Chad Dyar — Fri, 24 Apr 2026 14:01:05 +0000

TITLE: Embrace Authenticity in the Workplace

The Mask We Wear
Corporate spaces often feel like they demand a disguise. But what if we could step into work as we truly are?
Authenticity as a Strength
"Bring Your Best Self To Work" isn't about breaking rules; it's about being genuine. This book is for those tired of playing roles at work.
My Journey: Opera to Corporate
I've walked this path from opera stages to corporate halls and found authenticity isn't just possible; it's powerful.

I shipped ContentForge's iOS app on the fourth App Store submission. Here is what each rejection was and how I fixed it, because

Chad Dyar — Fri, 24 Apr 2026 14:01:04 +0000

I shipped ContentForge's iOS app on the fourth App Store submission. Here is what each rejection was and how I fixed it, because I could not find this information clearly written anywhere when I needed it.

Rejection 1: Missing Info.plist purpose strings (ITMS-90683)

If your Capacitor app uses any plugin that touches a privacy-sensitive iOS API, you need a corresponding NSUsageDescription string in your Info.plist. Apple's CI scanner catches this automatically and rejects the build before it ever reaches a human reviewer.

My app used Capacitor's StatusBar plugin. The purpose string was missing.

The fix: add the required string to ios/App/App/Info.plist. After fixing this the first time, I built a Node script that runs in CI and checks for missing strings automatically. It reads the Capacitor plugins from package.json, maps each one to the privacy APIs it touches, and verifies the corresponding purpose strings exist. That script runs on every push to main.

Rejection 2: Incomplete AppIcon.appiconset

Apple requires specific icon sizes for every device type your app supports. My asset catalog was missing several of the required dimensions.

The fix: generate the full set programmatically from a 1024x1024 source PNG. Make sure the source PNG is flat RGB with no alpha channel and is not upscaled from a smaller source.

Rejection 3: Magic link auth fails in Apple's review sandbox

Apple's review team cannot use magic link authentication. They work in a sandboxed environment where email links do not resolve. If your app's only auth path is magic link, reviewers cannot create an account.

The fix: detect whether you are running as a Capacitor native app using Capacitor.isNativePlatform(), and conditionally hide the magic link UI. On iOS, show only email and password. On web, show magic links as normal.

What passed on submission 4

The fourth submission included all of the above plus: server.startPage set to app.html in capacitor.config.ts, comprehensive touch target fixes at 44x44px minimum, 16px minimum font size on all inputs to prevent iOS zoom-on-focus, and env(safe-area-inset-*) padding on sticky navs for notch and Dynamic Island support.

The CI workflow I wish I had before submission 1

After all of this, the CI pipeline on main now runs npm install and build, the custom Info.plist lint script, TypeScript type check, and Vercel deploy preview. If the Info.plist lint fails, the build fails. The ITMS-90683 rejection path is now closed.

If you are building a Capacitor app and heading toward App Store submission: read the full App Store Review Guidelines before you build the auth flow, test in airplane mode if you have any concern about network-dependent auth flows, and build the CI lint before you need it.