Roy Derks

Vibe coding is not a silver bullet.

The value you get from coding with AI depends a lot on the developer and the problem you're trying to solve.

The 4 levels of vibe coding

(this sounds as a joke, but it’s actually how people build now)

SF does not just have tech events…

First marathon ✅

Thank you, ChatGPT

I don't trust developers that use test coverage percentages as quality score for their project

Junior Developers are doomed...

Says the guy who doesn't know how to code and did not try AI to vibe code himself

According to experts AI will ruin the world.

What did the same experts say about Y2K?

Doomsday.

Developers love to overengineer.

That’s why I like vibe coding. Just build something simple and get it in front of people fast.

And worry about scaling when you actually do reach scale.

Stars and downloads signal hype or interest but they don’t prove real-world adoption or value.

If you care about adoption, you need proper usage metrics. Not vanity numbers.

People star repositories for all sorts of reasons:
- To stay updated on changes
- To bookmark it for later
- To show support

And downloads are inflated too: automated trackers, bots, and CI/CD systems all inflate the counts.

That means the JS version has a much higher stars-to-download ratio — about 3× more stars per 1,000 downloads than Python.

What does this tell us? Not much.

There’s no causality between starring a repository and actually using the library...

The Python version has been around longer and has ~111k stars, while the JS version has “only” ~15k stars.

But if you look at the ratio between downloads and stars, the story flips:
- Python: ~0.0058 stars per 1,000 downloads
- JS: ~0.0163 stars per 1,000 downloads

What does this tell us?

GitHub stars, npm and PyPI downloads look impressive on paper, but they don’t really measure real usage.

Let’s take LangChain as an example — which has both a Python and a JS version.

GitHub stars don’t tell you how much a library is actually used. Not even close.

Thinking is becoming a skill again

Every PM should vibe code

Race for the best models, who will win?

Check out the full video here www.youtube.com/watch?v=TMmi...

MCP Inspector is like Postman, but for MCP servers instead of APIs

If you could automate half your job, would you waste the time or use it to grow?

The way you spend that freed-up time will define your future.

Awesome MRR for a “boring” company

My number 1 employee

AI is not just for coding

Everyone’s chasing the next agent framework.
Few are asking what problems are actually worth solving.

The future isn’t no-code.
It’s high-context code.

Learning to code was just step one.
Now you have to learn how to explain code to a machine that writes it for you.

Coding used to mean "write every line."
Now it means "design the outcome."

You don’t need to remember how to reverse a binary tree anymore.
But you do need to know when one makes sense.

Knowing what to build and why just became more valuable than knowing how to build it.

Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. - YouTube

Check out the video and tutorial

- www.youtube.com/watch?v=TMmi...
- hackteam.io/blog/build-t...