Newsletter
Character
July 7, 2020
Who you are.
Josh and Eliza
Over the weekend I listened to an interview with Josh Shaffer and Eliza Block. For years the duo teamed up to give crowd favorite presentations at WWDC. They are brilliant, personable, and understand how to tell an effective story with the right amount of code content.
Josh is now in charge of Swift Frameworks at Apple and is responsible for SwiftUI. Eliza is now working on Previews in Xcode. If you're coding for Apple platforms, this interview is chock full of information. Josh gives details about SwiftUI and also talks about some of the thought process behind design decisions. Eliza talks about some of what is involved to create a responsive round-tripping view that most of us use without ever considering the complexity of what's involved.
But that's not what I want to talk about today.
Eliza
I have a semi-personal story about Eliza.
I was working as a contractor on a project at Apple about five or six years ago. It was an app that would only be used internally. My team was amazing - I learned so much from them and am sad that WWDC was cancelled this year as I look forward to getting together with some of them whenever I'm out there.
Anyway, we were stuck on something and one member of my team suggested that we ask Eliza. I don't remember why, but he thought she'd know the answer.
The next morning he popped in my office with code that he'd gotten in reply.
Not only had Eliza answered our question but she'd provided a clear code sample demonstrating the right way to do it.
Identifying what drives you
In the podcast episode, Eliza said that before she joined Apple she'd studied Philosophy and Linguistics and programming on the side.
We've talked here before about how you sometimes learn what you're interested in by seeing what you spend time on.
During her last year of working on her dissertation in grad school she was drawn to coding for the iPhone. It was the very early days. Before the iPad. Before iOS - it was the early iPhone OS. She was souring on academia and instead was spending more and more time working on an app for the iPhone.
This is not uncommon. I wrote my first C programs at the end of my dissertation. Some of it was to do work with elliptic curves that I needed, but a lot of it was not at all related. There are a bunch of books written on the topic that remind PhD students that the thesis is not going to be the last thing you ever produce. Your job, they advise, is to finish and get out. Go into the world and continue producing work.
But it's also a time where people reappraise whether that's the work they want to do. Depending on your field, finding a job can be really difficult. There are fewer and fewer positions and of those even fewer pay well (many are part-time, no-benefits, limited-pay jobs). Scientists end up with multiple post-docs before they discover in their thirties that there's just no job for them now.
So Eliza decided academia wasn't for her and that programming was really what she loved.
And then...
Eliza tells this next part quickly and understates it. She wrote an app that "went in the app store and it was lucky for me, because people at Apple liked it and so they asked me to come apply for a job."
I love this story and wanted to share it because we've heard so many stories about companies that require a CS degree and a white board test. My time contracting at Apple was better because of the mix of folks from different backgrounds that I worked with and encountered even at a distance.
There is something about finding out the role you are to play in your own life's story and then getting an invitation to star in that role.
Making plans
I've decided to share my plans for the rest of this year. It makes me a little nervous to commit in public like this but I've done so in this blog post that draws from the great Penn and Teller take on the Cups and Balls trick. One of the promises of the post is that as I rewrite my books and prepare my classes, I will blog on the content and share things online.
This includes mistakes. My first such post is a beginners error that I made when working with a Nav view. I should have known better. I do know better. I made the mistake anyway. I'm sharing this in the Nav Mistake post to remind us all that we all make mistakes and it's ok. While I was there, I created categories for my posts on Editor's Cut and included a directory by topic of the posts.
Link to the Podcast episode from July 7, 2023.
It looks awful
I know.
Those don't even look like real people.
So far for me the hardest part of drawing the comic is the time it takes to distill the topic. This is not an easy process. The pictures are awful - but I hope the ideas are clear.
In my opinion, the best way to understand the topic would be for you to draw your own pictures.
Try it. I'm having a blast with this.
Staying safe
A lot of gyms are opening back up. Here in the US we still have a disturbing number of Covid cases. Here's an article about whether or not it's safe to go back to your gym.
Maggie's link
I'm assuming that this week's link from Maggie is a hint of something she'd like me to use for dinner sometime soon. It's Chef Mike's Awesome Potato Skins.
I've been watching Kenji's cooking videos. Last night I watched this one on Spanish Tortilla's.
Other people's stuff
Chris Eidhof posted an image that he's been working on to understand and explain the various data type Property Wrappers in SwiftUI.
The image will be included in his and Florian's rewrite of Thinking in SwiftUI.
One person replied to Chris with their suggestion for what he'd forgotten. Someone else replied arguing that Chris should have reversed the decision axis.
Chris spent a lot of time coming up with a diagram this simple. Once it's this simple, people pipe up with the "why don't you just"s. Chris is too polite to say, "why don't you just draw it yourself".
As I said before, it really is a blast and you learn a lot.
It will also remind you that simple isn't easy.