Traditional professions like doctors, judges, and the like need specialised academic guidance (certificate) + experience. I agree.

But what about technical and humanities? So far, everyone has argued that a university will bring contacts (I'm not arguing, that's true... but the same can be done with hustling/projects).

Hey everyone,

As a first-time founder gearing up for my first launch, I found myself getting overwhelmed by all the moving parts. To keep my sanity, I started building out a super-detailed checklist.

I work with startup teams and use AI tools almost every day for writing, research, support, and more. It saves a lot of time, no doubt. But there are still things AI just can t do well.

For example, when reading customer feedback, AI often misses the real meaning behind the words, like when someone sounds polite but is actually unhappy. Or when making product decisions, AI can list pros and cons, but it doesn t really understand the bigger picture or timing like a human would.

I have been building, learning, searching, investing for the last 6 years, back to back, non-stop. I feel I have officially reached burnout. One week I am super into building and I code new things like crazy. And the next I just want to chill and go surfing lol. Do you go through a similar phase? How do you deal with the constant change of emotions?

A lot of us tend to neglect our health, being so entrenched in the work we're doing. That's unfortunate because without health, we can't really do much. It should be prioritized above all.

Prioritizing health starts with simple habits. Personally, exercising even just 45 minutes a day (usually in the morning) - whether that's lifting weights or shooting hoops has greatly improved my posture, energy levels, confidence, and mental clarity. It sounds cliche, but I really do believe exercising is a super-enhancer.
What is one healthy habit that has yielded improvements for you?

@charlie_hb started quite an interesting thread where he outlined on which days people lose their streaks the most often.

He showed some stats regarding days in a week, but I am still lacking the reasons.

The most common ones I have heard were:

I think many tech product builders, including myself, can easily fall into tunnel vision, whereby I am overly convinced that the feature we re working on is clearly justified. With vibe-coding tools, the cost of building new features has also dropped dramatically. But lower development costs didn't seem to translate to product growth in my organization. Many newly launched features still receive little adoption, or have a hard time "syncing" with the rest of the product.

So I m curious: how do you decide when a feature is actually worth building? Do you wait for repeated user requests, test a lightweight version first, trust your product instinct, or rely on behavioral data before committing?

The world has changed rapidly over the past two decades with the internet, new technologies and the accelerated transfer of information.

Anyone not actively working online or in IT may have trouble keeping up with these "tech trends." This is especially true for older generations who did not have the opportunity to grow up with computers as it is today.