Do you remember opening a project and already feeling tired?
Not because the problem was hard, but because you knew what was coming.
A missing character. A library that almost works. An error message that helps everyone except you.
You open Stack Overflow.
The accepted answer is from 2016.
It doesn’t apply anymore.
You scroll. You try again.
At some point, you close the editor — not because you solved it, but because you ran out of patience.
Lately, many developers describe a shift toward vibe coding — a more fluid, flow-based way of working.
Does that resonate with you?
Has vibe coding changed how you approach problems, or do you still prefer the old, logic-heavy grind?
Top comments (0)