Josh's Swift Journey

Well, this has been the worst effort for a long, long time! An entire month! There's no point fretting about it - that will not achieve anything. I've felt a renewed sense of wanting to achieve with coding. At this point, it makes sense to switch to a new Swift 5 course, as the language has been updated. It will also give me a chance to consolidate and ensure my understanding of the basics is solid. Then I will resume with Angela's course! So not a cop out. OK, let's get stuck in! Start Time - 14:00 Just looking at Nick's course, there are 6 hours of content here. Perfect for the next few entries - possibly just even the next couple of days' worth. A lot will be the basics, but that's fine. Intro/Installing Xcode - skipping through all these! Don't need the Linux/Windows ones either. Swift Basics This is going from absolute beginner, so rather than totally skipping through and onto Intermediate, I'm going to just do a general skim over. S...

I don't know how many parts I will need for explaining what I know about Swift - this may be the last one! Another note - I'm writing this without ANY reference to Swift documentation/information - it is a pure test to see what I know! In the previous entry, I described how I went about learning Swift, with the timeframe that included the learning-forgetting-relearning cycle, which I am desperate to break. Last time it was the basics about variables, constants, numbers and strings. This time it gets a little more complicated... Boolean I believe that this comes from the (mathematician?) George Boole, who worked with absolutes: true or false. To apply this to Swift, it could be to find out whether a calculation is true or not. E.g. 7 > 4 would return "true" Using the <, > (along with the = for each) symbols means that you can test to see if a value is greater than another. Conditionals The above directly links to the use of the if/else stateme...