Mandaris

We continue with structs today and I think I’m getting it for the most part. The issues that I run into are ones where I don’t pay attention to property names.

This session wasn’t as long as others, but I feel that I needed that after going through closures.

Today, is an exploration of structs. A lot of Swift seems to be built using structs. I wasn’t 100% awake when I was doing the computed properties section.

I tried mixing property observers and computed properties, and that does not seem to work.

I understand it as the value cannot be both observed and computed at the same time.

I still enjoy the fact that the questions keep us on our toes. This means that basic things can still trip you up if you attempt to rush through them.

I do wish that I had 100 out of a 100, but I want to be honest with myself.

Update: I used the wrong screenshot and had to remove the second image.

Closures part 2!

Paul Hudson says that this is where closures start to look a little bit like line noise and it can be hard to follow functions that use closures as parameters. Needless to say, I’m happy that I started this section early in the day.

Closures!!!

It took me a while to understand¹ but this run through has really cemented how I look at them and just working with them in different tutorials.

For example, I had no idea what the section on “Closures as parameters” actually was saying. Now I can read the code and understand it.

I’m really excited and proud of myself! I did get a little too excited when I start the trailing closure syntax, but I can see where I went wrong versus just scratching my head about it.

Today, I decided that I’d use CodeRunner to look at the examples found in the tutorials. It’s part of SetApp.

It’s simple and I can just run the code that I want without the overhead. Plus it catches errors that are in code, which helps when I’m going through tests and logic.

At this point, you can really, really tell that the lessons are building on top of each other and you can’t rush through them.

I don’t like making mistakes. When I do, it drives the lesson home and keeps me awake and cautious of what I’m doing.

As an added bonus, I’m learning that mistakes shouldn’t effect my ego so much.

Also, I can definitely get along with someone who writes this kind of code.

enum PizzaErrors: Error {
	case hasPineapple
}