Today’s tutorial is about persistence. I think that’s a good one as I make my way through these various tutorials.

Section 1: Add Codable

Purpose: Make the models that we’ve been working on conform to a protocal that will allow it to be saved as JSON.

It’s interesting to me that they have file names with special characters like “+” in them for the tutorial.

It reminds me of when I first got into computers and how the teachers would tell us that it’s a big no-no.

Section 2: Create Data Model Purpose: To show how data can be stored. It touches on the Combine framework.

At this point, I think the tutorial should define the difference between the data in the different scrum objects/classes and the one for persistence. Or maybe they have and I jumped over it.

Documentation seems very sparse.

I like the way the documentation widgets work for the most part, but I would love to get more information from it.

Clicking on the link “Open in Developer Documentation”, doesn’t really give me hope I’m going to get an answer for any question I might have.

In the above picture, how is someone new to this going to know that the declaration has a link ObservableObject protocol?

Some of the notes feel like they should be closer together.

It feels like certain notes should be close to the steps that they highlight.

Keyboard shortcuts are amazing.

I love ^I for re-indenting my code.

I’m going to stop here and pick this up tomorrow.

Getting back into the swing of things and I’m continuing with the tutorial. Today is about State Management.

In this tutorial, you’ll add two new features to Scrumdinger. First, you’ll add a view to create new daily scrum meetings. Then you’ll update the meeting timer to keep track of past meetings.

Section 1: Use EditView

Today, I felt a little more confident in myself and my tools. I went with the option of defining the content of views and closures in the way that Xcode wanted.

For example, Xcode places the following as a method signature.

The tutorial defines the sheet as the following.

Semantically, they are both the same but I feel that the one in Xcode definition is less ambiguous. I’m still learning and want to be able to read this code later.

I pat myself on the back for being able to understand both options.

That being said, I don’t know if I like the idea of creating multiple views in a single line to make a composition.

I can see why you would do it since you aren’t using the buttons anywhere else in the application but I hope that I’ll continue to be able to learn and think in the swift way¹.

I don’t like long lines for code.

Much better.

Section 2: Add Scrum History

Purpose: Re-enforce the ideas of state.

I’m immediately impressed with the object diagram.

The second section really made things click for me and having the alt-click shortcut allows me to look up the documentation quickly.

In review

I liked today’s progress. I really feel that a lot of stuff clicked for me. This isn’t my first tutorial, and I’ve attempted to learn multiple times in the last couple of years. Today was jun and I’m looking forward to tomorrow.