I do everything that is cryptography / heavy on binary encoding and most c++ manually. Doesn't mean you can't get assistance on building test suites or docs and such, but even there, the resulting tests and docs are often sloppy af. For private stuff I vibe everything, and everything is either a poc or a working alpha.
I also don't merge anything from anyone that I don't trust they know what they're doing into libs/runtimes that are widely used and supposed to be reliable. I do accept trivial things that smell like Claude's unwashed feet nowadays. Docs are fine, comment fixes are fine. But most often I get 1700- 4800+ PRs with not even the markdown slop cleaned up, and those I deprioritize to a point that I will never get to them.
There are repos where everything is vibed now tho. I do my best to not give in. I may be slower than the yolo, but I'm still 2-3x faster than I used to be, and can operate with 10x more precision. This morning, I only had to binary -> hex -> manually TLV-tag a thing 3 times before I, with assistance, caught all the bugs i wrote - took 2 hours or so. Last year, would have taken up to full day and way more than 3 rounds.
I also test my solutions actively: how robust is this? Where are issues in what i just WIP'd? What's off-standard? Is it complete? I have "agents" (=prompts) for all this.
Between that, attention to detail, willingness to throw things away and never think about sunk cost, and everything I miss in tooling built on the spot... life is good. Also when writing code. It's just a matter of finding a balance between not being lazy and not burning out.
I do everything that is cryptography / heavy on binary encoding and most c++ manually. Doesn't mean you can't get assistance on building test suites or docs and such, but even there, the resulting tests and docs are often sloppy af. For private stuff I vibe everything, and everything is either a poc or a working alpha.
I also don't merge anything from anyone that I don't trust they know what they're doing into libs/runtimes that are widely used and supposed to be reliable. I do accept trivial things that smell like Claude's unwashed feet nowadays. Docs are fine, comment fixes are fine. But most often I get
1700- 4800+PRs with not even the markdown slop cleaned up, and those I deprioritize to a point that I will never get to them.There are repos where everything is vibed now tho. I do my best to not give in. I may be slower than the yolo, but I'm still 2-3x faster than I used to be, and can operate with 10x more precision. This morning, I only had to binary -> hex -> manually TLV-tag a thing 3 times before I, with assistance, caught all the bugs i wrote - took 2 hours or so. Last year, would have taken up to full day and way more than 3 rounds.
I also test my solutions actively: how robust is this? Where are issues in what i just WIP'd? What's off-standard? Is it complete? I have "agents" (=prompts) for all this.
Between that, attention to detail, willingness to throw things away and never think about sunk cost, and everything I miss in tooling built on the spot... life is good. Also when writing code. It's just a matter of finding a balance between not being lazy and not burning out.