I saw a headline about layoffs.
Not a specific one. Just the pattern. In any given month, tens of thousands of people are losing their jobs. The number keeps going up. It's becoming background noise — which is exactly the problem.
I started thinking about what that actually means for someone who built their entire professional identity inside one company.
That thought turned into a conversation with ChatGPT.
Not a research session. Not a content planning meeting. Just: here's what I'm thinking, here's why it concerns me, what are the angles worth exploring?
An hour in, I had five post ideas fully formed:
Why most people lose their story before they lose their job.
Your voice is an asset — the skill you weren't told to build.
Layoffs are rising. Here's what visibility actually protects you from.
The borrowed identity problem.
What comes next when the title is gone.
Each one came from letting a genuine thought run long enough to become something.
The layoff number wasn't the story. The layoff number was the current event — the hook that made the underlying problem urgent right now. The real story was about people who outsourced their professional identity to a system they didn't control, and what happens when that system changes.
That's the thing about newsjacking done right. You're not writing about the news. You're using the news as a reason to say something you already believed was true.
I believed this before I saw the headline. The headline just made it timely.
Here's what happened after the conversation.
I told ChatGPT: write the first article. Here's the angle. Here's the voice. Here's who it's for.
It drafted it. I reviewed it. Made some edits.
Then I said: push this to my GitHub repo under the blog content folder.
And it did.
Because ChatGPT is now connected to GitHub directly. The conversation produced the article. The article went to the repo. The repo feeds the site. I showed Shelly this exact workflow on a call this week and watched her eyes go wide.
"Did it curate the image too?"
Yes. It pulled a relevant photo from Unsplash and attached it to the file.
I didn't search for anything. I didn't open a separate tab. I just had the conversation and the article was done.
The article went up as: Why Most People Lose Their Story Before They Lose Their Job.
It's on superjunaid.com now.
What I want people to understand isn't the ChatGPT workflow — though that's useful. It's the upstream thing. The thing that made the workflow produce something real instead of something generic.
The thought had to be real first.
I genuinely care about the layoff problem. I've seen it. I've talked to people going through it. I've built things specifically because I know what it feels like when your work stops being visible the moment you change companies. All of that genuine concern is what made the conversation with the AI actually produce something worth publishing.
If you start with "write me five posts about layoffs" — you get five forgettable posts about layoffs.
If you start with a real thought, a real tension, a real belief — and then use the tool to find the shape of it — you get something that sounds like you. Because it came from you.
ChatGPT is now connected to GitHub. It can push content to your repo. It can pull your site's existing structure, match the format, pick an Unsplash image, and file it in the right folder.
The pipeline is shorter than it's ever been.
But the pipeline doesn't matter if there's nothing real going in.
Start with the thought. The rest is fast.