wsostt

You might have missed the ending.

> Also, for those wondering, I really really hate the Pixel 7 Pro.

Are they saying that the same 12% of people eat half of the consumed beef each day? Or that 12% of beef consumers eat half of the daily consumption but that group’s membership changes each day?

If I eat a steak and cheeseburger in the same day, am I part of that group or am I never part of the group because I only eat beef 1x per week?

Totally agree. I’ll treat Google’s future Gmail AI announcement with a lot of hesitancy. Forget a 3rd-party implementation.

I would add that good writing is required for all career advancement.

Senior engineers or architects may do more design than coding and the design needs to be conveyed likely as writing and hopefully a couple diagrams.

Managers absolutely need to be good writers to communicate effectively, advocate for their team, and tell the story of the team’s work.

If you’re an engineer and want to have a higher level job than you have now, getting better at writing is only going to help. I’m not saying it’s a MUST because I’m sure there’s some outliers, but it won’t hurt.

Going to check this out.

FYI - your Obsidian and Logseq links on the honmepage are swapped.

I don’t think the pilots are being scapegoated when they ditched a working plane in the ocean. There were a lot of things that led them there and a lot of reasons it happened, but this crash was avoidable with proper procedures.

If they’re unhappy with their own API, this could provide an abstraction layer for the app. They rewrite their client to use this API and it frees up two teams to work (almost) independently. The UI team can work on their roadmap while the backend team fixes the internal API or retires the logic and implement it into this new layer.

I’m not saying they’ll do this or that it makes sense. But I’ve definitely done it in much smaller projects.