Todd Hoff @[email protected]

@sharptechpod In the dorm room, someone might point out that the Culture series covered this topic long ago; that a white heteronormative Western view of what people want isn't universal; the hedonic treadmill puts hard limits on human satisfaction in any environment. Now pass the dutchie.

The Economy in the 22nd Century, Amoral Tech and Silicon Valley Micro-Culture, What Nvidia Is Getting From Groq sharptech.fm/member/episode…

@merowing_ My experience is the code is quite good usually. Real names for everything that makes sense together. Good coupling and cohesion. Far better than I would have expected.

"LLMs write terrible code" No. YOU suck at learning how to use new tools. You're feeding it nothing, getting the average of its training data, then complaining about it. Saw it with my tools: some learned and got 10x out of that time, some complained. merowing.info/posts/stop-get…

It's Released: Max Workout 5.0 for iOS 26! apps.apple.com/us/app/max-wor…. I love the new look with Liquid Glass. Plus a new AI personalized training schedule and all new everything.

@jacobtechtavern A downside of using enums is that they centralize the logic rather that making independent components. This can be a strength, but it can be a mess too.

Advanced SwiftUI tip for iOS devs: I love using enums to implement my design systems. You can get progressive disclosure, intelligent defaults, and full customisation within your system. (composition shills are welcome to spew vitriol below)

@azamsharp Except for code not in a view which is why I don’t like using the environment.

Stop Overengineering: SwiftUI Already Has Dependency Management Built-In Link to the full member only video in the comments #swiftui #iosdev

@azamsharp How else would you do it?

Updating List of movies from sheet using Binding in SwiftUI. * Although this works but for me personally, it never felt right.

@designerants Are there new app store guidelines for images? They used to have to be just of your app. These are all very much not that.

This developer is following my guidelines for screenshots. Pretty good, but can be improved. Some feedback: - Low contrast between background and text. White and orange have insufficient contrast. - Girl with a more orange t-shirt will not draw as much attention. - Images 3 and 4 should be moved to first positions. They show your app in action, but you need to remove noise from them, especially the iPhone below, which captures lots of attention without adding value. - Most texts are hard to read. When you design in Figma (or any other software), I recommend zooming out to match the font size to the smallest device you want to target. Double your text size. - You can hide some UI elements, like the subtitle in screenshot 2. -Political images can split your audience. Heavily test that image or avoid it. Copywriting: - While you showcase benefits, you don’t show pains. "Does your gallery look like this?" "If your gallery looks like this, use this app to sort it out". This type of copy can trigger the "guilt" side of users and push them to take action to fix their mess. - You can add some numbers like: sort 300 images in 3 minutes, sort 37.6 images in 10 seconds, 80% of photos will never be used again. (Validate your numbers)

@azamsharp I like putting the select tab and a tab router for each tab in an app router and then passing the app router through the environment. This makes it so you change tabs on an open url and navigate to other views.

Multi-Tab Navigation maintaining individual NavigationStack. Navigation chapter is coming along nicely!

@natpanferova That was very helpful. Thanks. Interesting that .matchedTransitionSource does not work on ToolbarItemGroup.

iOS 26 comes with a few updates to sheets, like the Liquid Glass background in partial height and morphing transitions from the toolbar buttons that present them. My new blog post explores how we can take advantage of these changes in our SwiftUI apps: nilcoalescing.com/blog/Presentin…

@sharptechpod Great episode as usual. From a developer's perspective, the in-app purchase process is not good. Developers can create better user experiences than Apple, app store rules prevent that. Having to shell out to a website means the experience will never be as good, which is a shame.

Apple and the Power of Platforms, AI Comes for Google Search, ChatGPT Comes for Higher Education This episode is free for everyone. sharptech.fm/member/episode…

A potential origin of Cold Harbor in Severance. The first research station for the start of the Eugenics movement was in Cold Spring Harbor on the North Shore of Long Island. Kind of fits.

@Culture_Crit Paul is not hero. He’s a lesson. I’m surprised JRR didn’t get that.

JRR Tolkien hated Dune because its ethics are fundamentally wrong. The Lord of the Rings is a profoundly different take on Good and Evil — and how to live a moral life. Here's why… (thread) 🧵

@alexbdebrie Worth another look now.

Cool release from the AppSync team. Lots of good stuff there. Excited to be able to use this separately from GraphQL

@houlihan_rick What did u think of the future directions?

I asked Claude to describe the history of Single Table Design. It was a surprisingly good read. claude.site/artifacts/93b2…

You can Crawl entire website with Claude 3.5 or GPT4 with @firecrawl 💯 Its open-sourced and code in github - Turn entire websites into LLM-ready markdown or structured data. Scrape, crawl and extract with a single API. - Crawls all accessible subpages and give you clean data for each. No sitemap required. - The greatest benefit is that the extracted data is catered for LLM-based pipelines. - The api is self hostable and opensource ----- Some benefits of firecrawl 1. handles crawling (with or without sitemaps) 2. runs headless browsers scalably 3. handles bot protections and proxies 4. a team of dedicated engineers to solve the millions of edge-cases on the web for you 5. quality formatting to markdown by default Beautiful soup doesn't generalize, thats why we built firecrawl

@jeremy_daly Both are pretty great.

I don’t know what’s funnier, the joke itself, or the fact that most people don’t seem to get it. 😂 #perfect

A requirements document, but we are closer than ever to that document actually generating and documenting a system. That has always been the dream.

The prompt captures the intent. It’s also a form of compression. Comments are hard. You already have the prompts so now they are easy. They scale with subsystem size. Even a million lines of code are generated the comment takes the same effort. I’m not saying you don’t need

What and how much to comment in code has always been controversial. It ranges from write a full spec to don’t comment at all. I’ve always felt comments should be about purpose. What does this code accomplish and why does it work the way it does. Intent.