Please add a supplementary video of Actors in the Basics of Swift Course because now functions are not accessing the global variables within their blocks without identifying the Actor so it will be helpful for the beginners to understand what the Actors are and what do they do at this stage respect to the functions usage.
Hi Nick, thanks for those awesome video content! I have been watching your videos for a month now and I like your videos and coding style the most among all other videos on RUclips. Now I have some trouble when I try to practice my own app. I wonder if you are open for giving personal tutoring lessons.
Hey! Thanks for the comment but I’m not doing personal lessons right now bc I want to keep making more videos for everyone. If you need help, someone in our discord will help: discord.gg/vhKKyYTGDb
Hi Nick! Quick question, at 31:20 on line 117 of your code why did you change "value1" and "value2" to "Number1" & "Number2"? ...Why not just type Number1 & Number2 in the first place? Sorry for such a basic question but it confused me so much when small changes like that are made and I don't understand the reasoning behind the change. Thanks in advance!
Hi Nick! Thanks for this amazing content! Indeed ,your teaching style and diction, and explanations are absolutely great and makes it really easy for people like me (with no prior knowledge to programming) to follow the lectures. However, as I am a more visual person and it is always a lot easier for me to remember and grasp concepts more easily when I see it, do you think there is any way of integrating the Xcode and visualising what you are teaching on the screen with the iphone, where you actually see how your code changes the screen of the iphone.? Even if it is at this very beginners level - it would be so much easier to "see" waht we are doing. I follow the lectures and really enjoy them, but at some point if there isn't a visual break to actually see and feel how it is applied to the app I get somehow fatigue from just "pure programming." I am sure there are other people like me and integrating some visualisation would help them as well. I hope all this makes sense to you and it would help you make your amazing lectures even better! Regards, Villy
Hey! This playlist is an intro to the Swift language, which doesn’t involve building a screen (it is just a coding language). The next playlist is the “SwiftUI Bootcamp” which is learning how to build screens and is 100% visual. Every video in that playlist involves seeing your code on screen 🤙
Is there a performance improvement using guard vs. if else? Also, what's a realistic use of calculated variables? Great videos and series! Thanks for doing this!
@marcelolewin performance-wise, both approaches are equally efficient. However, using guard is often preferred when validating input or unwrapping optionals because it avoids deep nesting as is possible with multiple if & if-else conditions, making the code easier to read. This is also commonly called early exit which makes the guard like a gatekeeper. It also improves readability to an extent. For example you may have an if statement that first checks if the user bought a ticket for a movie, then check if the movie plays at a given theater, then check if the showtime is nearing etc etc which would have nested if's within if's. With guard you could have each check separately such as guard userHasTicket, then check guard moviePlaysAtTheater, then check guard showTimeIsNotOver etc.. It'll make more sense if you write these down to see the benefit. Coming to calculated or computed properties, as Nick said you could use them to provide derived data. For example, if you had a Struct or Class for a Rectangle that took width & height parameters, you could have a computed property that calculated the area of the rectangle and do something with it. These are handy as they will always use the latest state or value of width & height. They are also useful when you aren't returning multiple values as a function would or throwing errors for example or executing complex logic. So basically when the property is a function of the state. Do note that when using autocomplete for example, it may seem that width, height & area (as a computed property) are variables in equal sense when in fact, area depends on width & height. I use computed properties when they are just that i.e. properties doing simple things (like with area); and use functions for more complex & intensive logic execution. Hope this helps!
I covered escaping closures here: ruclips.net/video/7gg8iBH2fg4/видео.htmlsi=ySMPW4QBbHENDGFR But if you’re following these playlists in order, you don’t need to know that yet
Nick, because we are making new playgrounds for each lesson within the same file, how do you have Xcode only run the code we wrote in the current playground? Xcode is building the entire project when I run it, even when only running by clicking the blue arrow below the code, but its still pulling in code from every file and module and displaying the previous lesson print statements in every subsequent lesson... thanks!
so, inside my function my variables that I created before my function are not auto-populating like yours are in your video. Do you know why this might be? It makes me go a little slower, and I don't want this to be a bad habit for the rest of my coding career.
I’m not sure what you’re doing different but I’m sure the behavior of functions hasn’t changed haha if you want to share your code someone can help you in our discord: discord.gg/uaRRJeGbFc
I have a video on Generics but it’s not covered in this playlist because it’s a much more advanced topic that beginners don’t need to know yet. You can watch it here: ruclips.net/video/rx3uRICZr5I/видео.html
Please add a supplementary video of Actors in the Basics of Swift Course because now functions are not accessing the global variables within their blocks without identifying the Actor so it will be helpful for the beginners to understand what the Actors are and what do they do at this stage respect to the functions usage.
amazing content, crazy this is free
Thank you Nick, you are the best :) SwiftBasics --> Basic Types --> Variables --> Operators --> f(x)... I am super excited for Optionals.
I love your teaching style
Your video has ability to let me feel exciting to forget to sleep.
You got this! 🚀🚀🚀
Great content. Finally I'm understanding some concepts that was so hard for me!
Very helpful! thanks for the excellent free classes!🙂
@19:32. Doesn't swift infer from the parameter name that the return value type should be of type bool instead of void?
I was thinking the same thing
We’re back
Again
Welcome back
Hi Nick, thanks for those awesome video content! I have been watching your videos for a month now and I like your videos and coding style the most among all other videos on RUclips. Now I have some trouble when I try to practice my own app. I wonder if you are open for giving personal tutoring lessons.
Hey! Thanks for the comment but I’m not doing personal lessons right now bc I want to keep making more videos for everyone. If you need help, someone in our discord will help: discord.gg/vhKKyYTGDb
you kinda sound like Mordacai from the regular show lmao, appreciate your videos so much
Hi Nick! Quick question, at 31:20 on line 117 of your code why did you change "value1" and "value2" to "Number1" & "Number2"? ...Why not just type Number1 & Number2 in the first place? Sorry for such a basic question but it confused me so much when small changes like that are made and I don't understand the reasoning behind the change. Thanks in advance!
Yeah it's definitely confusing. I think Nick is demonstrating "named parameters" . They're like labels for parameters to make code easier to read
Great video. Thank you
Hi Nick! Thanks for this amazing content! Indeed ,your teaching style and diction, and explanations are absolutely great and makes it really easy for people like me (with no prior knowledge to programming) to follow the lectures.
However, as I am a more visual person and it is always a lot easier for me to remember and grasp concepts more easily when I see it, do you think there is any way of integrating the Xcode and visualising what you are teaching on the screen with the iphone, where you actually see how your code changes the screen of the iphone.? Even if it is at this very beginners level - it would be so much easier to "see" waht we are doing.
I follow the lectures and really enjoy them, but at some point if there isn't a visual break to actually see and feel how it is applied to the app I get somehow fatigue from just "pure programming." I am sure there are other people like me and integrating some visualisation would help them as well.
I hope all this makes sense to you and it would help you make your amazing lectures even better!
Regards,
Villy
Hey! This playlist is an intro to the Swift language, which doesn’t involve building a screen (it is just a coding language). The next playlist is the “SwiftUI Bootcamp” which is learning how to build screens and is 100% visual. Every video in that playlist involves seeing your code on screen 🤙
thanks for the video mate..
Is there a performance improvement using guard vs. if else? Also, what's a realistic use of calculated variables? Great videos and series! Thanks for doing this!
@marcelolewin performance-wise, both approaches are equally efficient. However, using guard is often preferred when validating input or unwrapping optionals because it avoids deep nesting as is possible with multiple if & if-else conditions, making the code easier to read. This is also commonly called early exit which makes the guard like a gatekeeper. It also improves readability to an extent.
For example you may have an if statement that first checks if the user bought a ticket for a movie, then check if the movie plays at a given theater, then check if the showtime is nearing etc etc which would have nested if's within if's. With guard you could have each check separately such as guard userHasTicket, then check guard moviePlaysAtTheater, then check guard showTimeIsNotOver etc.. It'll make more sense if you write these down to see the benefit.
Coming to calculated or computed properties, as Nick said you could use them to provide derived data. For example, if you had a Struct or Class for a Rectangle that took width & height parameters, you could have a computed property that calculated the area of the rectangle and do something with it. These are handy as they will always use the latest state or value of width & height. They are also useful when you aren't returning multiple values as a function would or throwing errors for example or executing complex logic. So basically when the property is a function of the state. Do note that when using autocomplete for example, it may seem that width, height & area (as a computed property) are variables in equal sense when in fact, area depends on width & height. I use computed properties when they are just that i.e. properties doing simple things (like with area); and use functions for more complex & intensive logic execution. Hope this helps!
Thanks for the amazing videos, are you going to do a video on closuers
I covered escaping closures here: ruclips.net/video/7gg8iBH2fg4/видео.htmlsi=ySMPW4QBbHENDGFR
But if you’re following these playlists in order, you don’t need to know that yet
Please use AIDente for the sake of your laptops battery, keep it at 80% limit or perhaps 70% when its just sitting on your desk
Nick, because we are making new playgrounds for each lesson within the same file, how do you have Xcode only run the code we wrote in the current playground? Xcode is building the entire project when I run it, even when only running by clicking the blue arrow below the code, but its still pulling in code from every file and module and displaying the previous lesson print statements in every subsequent lesson... thanks!
You can click the trash icon on the bottom right of the screen
Hold the option button thing does not work on my computer.
how do you get the info when you hi-light/hold mouse over the word?
Is it aloud to access the function before declaring in swift ?
so, inside my function my variables that I created before my function are not auto-populating like yours are in your video. Do you know why this might be? It makes me go a little slower, and I don't want this to be a bad habit for the rest of my coding career.
I’m not sure what you’re doing different but I’m sure the behavior of functions hasn’t changed haha if you want to share your code someone can help you in our discord: discord.gg/uaRRJeGbFc
where can i donate
In calculated variables, why you didn't use Double? I thought you would use Double for math.
Yea double is good if you need decimals in the calculation. Sometimes for simple math, you can use Int
Why do you keep calling the function body: "closure"? Isn't closure a different type of statement?
when i am pressing option button and clicking on name its showing : No Quick Help
Closing Xcode and reopening fixed it for me
When will you make a video about Generics?
I have a video on Generics but it’s not covered in this playlist because it’s a much more advanced topic that beginners don’t need to know yet. You can watch it here: ruclips.net/video/rx3uRICZr5I/видео.html
@@SwiftfulThinking thanks 🙏
I knew the frowning upon and shaming global variables with pop-up. Shaking my head
how appropriate to call a function before create it
awesome
🎉🎉🎉
👌🏽👌🏽👌🏽