med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

413
active users

#swiftdev

0 posts0 participants0 posts today

I think I could make a good Mac music player app. Already have experience with the lower level APIs for audio playback and seeking and visualizers and whatnot. It would not re-organize your music files and could also gracefully handle if some of your music is gone temporarily because you unplugged a hard drive or you’re on a different network. It could have smart playlists based on metadata info and such and maybe one day I would cave and do AI-generated playlists. #indydev #macapps #swiftdev

Xcodes 16 AI thing is giving me incredibly mixed vibes. Sometimes it will suggest exactly what I need, and sometimes it hallucinates interfaces and objects that don't exist and makes me write code that won't ever work.

I am trying to work with a foreign interface and exploration is very frustrating.

I feel quite clever for coming up with this. Since this API returns relationships as JSON arrays of URLs instead of IDs, I created this Relationship type which I can then use a service to download the relevant models when needed. #swiftdev

MMVM in SwiftUI based apps is just a slightly different version of MVC, and closer to the original Smalltalk MVC than the whole UIKit view controller thing ever was.

We could call view models controllers and it’s basically Smalltalk MVC. The AppKit/UIKit conception of MVC is the outlier. #swiftdev

I’m yet to encounter a Swift app architecture which promises modularity, testability, and maintainability where I don’t think I could have written more modular, testable, and maintainable code by just applying basic OOP principles. I remain open-minded. #swift #swiftdev

For those interested, here is my software development process.

1. Write some really good code that doesn't actually fix the problem.
2. Start fixing a bunch of stuff that is unrelated, but bothers me.
3. Get frustrated that my PR is WAY too big.
4. Try to back stuff off, but break xcode.
5. Step away and take a break.
6. Have a eureka moment on how to actually fix the problem.
7. Open Fork and go over each change and cherry pick individual changes onto a new clean branch that only fix the actual problem.
8. Test.
9. Ship.

I wish I could skip to step 6, but it's just not possible. Steps 1-5 are essential.

🤷😅

The Apple Platforms Developer Challengers Survey is now up and ready to fill in. Please share widely:
forms.gle/KSQEcLZxBUQitmVB9
The purpose of this survey is to better understand challenges and difficulties faced by developers when developing for Apple platforms, and to determine possible areas of improvement.
Presented by Swift Dev Collective, an independent collective of developers using Swift.
#iOSDev #macOSDev #SwiftDev #SwiftUI

Google DocsApple Platforms Developer Challenges SurveyThe purpose of this survey is to better understand challenges and difficulties faced by developers when developing for Apple platforms, and to determine possible areas of improvement. (Presented by Swift Dev Collective, an independent collective of developers using Swift.)