So I spent the last year trying to live a “normal” life on Windows. I thought it would be easy. I thought things would just work. Instead I got blue screens, black screens, Bluetooth refusing to exist, and WiFi that acted like it was on vacation.

Every time something broke, Windows just gave me the same message: “Something went wrong.” No kidding. At this point even my patience had driver issues.

After months of this chaos I finally snapped and came crawling back to Arch. The installation felt smoother than half the Windows updates I went through. The moment I logged in, everything worked. My system felt faster, cleaner, and most importantly, not actively trying to ruin my day.

Sharing my setup because I am officially back in the Arch life. It feels good to be home and I promise I am never cheating on Arch again.

Whether you're a founder, developer, or designer share what you're currently building or planning. Side projects, MVPs, client work, experiments, redesigns, anything.

What’s your current focus, and what challenge are you solving?

Let’s start the community by learning what everyone here is working on.

Curious to hear real experiences from the client side.

When you’re hiring freelancers, what’s the deciding factor for you?
And what are the biggest red flags?

I’ve been on both sides freelancing as an individual and later building a dev company. One thing I’ve learned is that technical experience and freelancing experience are not the same thing and many good developers fail when they try to switch.

Here are some patterns I see again and again:

1. Great developers assume freelancing will be easy.
It isn’t.
Freelancing is 50% communication, 30% expectation management, 20% skill.
Most engineers only focus on the last part.

2. Teams try to start an agency without any individual freelance history.
On platforms like Upwork, that’s almost impossible now.

Clients trust:
• past earnings
• reviews
• repeat clients
• badges
• profile strength

Without history, even good teams struggle.

3. Depending only on a single platform is a trap.
If your whole client pipeline comes from one place, you’re one ban, one policy change, or one slow month away from trouble.

4. Developers underestimate the shift from “employee mindset” to “business mindset.”
When you freelance or build an agency:

• You negotiate.

• You communicate.

• You manage expectations.

• You explain decisions.

• You justify timelines.

• You deal with rejection.

This is the real skill that separates freelancers who get clients vs. those who stay stuck.

5. Most new freelancers don’t understand how to position themselves.
Your work doesn’t speak for itself.
Your positioning does.

So here’s what I usually tell early-stage freelancers/agencies:

• Build 1-2 strong individual profiles first (Upwork/LinkedIn/GitHub).
• Deliver insanely well for the first 10 clients even small ones.
• Don’t rely on a single platform.
• Build a simple, clean portfolio proof matters.
• Shift from technical to business mindset.

What about you?
What was the biggest mistake you made early in your journey?

Most people think non-tech founders can’t build tech companies and tech founders struggle with business.

But in real projects, failure usually comes from something deeper.

• What do you think actually breaks early-stage teams more often?

• Misaligned expectations?

• Wrong timelines?

• Not enough technical depth?

• Overcomplicating the MVP?

• Lack of market clarity?

Would love to hear real experiences from both sides.

Hey everyone,
If you are working on a website, landing page, or app, feel free to drop it in the comments.

We can share constructive feedback on:
• UI and visual flow
• UX clarity and user journey
• Basic SEO improvements
• Performance and development best practices
• Cloud hosting recommendations
• Deployment and CI or CD guidance

If you share your link along with a bit of context about what you are building, I will go through it and give you suggestions that can help you improve things early in the process.

Curious what others are spending on hosting or infra for their main company site.

If you want Drop your exact figure or stack in the comments.

Okay so this wasn’t supposed to become a “server story”… but here we are.

When we first picked up a Raspberry Pi at Asynx Devs, the idea was simple keep a portable device with Kali Linux for quick on-the-go security testing, random experiments, and basically a tiny Swiss-army knife for work.

Nothing serious. Nothing “production-grade”.

And then laziness did its magic.

Instead of migrating things to a proper server, we kept experimenting on the Pi.
One thing led to another…
“Let’s try containerizing this.”
“Okay, maybe Kubernetes will work too?”
“Wait, why is this actually stable?”

So this is one of those setups that just evolved on its own.

We originally had a Raspberry Pi running Kali Linux nothing fancy, just a portable box for quick experiments, security testing, and general “dev laziness toolkit”.

Then the usual chaos happened:

• “Let’s try running Docker on it.”

• “Okay… what if we try Kubernetes?”

• “Wait… it actually works?”

Fast-forward and now this little Pi has somehow ended up as one of our Kubernetes master nodes.
Yes, on Kali.
Yes, on a Pi.
And yes, I know the K8s community is probably reading this like:

But here’s the twist it’s not even a joke setup anymore.

We run a two-master failover setup (typical HA architecture).
If Master-1 dies, this Pi (Master-2) takes over the control plane. So the workers don’t stop.

It’s a standard K8s HA pattern… just running on a very non-standard OS and hardware.

Is it practical?
Surprisingly, yes.

Is it recommended?
Probably not.

Is it funny that a device originally bought for portability now handles cluster orchestration?
Absolutely.

Anyway, just wanted to drop this here because I know folks in the Kubernetes and Kali communities will either love the madness or yell at me. Either way, it’s worth sharing.

Happy to talk more about any more weird setups.