Great content man, keep it up! Would really like to see your preferred approach of identifying and improving app performance (besides the usual LazyLoading and weak self references) E.g. I'm working on a legacy codebase, would like to do an overall performance report to see what's slow, then improve those slow areas. What would be a good way to tackle something like that? Maybe profile screen by screen? Thanks!
I’d start with overall app architecture and design and see if you can make improvements there. If there’s networking involved, I’d check both client side and server side performance for load times, make sure data is being paginated, etc. I’d also try to implement performance testing. If you need help with something like this, let me know! I do contract work like this often
3:54 I've noticed that when you specify an asset directly from Storyboard (and xib as well) to the GUI navigator, it's not tracked in the code (e.g. cmd+shif+f to find the asset name). so I'm wondering if this method will track that as well?
Is there a problem with that? Both guys are awesome content creators, and I learn from both of them. If everyone thought the way you did, nobody would ever learn from anyone else. Appreciate the comment buddy, even if it’s hate 😂
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
Gonna buy the lifetime membership right now 🔥🤝
UGGHHHHHHHH the new debug stack trace feature is clutch! What a great find Stephan! Thanks for that one!
Wow didn’t know about the stack tracing! That’s cool
And I totally forgot about Previewable, thanks for the reminder and tips!
5:10 I literally spent 4 hours this morning debugging a run-time error without knowing this feature. 🤦♂ I wish I watched this earlier!
Thanks!
Great content man, keep it up!
Would really like to see your preferred approach of identifying and improving app performance (besides the usual LazyLoading and weak self references)
E.g. I'm working on a legacy codebase, would like to do an overall performance report to see what's slow, then improve those slow areas.
What would be a good way to tackle something like that? Maybe profile screen by screen?
Thanks!
I’d start with overall app architecture and design and see if you can make improvements there. If there’s networking involved, I’d check both client side and server side performance for load times, make sure data is being paginated, etc. I’d also try to implement performance testing. If you need help with something like this, let me know! I do contract work like this often
3:54
I've noticed that when you specify an asset directly from Storyboard (and xib as well) to the GUI navigator,
it's not tracked in the code (e.g. cmd+shif+f to find the asset name).
so I'm wondering if this method will track that as well?
You just shouldn’t be using storyboards lol
2:35 he is getting inspired by Swiftful thinking and Vincent in his browser rofl
Is there a problem with that? Both guys are awesome content creators, and I learn from both of them. If everyone thought the way you did, nobody would ever learn from anyone else. Appreciate the comment buddy, even if it’s hate 😂