We're watching the birth of a new economic model.
January 2026 just hit 108,435 layoffs.
The highest January since 2009.
Up 118% from last year. Up 205% from December.
And here's the number that's even more important:
New hires announced in January: 5,306.
The LOWEST since they started tracking in 2009.
For every 1 person companies announced hiring, they announced cutting 20.
UPS is slashing 30,000 jobs.
Amazon is cutting 16,000.
Dow is restructuring thousands.
Healthcare just hit its worst month since April 2020.
But here's what makes this terrifying:
GDP is still growing at 4%.
The economy looks fine on paper.
Yet companies are firing at 2009 rates.
Wharton professor Mohamed El-Erian called it out:
"These layoffs are occurring while GDP continues to grow at approximately 4 percent, accelerating the decoupling of employment from economic growth."
Read that again.
Employment is decoupling from growth.
Companies are making more money with fewer people.
This is something new.
The economy is growing. Profits are up. And jobs are disappearing anyway.
AI was cited for 7,624 of January's layoffs. 7% of the total.
But that's just the companies willing to admit it.
Every CEO is talking about AI. Every earnings call mentions it. The market rewards companies that announce AI efficiency.
The real number is probably 3x higher.
The funny part is that "contract loss" was the #1 reason cited. 30,784 layoffs.
In other words, companies aren't renewing deals. They're pulling back. They're expecting less business.
This is what happens when corporations get spooked at the same time.
These layoff decisions were made in late 2025.
Before the new year even started, executives looked at 2026 and said: "Cut now."
The narrative has been "no-hire, no-fire."
Companies aren't growing headcount but they're not shrinking either.
That story just died.
We're now in "no-hire, YES-fire."
Hiring is frozen. Layoffs are accelerating. And the economy keeps growing.
If this continues, we're watching the birth of a new economic model.
One where prosperity and employment finally divorce for good.
What do you think?
Programmers were asked to make the worst volume control for a contest
teapawt.net/fluxfolio_/status/1972…
51
Yup, the manipulation is real...
1
62
Want to deploy your Streamlit app without the Streamlit branding?
Here's how I host mine on Render :
The setup:
→ Create requirements.txt with pipreqs
→ Push to GitHub (don't forget .gitignore for those secrets)
→ Connect to Render
→ Configure build commands
The tricky part most tutorials skip
Your Build Command needs to copy secrets AND install dependencies:
cp /etc/secrets/secrets.toml ./.streamlit/
pip install --upgrade pip && pip install -r requirements.txt
Start Command:
streamlit run <your_app>.py
Pro tip: If you're using @astral_sh's uv with custom packages, you'll need also create and use a build.sh file to make sure your custom packages are there too.
I wrote the full walkthrough tutorial (including the uv fix), because I couldn't find it anywhere else.
Here's the tutorial... you're welcome.
shanirivers.hashnode.dev/dep…
28
Want to try to make some money this year with that wee Streamlit app you built?
You can add a @stripe paywall to it! 🤑
Here's the exact process I used to add payments to my app in under 30 minutes:
1. Install st-paywall library
2. Create a Stripe product in Test Mode
3. Generate a payment link with redirect URL
4. Create a restricted API key (Read access for Customers + Subscriptions)
5. Drop secrets in secrets.toml
6. Add add_auth(required=True) before your locked content
7. Once deployed, flip your Stripe product to live
The trick? Test mode first. Always.
And now you too can call your app a micro SaaS! 🙌
Full walkthrough tutorial with a 💩 ton of screenshots: shanirivers.hashnode.dev/dep…
1
29
I spent last month building a paywall into my Streamlit app.
Honestly? I was surprised when the library threw a depreciation error back when I started building it. Had to dig into the Github repo, find the fix that wasn't pushed yet, and went in to fix it myself. (Don't worry it's pushed now!)
That's the thing about coding, as a busy parent, you have to learn to troubleshoot fast, because you don't have time to wait around.
The win: My calendar app is now behind Stripe payments. Test mode works. And now it is live.
What I learned: You don't need to be a full-stack dev to build a SaaS. You just need to be willing to figure it out as you go.
What did you ship last year?
shanirivers.hashnode.dev/how…
11
Happy Belated New year!
pinkphi.ai is live + looks amazing on @render
Their free tier is crazy = 25,000 users + 2 custom domains! 🤯
Making my app look like the real deal that it is!
What's one tool you ditched this month that made your life easier? #BuildInPublic
shanirivers.hashnode.dev/dep…
It lives!
pinkphi.ai
Took the free SCORE webinars.
Read the marketing books.
Watched so many YouTube videos.
Researched a 💩ton of Python libraries.
Then I finally built the tool. It generates a month of social media posts from long form content within minutes using a heck of a lot of code, an AI agent, so I could create a strategic content calendar without the headache. #buildinpublic #microsaas #momdeveloper
{ by @shani-codes } from @hashnode shanirivers.hashnode.dev/fro…
1
1
69
Unpopular opinion: Sometimes the fastest way to finish your project is to stop building it.
I paused my micro SaaS build for a week to learn Flask and how to build APIs.
Here's part 1 of why that "detour" was the best decision I made👇#buildinpublic
youtu.be/xpsyZOyrz3A
1
40
Went dark on #buildinpublic for 2 months, but not because I quit.
But because I hit a wall that I couldn't tweet through.
Worked on 2 "unrelated" side projects: a hipster translator API and a Flask tutorial rabbit hole (I'll share them soon). Turns out they taught me exactly what I needed to fix my main project. Deploying this weekend.
2
1
69











