Curtis Herbert

@parrots
1.6K Followers
122 Following
2.5K Posts
Expect 👨‍💻, 🎮, 🏂, and general 🤓 too · Elder millennial · Neurospicy (AuDHD) · Building Slopes in the open · Apple Design Award winner · “An app mogul” - Apple
Homehttps://curtisherbert.com
Slopeshttps://getslopes.com
👋 Threads keeps improving their fediverse support and just rolled out being able to see replies from Mastodon(/etc) accounts *in* Threads. So it's no longer a black-hole if you reply to me on there: @parrots01
Turned on Fediverse sharing for my threads account. Still not as active on there as I was Twitter, but I’m never on mastodon so 🤷‍♂️. Probably better to follow that. @parrots01
Another third Wednesday coming up soon! We’ll see you this Wednesday, the 18th, 7pm at Barchetta Pizza. https://boulderos.com
boulderOS

boulderOS monthly gathering of friendly people in the iOS / watchOS / macOS (and adjacent!) space.

Another third Wednesday coming up soon. We’ll see you this Wednesday, the 16th, 7pm at Barchetta Pizza. https://boulderos.com
boulderOS

boulderOS monthly gathering of friendly people in the iOS / watchOS / macOS (and adjacent!) space.

Consolidating social networks. Taking a break from checking Twitter in favor of Threads (it's giving good community vibes). Not sure if I'll delete my Mastodon account, but prob not going to be logging on here.
All I want for America's birthday is Xcode beta 3 (tomorrow? 🤞) to fix wired debugging for iPhone. Wireless install + launch is so slow, and the workaround in the release notes doesn't work for me.

@BenRiceM You should have full control to update / cancel LA shit while not in the foreground. The only limitation is you can't *start* one from the BG.

You'd have to use background refresh or something to get some runtime, that's all.

@joel yeah, this it the recording UI. This is the card that shows when you search, or tap on a run on the map.

I've been building towards nav for 2 years (screenshots 2 + 3). But I need this card in place first to expose "navigate to here"

@ryanashcraft just moved it from JSONB -> JSON. Didn't need the efficiency B grants for queries and all. But, turns out, B was actually like 8% less disk space lol.

Ugh - am I really going to have to split out this JSON Postgres column entirely from my main DB and move it to something like Mongo? The single column is eating up like 49gig out of my 51gig DB.

This'll be a fun summer project. 😳