Josh's Swift Journey

sSo begins the recommencement of Treehouse! Yes, it's been a long time and I was certainly put off it before. This time, though, I have got a good grounding from such a range of courses, including practical projects along the way. So I'm going to do something else that's new - supplement my learning with other stuff! In each entry, I will include further reading and - where applicable - code practice! Rather than race through to get it done quickly, I'm changing my approach. Let's say that the focus is on optionals, then I will go through the content, then look at other bits on optionals - online, in Swift book etc. etc., then include some practice on playground... you get the drill! So, I'm excited for this and, as I've said, this will be more about going deeper and getting to grips with the content each time rather than racing through. OK, let's do this!! Start Time - 09:30 Rather than I just continue, I'm going back to the start of this sect...

One day's break in between is fine. I plan to do just half an hour here - seems reasonable! So we're continuing with API design. From what I remember, this was basically about the rules of making code readable and logical. OK here we go! Start time - 19:35 Naming Methods Pasan starts off by recapping a method - this one is index. What he's describing is very dull. I can't lie! Right some key rules - 1. Omit needless words 2. Avoid ambiguity So a point here is whether it is clear at the use site - where the function is used. Really - I've lost so much interest with this. If the next video does not pick up, then I'm leaving this stuff for now and moving on from Treehouse! Fluent Usage So grammatically correct English is important. Fair enough. E.g. 'insert a at 1' is grammatically correct. A lot of it is prepositional - at, in etc. Well, this has been a waste of time. It is so dry and without interesting examples that I'm going ...