This probably doesn't qualify as vibe coding at all. The developer involved is an experienced Mesa contributor, and just tagging Copilot in commit notes doesn't tell us how much of the actual logic came from AI. Vibe coding implies someone navigating code they don't really understand. That doesn't seem to be the case here.

The hardest part is when, even after putting in some effort, the people around you look at you and say, “Nothing’s changed about your body yet.” It’s hard because it makes us lose our resolve when it comes to staying disciplined.

I hope I can manage it this time, because it's been quite a lot of work

Hot take: portfolios didn't democratize hiring. They just moved the gatekeeping from "did you go to the right school" to "did you have enough free time to build side projects." A single parent working two jobs is not less talented. They just had less margin. We keep calling that a skills gap when it's actually an access gap.

But be careful, this isn't going to benefit everyone. Those who already have a background in software engineering or cloud tend to benefit a lot from it. But for those who are just starting out or stuck in more routine roles, they definitely won't get anything out of this.

This raises an interesting question: is full privacy in an AI actually freedom… or just removing the only remaining safeguard? If no one can see or audit conversations afterward, how do you ensure the system doesn’t become a perfect space for abuse, fraud, or worse? At the same time, without that level of privacy, many people simply won’t use AI for truly personal things. Maybe the real issue isn’t “private or not,” but who gets to decide where protection ends and responsibility begins.