There's one good saying that
"Anyone who stops learning is old, whether at twenty or eighty. Anyone who keeps learning stays young."

This is so authentic, especially in the tech world, when everything changes so fast.

Before I would learn something first and then try to build with it

Now I often do both at the same time

I get an idea

Start building

Keeping a startup team motivated without money is one of the hardest challenges I ve faced, harder than growth or sales.

I ve worked on a few SaaS products with let s just say, not-ideal budgets. And honestly, the hardest part wasn t traction. It was morale.

As a new founder, I m starting to feel like there s a rude awakening waiting on the other side of building something.

You spend months obsessing over an idea. You build it. Break it. Fix it. Change things you were convinced were right. Question whether the idea is any good at all. Then eventually you get to that incredible moment where you can finally say:

I built something. It exists.

And then you realize...

I used Fable 5.1 for coding whole day and it's definitely the best publicly available model for this purpose. I'm curious what are your experiences related to other use cases.

I m a UI/UX designer and recently started exploring how AI can help bridge the gap between a Figma design and a more functional prototype.

Traditionally, I d create the UI in Figma and then build interactions separately. With the newer AI tools, I m curious how designers are changing this workflow.

For those who work with AI-assisted prototyping:

• How do you go from Figma designs to functional prototypes?

• Which parts of the process does AI handle well?

• Where do you still prefer traditional Figma prototyping?

• Have you found any tools that preserve the original design particularly well?