There are quite a few comments here talking about how comparing images from feb/march isn’t useful. Here’s data on what’s going on. This snowtel location is within the Utah picture in the article.
I've been vibe-coding a Plex music player app for MacOS and iOS. (I don't like PlexAmp) I've got to the point where they are the apps I use for listening to music. But they are really just in an alpha/beta state and I'm having a pretty hard time getting past that. The last few weeks have felt like I'm playing wack-a-mole with bugs and issues. It's definitely not at the point others will be willing to use it as their daily app. I'm having to decide now if I keep wanting to put time into it. The vibe-coding isn't as fun when you're just fixing bugs.
This has been exactly my experience too. I switched from Spotify to Plex, but discovered there really isn't a music focused desktop player. So I vibe coded one, exactly how I want my music player to work (albums not playlists/tracks as the central item). I was so happy with my desktop app, I built a mobile version to use instead of PlexAmp. There are some bugs I'm ironing out, but they are both I've stopped using PlexAmp and Spotify entirely.
I very much like the no LLM output in communication. Nothing is worse than getting huge body of text the sender clearly hasn't even read. Then you either have to ignore it or spend 15 minutes explaining why their text isn't even relevant to the conversation.
Sort of related, Plex doesn't have a desktop music app, and the PlexAmp iOS app is good but meh. So I spent the weekend vibe coding my own Plex music apps (macOS and iOs), and I have been absolutely blown away at what I was able to make. I'm sure code quality is terrible, and I'm not sure if a human would be able to jump in there and do anything, but they are already the apps I'm using day-to-day for music.
It's abstraction, but for things you don't care about. I was an engineer early in my career and I felt exactly as you. All that stuff was in one ear and out the other and I couldn't for the life of me make sense of it.
I moved to product and finally got it. A PM can't explain the same concepts/ideas/initiatives/etc every meeting because the whole meeting will be spent doing that. They give it a name.
Take the strategy example. In the early stages of forming this strategy, part of the PMs job is to communicate it lots of groups of people. They have the same meeting 1-10 times depending on the size of the company. Then everyone who needs to know about this strategy has an understanding of what it is. Then the PM gives it a name. The next meeting, rather than having to explain it from scratch, they call it by its name.
You're either not paying attention when it is first explained (I don't blame you, a lot doesn't matter to an engineer), or you weren't invited to the meeting it was explained.