Justin Williams
23.4K posts

Justin Williams
@JustinIt4Fun_
Engineering Leader & Builder. Formerly @Blocks, @CashApp, @Handy & @GoldmanSachs and @NASA Intern/Rocket Scientist. DMV Native. BK Resident.

CPU and thermal performance in a SwiftUI list explains why we had so many hitches. Even at rest, no scrolling, the CPU screamed at 100% capacity to render every gif, and well past 100% (distributing work across CPU cores) when I scrolled. The “Very High” energy impact rapidly heated my device. The measured thermal trace crept up towards Serious. When I wasn’t paying attention, the app was even killed by the OS, presumably hitting a critical thermal spike. After giving a serious beating to my shiny new A19 chip, the same feed in UIKit produced comparatively nearly trivial CPU and energy usage. * At rest, UIKit dropped as low as 11% CPU utilisation, vs a consistent 100% for the SwiftUI version * Energy usage correspondingly held at High for UIKit, vs Very High for SwiftUI. I gave up waiting for the thermal profile to hit Fair after 3 minutes. Read my scientific performance comparison right here 🧪 blog.jacobstechtavern.com/p/swiftui-vs-u…



im just copy pasting now with codex 5.4 high (NOT xhigh, NOT medium) before every pr. it's beautiful


.@carrynointerest says Manus is one of the most underrated AI products today, and that it was a genius acquisition by Zuck: “There are simply things that you can do with Manus that no other inference provider or product can do. I would reveal them, but that’s alpha for me.” “What Zuck realized is — 'I don’t have to care about inference or who’s giving it to me, because [Manus] figured out some really special stuff around how an LLM processes data in and around a web browser.'” “And now he’s already integrating it with Ads Manager. It’s a great bet.”

In our conversation Marc Andreessen makes the case that the beating heart of our civilization’s progress is the founder: “You’re much more likely to build something important in the 21st century if you start with a founder and train them in management than if you start with a manager and try to train them to be a founder.”

I feel like I need to start fighting this shit with more linters. They are just not listening.



Most managers already know how to run great 1:1s. They choose not to because their org punishes them for it. Every experienced manager has heard the advice. Let your reports own the agenda. Focus on their growth. Coach instead of direct. They learned it in their first leadership training. They’ve read the books. They’ve nodded along in the workshops. They still run status update 1:1s. And the reason is structural. A manager who develops their reports well creates people who get promoted out, get poached, or start asking for the manager’s job. A manager who runs low-energy status updates keeps the team stable, dependent, and unlikely to leave. HR tracks attrition as a negative on the manager’s scorecard. Nobody tracks “I developed three people so well they all got promoted in 18 months” as a win. The incentive math is brutal. Develop your people → they leave → you backfill → you spend 6 months ramping a new hire → your team’s output craters during the transition → your performance review suffers. Run status updates → team stays put → output is predictable → you look like a stable operator. This is why advice like this resonates massively and changes almost nobody’s behavior. The managers reading and bookmarking it will open their next 1:1 on Monday and ask “so what’s your status on the Q2 deliverables?” Because their org rewards exactly that. The managers who actually run great 1:1s tend to work at companies where developing people out of your team is celebrated. Those orgs are rare. And until that changes, most 1:1s stay exactly where they are: status updates with a calendar invite.


