maximg68

I also experienced pushback when I shared a similar skill with some of my colleagues (and it didn't mention "vibe" in the name). The main objection was "I am doing careful planning upfront, so I have the same level of understanding of the code as before".

Maybe they do. In my experience, the agent was going over the scenarios that I failed to consider during the planning stage, and it was net positive. I haven't tried it with a spec-driven approach.

After noticing a drop in my understanding of the code I ship, I built and started using a similar skill ("Quiz me on the PR or the current branch"). I didn't tie it to a specific commit, though - to me it makes more sense to look at the PR as a whole.

So far I was positively surprised with the questions it could come up with.

Makes sense. I started asking Claude to grill me on the PR to make sure I understand it.

When I was actively using my Macbook 2014, I did the same, though to lesser extent and in a uniform way. The edge was way too sharp.

I would expect that this should be rather easy to confirm (or disprove) by breaking down the suicides across the age/profession/social status.

This does not have to be "either-or". As we see an increased focus on teamwork this could evolve into a shared (electronic) team logbook.

Sounds very promising, I can think of some professional applications in software development. Signed up.

I see a market for contactless EEG readers emerging.