This entire conversation is a masterpiece!

Just picture this convo somewhere in nature, at night, by a fire.

Thanks for the tip!

Here's an update on Tiny Portals!

Not that we discovered America, but our voyage revealed new horizons that prompt us to seize the opportunity and...

- Sharpen our vision and revamp positioning - Enhance our feature arsenal - And prepare for the next étape of discovery

So... Instead of a "freelancer managing clients in simple portals"...

Now it's a tool for any high-volume collaboration with external stakeholders.

- Manage your freelancers - Give your clients a branded space - Work with internal pods

__ Ping me on LN https://www.linkedin.com/in/daliborbelic/, and I will unlock unlimited access for 6 months for you

One could argue that this does not apply to larger organisations. However, that opens up many questions regarding work culture, productivity, overhead and, ultimately, ethics.

I see a similar issue in 2025, but with vibe coding.

It all boils down to the 3 key factors: speed, quality and cost. And you can't have it all

Know your trade-offs.

How do you achieve speed and quality at the same time?

To quote one movie character: "Bro, when you can't fix a problem with money, you fix it with a lot of money."

Jokes aside, you find the crème de la crème of engineering, and pay as much as they ask for.

Speed + Quality = $$$$$

On the other hand,

Speed + Cheap = Crap Quality

Cheap + Quality = Slow

With vibe coding, you have none of those. The initial speed advantage will disappear once you need to maintain the mess.

Tnx for the comment. Discussing tools (in this case, vibe coding) naturally raises the issue of what skills are actually needed to use them effectively, such as prompting, which in turn leads to a broader question about the role and relevance of traditional software engineering skills. It's a whole other topic...

You can create value with vibe coding. As I said, know your trade-off, your context.

You wouldn't use a hammer to fix a watch, would you?