@tclementdev @cocoaphony now I understand. It's because the closure is executed as soonas the task is created. Thanks.
Markos
@qnoid
- 11 Followers
- 19 Following
- 15 Posts
@tclementdev @cocoaphony my understanding is that the weak entry in the capture list is done when the closure is created. So the Task has a weak reference to self. Whereas the guard is to avoid execution in case self has since been deallocated.
@tclementdev can you please expand?
I have found comfort in the words of @steipete talking openly about what's possible. Demonstrating a role for software engineers that is achievable with agentic AI. It is this PR by mattt that opened my eyes to how empowering it can be as a solo developer to use Copilot as your code reviewer. It's the tinkering by @stroughtonsmith that makes me think what more value I can create. It's the path these men carve for others.
https://github.com/mattt/EventSource/pull/17
https://youtu.be/muh8ooHd7yU?si=eOuJS_FenmfndeED
https://mastodon.social/@stroughtonsmith/116018205506714527
@tonyarnold welcome back Tony! It's good to hear you have found some balance. We could use your voice as we navigate the tides. Keep writing and find solace in the fact that we are all in this boat together. We are all trying to weather the storm while trying to keep calm and carry on.
@cocoawithlove @stroughtonsmith you don't think the guideline is in relation to SwiftUI rather than an all encompassing? I can't see how async/await can be a substitute for Combine.
"Follow SwiftUI patterns with clear separation of concerns. Avoid using the Combine framework and instead prefer to use Swift's async and await versions of APIs instead."
Businesses might have to bear the brunt of hiring graduates as they develop their skills. Which is no different to how it's always been! The question that needs to be answered is both how they will develop their skills in an environment where agents write code and what role would they play. This is where I would like to hear from business schools the likes of Stanford, Harvard, Oxford etc.
I am still wrapping my head around all that insight to try to take it all in. It's worth watching that discussion twice. This is what's going through my head:
* Universities will become relevant again for the same reason they've always been important. Develop your critical thinking, teaching you how to do research.
* Junior software engineers will need even more help and support to become experienced. I have no idea where, how or who will take that responsibility. Let alone willingly.
* Universities will become relevant again for the same reason they've always been important. Develop your critical thinking, teaching you how to do research.
* Junior software engineers will need even more help and support to become experienced. I have no idea where, how or who will take that responsibility. Let alone willingly.
@steipete your work, writings and talks do the heavy lifting. My advice would be to not waste any time arguing. You spent 2 hours in that podcast talking to @gergelyorosz. That was gold. Especially because Gergely has a background in software engineering who understands both product and business.