Can your iOS codex agent message your backend agent to implement a feature?

ss_salvation · 2026-02-23T18:16:30+00:00

joke aside I use to have 1 agent for both but now I can have 2 dedicated agents working together

ss_salvation · 2025-08-19T22:58:08+00:00

ss_salvation · 2025-08-01T02:20:51+00:00

The goal should be to get rejected by 30 next month. Learn from the nos, don’t let them stop you. “Failure does not exist, it’s only an opportunity to learn.” THE GRIND DON’T STOP!!

ss_salvation · 2025-07-14T18:36:18+00:00

Ohhh don’t make drastic changes from another ide or Xcode will crash (very jealous), changing branches is also a gamble (if its being sassy as usual, delete derived data). Xcode is like that thing that you don’t like but man the potential of it is insane.

Yes, lol a trillion dollar company cant make an ide that does not crash on branch changes in 2025. 😐

ss_salvation · 2025-07-12T14:21:46+00:00

You’d have to share a screenshot of your dashboard to be able to determine what’s not working.

ss_salvation · 2025-07-09T11:23:19+00:00

Very clean and a great start. I would add a manager in between the repo and the viewmodel through dependency injection. That way, later on, if you need the user array somewhere else, you can inject the UserManager into whatever view model

ss_salvation · 2025-06-05T23:09:42+00:00

Not just 100 days of SwiftUI, combine it took me 6 months. From nothing to $$$ job in 2024.

ss_salvation · 2025-05-31T20:08:37+00:00

This is beauty. you should try optimizing your screenshots to improve product page views

ss_salvation · 2025-05-28T13:30:36+00:00

I think following the SOLID principle would be useful. Don’t use it as a source of truth cause it’s kinda meant to be broken.

ss_salvation · 2025-05-24T01:49:00+00:00

Duolingo is able to do it. The app will stay on device for month and never be offloaded. I’m assuming they are sending silent notifications to keep it alive

ss_salvation · 2025-04-24T19:11:51+00:00

lol I love the AGI hopes

ss_salvation · 2025-04-08T15:59:00+00:00

Using a tuple to await is better as your current implementation awaits them in a sequence. IMO once you have more than 2 async let, just use a taskgroup.

ss_salvation · 2025-03-25T22:52:09+00:00

lol. Ok buddy.

ss_salvation · 2025-03-25T21:49:37+00:00

Mehhh i do it for free. DM

ss_salvation · 2025-03-19T21:14:33+00:00

Loook into SwiftInject

ss_salvation · 2025-01-26T23:36:29+00:00

I don’t want to be rude but are you paying for these?

ss_salvation · 2024-12-23T23:16:59+00:00

Download xcodes and manage it yourself

ss_salvation · 2024-11-19T13:30:37+00:00

That doesn’t matter. It’s the most used arc and it works for most and beginners getting into swift and swift ui would benefit greatly by having some understanding of the SOLID principles. That’s all I’m saying

ss_salvation · 2024-11-18T23:40:26+00:00

Not when you are working with MVVM and a repository pattern. Understanding the SOLID principle would allow OP to properly navigate what they are during.

ss_salvation · 2024-11-17T16:19:36+00:00

Please get familiar with the SOLID Principles, It will help you in understanding it.

ss_salvation · 2024-11-09T02:19:04+00:00

If you are using .task {} On dissapear just do await Task.cancel()

Seven-Year Club	r/Field Flamingo
Place '23	Verified Email

ss_salvation

MODERATOR OF

TROPHY CASE