| Walking with Swift | |
| Github | https://github.com/phynet |
| Walking with Swift | |
| Github | https://github.com/phynet |
I made GitHub Copilot write a raindrop sound synthesizer in Swift (plus some SwiftUI and Charts) and wrote about how it feels, as an experienced developer, to wrangle an LLM-based coding assistant for Swift/Mac development.
https://www.cocoawithlove.com/blog/copilot-raindrop-generator.html
Hello network! Katharina Gopp and me are interested in orginze an event targeting female audience that code in iOS/MacOS, but first we need some input to shape it. Would you like to help us?
#womenintech
https://forms.gle/vcWAvjZkjCZ2sbec8
Thank you for your suport! 💪
We would like to create a iOS conference or workshop event targeting women of all experience levels and backgrounds to share experiences, ask questions about iOS development, and enhance soft skills. Men are also welcome to attend, but our primary focus is increasing the participation of women in the field and to do so, we need to know how many women would like to attend. All personal data collected will solely be used to analyze the questionnaire and will be deleted afterward. This email box is required since we want to avoid duplicates. If you permit us, we may reach out to you for further communication. (see next question).
When exploring race conditions in async/await code, I would like to suggest a tool that's been helping me:
Before and after every `await`, and at the beginning of every Task, add a Task.sleep (I use 100ms).
This will ensure that suspension points are long enough that rare things can happen more often.
You're just expanding the suspension points here, not adding new ones. Adding new suspension points would change the semantics of your code.
Don't use Thread.sleep here. That's very different.