Jon Bauer

@googlecalendar iOS and Web via Google Apps account

@coveloper Hi Jon. Could you let us know how you're accessing Google Calendar (Android, iOS or browser)? We'll do our best to help.

Is anyone else getting Google Calendar event spam? I’m getting phishing attempts disguised as calendar events. Be careful out there.

@twannl I am Claudifying an existing project but we still support iOS 14. I feel like I have to make a Skill that specifically does not use the latest best practices. Ex. We can't use Observable, or even .task 🙈 . .

My iOS Agent Skills are packed with knowledge. I even include things you'd think an LLM already knows, like: - "Use Observable instead of ObservableObject" - "Use async/await instead of DispatchQueue" You might think Agents know these things, but in my experience: - They need strict guidance - They still make rookie mistakes - They get influenced by your code patterns, which often still use older APIs Even though training data is there, my Agent Skills guide your agents toward better iOS development. The risk of this approach is token usage. An inefficient skill will eat your context, leaving less room for the actual task. That's why my skills are: - Optimized for token usage - Designed for Agents navigating through reference files Code examples are intentionally minimal: just enough for an Agent to know what to do, nothing more. The latest release of my Concurrency Agent Skill saves ~4,000 tokens per query through smart routing, with zero loss in knowledge depth. Quick install instructions below 🚀 What Agent Skills are you using for iOS development?

Xpt 0.4.0 is out. Includes full test suite, handles branch renaming, and now we have a mascot, Point! github.com/coveloper/xpt

@amasad @Wefunder Also glad I invested then! Happy to see Replit keep growing!

It’s unfortunate that most people don’t have access to startup investing. I’m so glad we did a community round and encourage more founders to do it. @Wefunder makes it straightforward (and fun!)

Xcode users: If you're tired of managing breakpoints between git branches, I've made something for us. Automatically save and restore breakpoints with Xpt. Install and forget, just switch branches. Feedback, issues or PRs welcome! github.com/coveloper/xpt

Great session, look for me in the front row!

Apple showed off some really beautiful Apple retail stores today.

@sdw Pleasure meeting you at the coffee shop today! 🤝

@marcusubani @EuCardano @larissa_health Great work @marcusubani ! Your tireless efforts to keep the community connected through @EuCardano is appreciated!

Finalizing @EuCardano F11 for the summer break – then tripling down on what truly matters to us @larissa_health 👩🏽‍🍼

@JJAllenTech @StewartLynch What’s wrong with using Keychain?

@StewartLynch Now why doesn't Apple have a system build in for support of something like this so we don't have to rely on a third party package. Seems like a very common thing apps need.

Your API key might be hiding in plain sight. In this video, I’ll show you how to extract one from a compiled iOS app and then how to protect it using Swift ConfidentialKit. #Swift #SwiftUI #Xcode Watch now: youtu.be/FfXK0IrX0p0

Day 1 sessions from GDC Geneva have been published! @globaldigitalcollaboration?si=2BU7wn3-te8g3K6z" target="_blank" rel="nofollow noopener">youtube.com/@globaldigital…

At The Global Digital Collaboration Conference in Geneva. It’s so inspiring to watch the world adopt Verifiable Credentials. and Digital Identity. Great people are changing the world for the better!

Swiss trains are the best. 🇨🇭

Happy to be back in the EU for a while and catch up with some folks!

I like this image by @lehoho248.

I'm so glad Vibe Coding became a thing before I retired. But what was I doing for the last 30 years? 😭

@levelsio wow

Just closed my PayPal account Apparently they charge you money for inactivity every year?

Excited to be at DICE in Zürich talking about Digital Identity and Verifiable Credentials!

@krzyzanowskim Should NSImage be marked @PreConcurrency ?

the actual problem and solution to the ridiculous swift Sendable thing. Make the "fake" "sendingNonsedable()" function return the non sendable value type only to use in @ Sendable closure, that otherwise is an error. Explain that to the newcomer without having a Stockholm syndrome.