Make, Show, Learn Issue 2

From The DC Comics Guide to Digitally Drawing Comics:

But I encourage you to zoom out (by going to View > Fit on Screen) every once in a while just to make sure you aren’t getting stress out over an area no one will notice. — Freddie Williams II

That’s my preview of issue 17: Life advice from drawing books. In the meantime, welcome to issue 2!

img_580d37a284366

Sustainability

I wrote 100 posts in 100 days (and will probably mention it 1000 times in the next 100 days). Quality varied way too much but it was good seeing the amount of content at the end. Writing daily adds up.

I made some sacrifices to make it happen. (If I was a better writer, I’d have a lighter word than sacrifice.) I said no to some social events. I skipped workouts.

img_580d47ed9c6d0

Was it worth it? Well…

Yes. To learn from. I followed a routine and got a tiny taste of what people mean when they say they can’t wait around for inspiration to write.

And no. Those things I sacrificed are important. Long term, my relationships and my body are more important than this hobby.

Nutrition and fitness advice often revolves around making it a lifestyle change. Otherwise you’ll just try yo-yo diet after yo-yo diet. It needs to be sustainable.

However, it’s useful to go to one extreme for a short period of time, like eating completely clean temporarily. You can then re-introduce foods and see if the costs are worth it. You can figure out the 80/20 and adapt the most effective aspects long-term.

Oh yeah, this is about writing. I want this creative project to be sustainable. I don’t want to lose sleep and take small steps in the wrong direction. Those add up over time just like writing one page a day adds up.

One step at a time toward 40 issues

So how can I make things sustainable? High level, my goal is 40 episodes and issues instead of 52. That gives me some breathing room. One week off each month.

I won’t get to 52 in a year. Not without sacrificing things that are more important to me in the long run.

If I was new to a site and clicked “archive” and saw 40 posts or 52 posts, they’re basically the same. It’s like if an ebook is $4 or $5.

What it does affect is consistency. As long as I don’t take two or three weeks off in a row, the consistency will be there. It’s much better than pushing to do 13 weeks in a row, then quitting entirely because I’m burned out.

I can make up for it with consistency in other channels. Those are hypothetical right now. It’ll probably be instagram. On weeks off, I can put the growth hacker hat on. “I won’t be here this week but follow me on Instagram!” That was supposed to be a joke but I can really see that happening.

5 sections a week. Well, maybe

Zooming in a bit, what can I finish in a week? A lot is learning how long things take. Last week’s issue was too long. Both in the time it took to make and just the length of the post.

I’m kissing the weekly dozen goodbye. This week I’m trying 5 sections.

When learning something new, it can be useful to apply concepts from fields you’re more familiar with. I’m learning to draw, so maybe there’s a good way to apply product design or software development concepts to all this.

Design sprints come to mind. Each issue of this has some design elements. Drawing is already a core part of design sprints. In sprints, different kinds of sketches are usually timed. Actually, nearly everything in the sprint is timed.

From Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days:

We use Time Timers in our sprints to mark small chunks of time, anywhere from three minutes to one hour. These tiny deadlines give everyone an added sense of focus and urgency.

I’ll start timing things as I work on my process on each of these issues. If I can get an accurate time of things then I can set a timer, do that thing, and move on.

Avoiding the shallows

I’ve mentioned a few times that I want to try doing an entire issue—drawings and writing both—focused on single themes or topics. If it’s going to be about a book, Cal Newport’s Deep Work is at the top of the list.

The illustration above is a colored-in version of a sketch I found from earlier this year. I had an idea for a former version of this blog where each post would be a long-form book notes post.

It became another unfinished project.

The shark illustration is supposed to represent the idea of getting lost in the shallows. Deep work involves long stretches of focused time. The shallows are the opposite. Sometimes they involve work—glancing at email, bouncing around between 3 somewhat related tasks and making slow progress on all of them. Usually it’s not work related at all. Social media, texting friends, cycling through news sites.

Eventually, I’d like to sit down and finish that book notes post, because Deep Work has been a major influence for me this year.

Keys to Drawing

Deep work has a close cousin: deliberate practice. They both require the same sort of focus. I’m thinking a lot about how I can apply deliberate practice in learning to draw.

Anders Ericsson knows a lot about deliberate practice and shares a lot of the knowledge in Peak: Secrets from the New Science of Expertise:

If you’re in a field where deliberate practice is an option, you should take that option. If not, apply the principles of deliberate practice as much as possible. In practice this often boils down to purposeful practice with a few extra steps: first, identify the expert performers, then figure out what they do that makes them so good, then come up with training techniques that allow you to do it, too.

I don’t have a mentor to watch me draw right now. Tough luck, right? Maybe not.

This is where I might be able to really leverage technology. Recording and sharing my process is possible. You can watch me practice. I can hypothetically get feedback on that practice. First I’ll need readers and I’ll need to make interesting things.

I’ll work toward building an audience of people more skilled than I am that can give frequent feedback. That would be amazing.

In the meantime, I’ll find guidance from experts in the form of books. I’m currently working through Keys to Drawing by Bert Dodson. He explains different drawing techniques and provides exercises and suggestions for how much time to spend on them.

This week’s video portion is a look at an exercise of my own.

It’s inspired by something Simon Rich does to generate ideas:

When I was writing Free Range Chickens, I had just discovered Wikipedia and one of the ways I came up with ideas was to just keep refreshing, and keep clicking the random article until a premise occurred to me.

So I just set a timer to do three 5-minute intervals. At the start of each interval, I jam Wikipedia’s random button until a decent image showed up. Then I drew the subject with the remaining time.

Random images keep me from drawing the 17th plastic coffee cup of the week. It was a lot of fun. And it takes a set amount of time. This might become the first recurring feature of every issue.

DC Comics

Last week, I wrote about learning to create narrated images for each week’s video. Somehow comics never came to mind. But they moved to the front burner this week. When I drew as a kid, a lot of it was just trying to draw either comic characters or video game characters.

I bought a bunch of DC Comics books about making comics:

Having skimmed through these, here’s the main takeaway: I still need to learn to draw first. I’ll keep working through traditional drawing books.

img_580d475dad80e

However, comics provide a style I’m interested in learning. Comics shine in a particular way when it comes to learning.

Comic artists show their work. Many artists do signings and drawings at conventions and things. A lot of times, they’re happy to let people record over-the-shoulder videos showing their process. These are available on YouTube.

Artists also often share their own process videos on social media accounts. There just seems to be an endless amount of videos of experts at work. A lot of their thoughts end up visible on the page. You can see things progress from very rough lines to final prints. It’s a resource that doesn’t exist for every craft.

You could time-lapse a writer writing and typing, but it’s not the same. You’d need to see drafts with revision notes to get any real insight. You might be able to find some of this for authors you like. But they don’t sit at conventions writing one-page stories for people to watch and learn from.

I knew a little bit when I started this project. Two weeks later, I have a better idea of how little I know. Hopefully 50 weeks later, this will provide a deep look at my learning process.

In the meantime, I’ll be looking for another plastic cup to sketch. This time with cross-hatching!

Make, Show, Learn Issue 1

Creativity weekly

image_0

Blogs began dying somewhere around 2008. Personal blogs are on the endangered list between the rhino and the saola. Writing about what you’re up to used to be enough. Doing that with photos was a step ahead. There weren’t billions of things being shared every day, because it wasn’t easy to do. You’d need a digital camera then some know-how for getting a website up. Content management systems made it easier, but one-click installations weren’t the norm.

There were things with many names—365 Project, Project 365— but it was posting one thing each day for a year. It was usually a photography project but some people did other art. Now these things are just hashtags. Back then they were presented as a challenge. I failed multiple times.

“I’m starting my 365 challenge. — Me in high school

“Nevermind.” — Me, on day 17.

I would then play 7 hours of Counter-Strike

Finishing one of these annual photo projects was a big accomplishment.

Sharing a video every day? Before YouTube? You could probably win a Webby. Or at least a custom ribbon to slap on your page.

Now people do this in their sleep. Even kids. Multiple videos and photos. Every single day of the year. It’s called Snapchat.

There are millions of WordPress blogs with people sharing things they’ve made. I’m adding another one to the mix.

On not being just another WordPress site

Blogs are still the best way to broadcast longer-form text and images. (I’m counting Medium as a form of blogging.) There are tons of blogs, though, so it’s important to niche down. That also helps in staying focused.

I’ll write about things that interest me. The through-line will be that I’m learning to draw. The bigger picture is that I’m learning to tell stories visually. I’ve always wanted to be good at combining text and visuals.

Each week, I’ll make one video and a post to accompany it.

image_1

In learning to draw, I did some searching on recommendations for learning to draw digitally. Almost all of them said to start with paper and pencil. You’ll learn bad habits. You’ll use the tool as a crutch.

It reminded me of something I read in Smartcuts: The Breakthrough Power of Lateral Thinking, by Shane Snow. Children in Finland use calculators early. They end up excelling in math:

The overwhelming majority of academic research about calculators indicates that leveraging such tools improves conceptual understanding. By learning the tool (calculator) first, we actually master the discipline (math) faster.

This is my long-winded and tenuous defense of buying an iPad and Apple Pencil anyway. I’m going to learn to tell stories visually and I’ll take an entirely digital route.

Hopefully that’s a deep enough niche to find readers.

Inspiration

image_2

My larger goal is learning to tell stories with visuals and text. A lot of the inspiration for the format I have in mind comes from Extra Credits — a video series about game design. Mostly conceptual rather than actual implementation details. Most videos are narrated stills with some animation.

The thing that really got me was their episode on minimal viable products (MVP). I’m familiar with MVPs for startups and their episode talks about MVPs for video games. An MVP is likely more basic than it might seem. Mario would just be a block running and jumping over pits. No koopas, no fire flowers, nothing.

I got to thinking about what the MVP would look like for this project. I think one minute of narrated images will be the MVP. If I eventually want to make five minute videos, it’d be five interesting minutes. Making one interesting minute is a good start.

I admire that Malcolm Gladwell can take raw material on a subject and make it interesting for a chapter. Gladwell said he admires Michael Lewis for being able take make something engaging for an entire book.

I’m striving to make something interesting for one minute. So I’ll start broad with the topics. When I improve, I’ll be able to take that full minute on one topic. Then multiple minutes.

One great minute is the goal. One minute of any quality at all is the first baby step I’ll take.

On the Pro Blogger podcast, Darren Rowse recently talked about taking imperfect action to build momentum. This first post and video won’t be perfect, but it’ll be one step forward to build momentum.

bitmap

This week, I was thinking about how to come up with the video. I’m going to start with recording a Keynote presentation and narrating it.

To make the presentation, first I’ll start with the post. The way i see it, the presentation is a condensed version of a post with just the best parts. The longer version comes first.

I’ll aim to draw 50 things each week. Some will be more complex than others. Some might be a few words.

From those 50 slides I’ll pick 12 to share and write about. That’s what I did for this post. Then, aiming for a one-minute video, I’ll talk about each section for 5 seconds.

That’s the MVP. And I’m already learning from it. 12 might be too many each week. I estimate that I had more time this week than I’ll usually have. Eight might work better. And that’s about 8 seconds per section in the video.

Make things, show people, learn more thingsimage_3

Other title ideas for this weekly video and blog post: Creativity weekly, Making things weekly.

When thinking of a title, I thought “What do I want this blog to be about?” If I’m dedicated and have 40 posts a year from now, what would I want them to represent collectively?

Learning. I’m learning how to tell stories. It’d be great if I could show my progress as I learn to draw. And I can try pulling stories from links and books that I find interesting.

I had the title already. My Twitter account used to be @makeshowlearn. I’m gonna switch it back. Make, Show, Learn was based on a slide from a WWDC presentation about prototyping with Keynote.

The slide described steps for testing prototypes: make a prototype, show the prototype to people, and learn from their use of the prototype. Repeat.

I used to write about design and the Twitter handle reminded me of steps to follow to grow as a designer. Make things, show what I made to people online, and learn from that process. Repeat.

It worked. Some people liked what I was showing. (Some people hated it, of course.) A few people commented or emailed saying I helped them learn. That was very rewarding.

Then I stopped.

Now I’m starting again, but with storytelling as the focus.

Getting my reps in: 100 posts, 100 days

image_4

Earlier this year, I wrote 100 posts in 100 days. I learned to enjoy the process and I appreciate the collective end result. However, a lot of the individual posts are just so rough. I’m not proud of every single post. I needed to edit more.

I do like some of them though. Here are a few of my favorite posts:

Japan Trip 05 of 10: Ramen — I went to Japan earlier this year with my girlfriend. A lot of my favorite posts are about that trip. In this one, I go over a few of the ramen places we ate at.

Japan Trip 06 of 10: Five more thoughts — Some thoughts on the Fushimi Inari temple, which really stood out among all the temples we visited.

Japan Trip 08 of 10: Rico! Ospreay! — I read that in lieu of mastering words and sentences to make the writing interesting, you can do something interesting and then write about it. We went to a New Japan Pro Wrestling show and it happened to have one the most insane matches from this year.

Book Notes: Save the Cat! — I wrote a lot of book notes posts. Some were better than others. I want to continue doing these.

Book Notes: Smartcuts — Another book notes post. David Heinemeier Hansson is an example of someone that used a Smartcut to success. He created Rails when Basecamp was still called 37Signals. It’s not in the book, but I enjoyed learning that Ernest Kim and Kicksology had roots in 37 Signals.

I’ll continue linking to other posts in future issues. Some of the content is worth checking out, so I wouldn’t want it to go completely unseen.

Almost drowning

image_5

As mentioned, I have a bunch of posts that I’d like to link back to. Some of my drawings this week are about existing posts. This solves two things: 1.) it gives me concrete ideas to draw and 2.) it allows me to link back to posts. A couple weeks ago, I wrote about almost drowning. It’s a book note post about Steven Pressfield’s latest book Nobody Wants to Read Your Sh*t. It’s is about the importance of storytelling and served as motivation to become a better storyteller.

Meet Ube

artboard-copy-5
I was sketching ideas for the front page of this blog then I thought this part looked like a mouth. So I made it the mouth of a monster. (It also looks sort of like a building.)

I showed it to my girlfriend and she said it looks like ube. We had ube ice cream recently and it was actually labeled ube instead of taro. I wonder if there’s actually a difference. I can look this up.

page-1

They’re different. And I’m delighted that ube is a tuber.

This monster’s name is now Ube.

A drawing of a tree

image_6

Each of the posts will have drawings. I can talk about the process. I’m pretty new to this. Right now I’m doing something like this:

  • Sketch with a pencil tool
  • Use one of the ink tools to go over the pencil
  • Add a layer and set its blending mode to Multiply. Use a paint tool to color things.

I mentioned bad habits earlier. Some tutorials I’ve watched mentioned learning bad habits. Artists reviewing the 9.7″ iPad have side remarks saying you might pick up bad habits learning to draw on it. You might get used to zooming too much. You might lean on being able to undo. You won’t be able to draw with pencil and paper.

Drawing with pencil and paper isn’t a goal of mine right now. The tradeoff of these potential bad habits is that I’ll be able to build a good habit: showing my work. I want to make digital things because they’re easier to share.

I’m also having more fun learning to draw digitally. It’s likely that other people are in the same boat. They want to draw using their tablets, because it’s fun. Maybe I can provide value to those people.

Ben Orenstein, a developer at thoughtbot, wrote about landing a Rails job and the value of blogging daily:

Write about what you’ve learned so far. Don’t make the excuse that you’re just a beginner. Imagine someone who is two months behind you and write for them. An active blog shows passion, demonstrates skill, and helps you make more Ruby friends.

I can at least help someone two months behind where I’m at. Right now I’m at 1 week so I’d be helping someone at like –7 weeks. It doesn’t quite apply. Eventually I’ll be able to share resources and learnings helpful for someone just getting started.

image_7

Apple cider

I mentioned writing 100 posts in 100 days. On Fridays, I’d share links that I found interesting from the week. The idea was inspired by/stolen from Tim Ferriss. I’d like to continue sharing links. Part of this weekly dozen will be link shares. It might even completely be that in the future.

In Ferriss’s most recent 5-Bullet Friday, he links to a video of his evening routine. The first part is really followable (NOTE: No red squiggly came under this word. ) — tea, apple cider vinegar, and honey. It’s supposed to knock you out for the entire night.

Then he goes into his private soaking tub. Some people say the cider and honey combo creates more vivid dreams. Dreams like owning a home with a private soaking tub.

Closing with honey and some links about drawing with an iPad

image-5

Here’s a honey bear that looks more like a honey squirrel. Something that occurred to me here is that I used a white paint tool. I don’t know how this would work if I was working with markers. I mean I’m guessing there’s probably a white marker so that’s probably the answer.

Scratch what I said a couple sections ago. I’ve already got resources that were helpful in my first week of drawing digitally.

Procreate 3 tutorial by James Julier — This was a great overview of a lot of Procreate features and how he uses them. It’s great to be able to see how experts work, knowing you have access to the same tools they’re using.

How to Draw Using Procreate by Will Terry — Another Procreate overview and he draws with his finger.

Spiderman speed painting by Danny Glasglow — I will never be this good. (“Especially with that attitude!” I know.)

Drawing on the iPad Pro by Scott Johnson — This was fun and, again, it’s good to see an expert work. I’d like to be able to draw this well but I know I’m thousands of reps away.

iPad Pro 9.7“ vs 12.9” by NihongoGamer — The previous four links were all centered around using Procreate for drawing and painting. In this video, I saw that he was using the Notes app for sketching. He explains that he likes how the pencil feels in it. I liked that he was just creating new notes with a two finger swipe.

I started trying that and I really like it. Constraints can be good. Not being able to tweak paper size and all the different brushes is good in many ways. I can just get right to drawing.

I’ll continue using both Procreate and Notes and I’ll learn what works best for me for different situations.

Thanks for checking this out. Now I gotta go make that video. Give me a minute and I’ll give you a minute.

I’ve got an idea

I’ve been posting something every day from my iPad. Sometimes it’s a few drawings. Sometimes it’s a few photos. Sometimes it’s just a single drawing. From writing 100 posts in 100 days, one big takeaway is that posting just to post sometimes wasn’t worth it. Putting junk out into the world might not be productive.

80 posts in 100 days might have resulted in better posts. Or maybe it wouldn’t. Maybe I would have taken it too easy, skipped a few too many days in a row, then just quit.

After the 100 posts project, I decided that working on something every day was valuable. Flexing your creative muscle is really rewarding. The value of publishing daily was the goal itself. It was a hard goal. I knew if I reached it. I didn’t build a readership so there wasn’t value in that sense. Even if I shared it more widely, the content likely isn’t good enough for it to build a readership. Still, it was good to built that habit of finishing.


I want to continue being creative daily. Sharing a single sketch is likely better through social media than a standalone post on this blog. So I’ve been thinking (as in, this is an idea from today) about how to present collections of sketches and other things I’ve made through the week.

I’ll make a video. It’ll mostly consist of sketches done through the week. I’ll share things I learned that week through books or other resources. It will be part of a weekly post. This weekly post will be a hodgepodge of things. That video. A post explaining some of the process of making the video. Links from the week. Book notes from the week. Meals I ate. Who knows.

That’s what I think it will be. One post each week. I’ll work on it in some capacity every day. The glorious return of my non-glorious personal blog. Here’s a preview.

So, yes, I started it. I’m still keeping with this month’s theme of using my iPad for creating content. I was inspired by watching an episode of Extra Credits on MVPs. I was familiar with it in startup terms but was happy to see the idea reflected in video games. An MVP is stripped down much further than it might first seem.

The MVP for these new weekly videos and posts will start with slides that I’ll narrate. Right now I’m using Procreate for sketching and Keynote for organizing the sketches. Eventually I’ll record something for it. I’m aiming for 40 slides. That should get me to about a minute. That’s my goal for the week. A one minute video. We’ll see how it goes.

A drawing

Here is a drawing I did of all the different things that my wallet turned into yesterday. I drew these in Notability, which I’m trying out for drafting more visual blog posts. Unfortunately, it doesn’t look like you can just export to PNG so I might need to figure a better system out. Probably with Workflow or something.

Some photos

Some more photos with the iPhone 7 Plus.

A sketch a day #2: and a purchase

From what I’ve read about digital art, a common suggestion is to start by learning to draw with paper and pencil. You can get too caught up with digital tools and fixing mistakes on the fly. And trying to refine things without moving on to a new drawing. You can be less thoughtful and all that.

I bought an iPad Pro today. Here’s my first sketch.


I have more thoughts on this. I thought it’d be good to have a hobby that isn’t programming-related. Which I guess writing is, but writing is also mostly sitting at a keyboard and typing. Which, considering the amount of email exchange that takes place in any knowledge work, is what a lot of the work day looks like.

Now I’ll sketch. Which is what the work day probably looks like in some aspiring designers’ heads.

Oh yeah, so here’s all the things that I got. An iPad Pro 9.7″ 128GB silver. An Apple Pencil. A Logitech Smart Case. I actually really like the keyboard so far.

“So far” being pretty early days right now, because I haven’t left the Apple Store yet. As a device for creating content, this seems like a pretty good set up for what I want to be doing.


A sketch a day

I did this sketch on my iPhone 7 Plus using Procreate.

More iPhone 7 Plus photos

Went to Dia:Beacon. We also went apple picking. It was a good chance to give the iPhone 7 Plus camera a spin.

20161006-iphone92-10-0-img_0755

20161006-iphone-7-plus-img_0812

20161006-iphone-7-plus-img_0799

20161007-iphone-7-plus-img_0882

20161007-iphone-7-plus-img_0921

20161006-iphone-7-plus-img_0737

 

10-3-2-1-0

I’m focusing on getting healthier this month. I had a lengthier explanation in my previous post.

I’m now forgetting where I got to this link, but it was probably a podcast. (It’s always a podcast.) Craig Ballantyne has a 10-3-2-1-0 formula for getting to bed on time.

10 hours before bed – No more caffeine.
3 hours before bed – No more food or alcohol.
2 hours before bed – No more work.
1 hour before bed – No more screen time (turn off all phones, TVs and computers).
0 – The number of times you will hit the snooze button in the morning.

With the actual goal being to wake up earlier to start the day off right.

Will this work? Let’s see how those hours translate for me. For me, those hours translate to: 2pm no caffeine, 9pm no food no alcohol, 10pm no work, 11pm no screens.

No snoozing! I don’t usually set an alarm. It’s not discipline or an amazing internal clock. I just don’t wake up incredibly early. I’m glad I have that flexibility. Many people don’t.

11pm, no screen time. I enjoy reading books, so that’s a good transition for right before sleeping. And reading something on my Kindle with blue blockers on is pretty close to no screens.

10pm, no work. I’m not usually doing anything on the computer after 10pm. Having a concrete time in mind will help. Especially for the nights that I’m tempted to work on some idea. It’s almost certainly better to sleep and work on it in the morning.

9pm, no food or alcohol. Ah. I drink less often than I used to, so that part won’t be too hard to follow. Food, though. I eat something after 9pm on most nights. Again, having a concrete time in mind will help. In most cases, it’s not anything healthy that I’m eating after 9pm.

2pm, no caffeine: This will be a change but not a huge one. I avoid caffeine after lunch. Well, usually. So I’ll just have to change “Well, usually” to “Period”.

I already wear blue blockers and drink magnesium. Following these guidelines should help even more. Next up, I’ll work on a morning routine to look forward to after a good night’s sleep.

All the books I read: 2016 Q3

Note: I’ll update this with some directives and author names. I’m posting things that need a few changes to push myself to finish posts. Knowing a post is published with a few things to finish will urge me to finish more than having something 80% done in draft state.

Thought it’d be good to follow up on All The Books I’ve Read This Year (written near the end of June 2016). I read 15 books. A few were pretty short, but I’ll go ahead and count them.

Here are the books I finished in July, August, and September 2016.

Flash Boys:
But What if We’re Wrong
Comedy Writing for Late-Night TV
Ego is the Enemy
Sprint
— You can prototype anything.
Food Rules
Originals:
Spark Joy
You are a Writer
The 15-minute Writer

I tried reading more fiction (aka nearly all of Simon Rich’s published books). It really is more pleasant reading fiction at night before bed. Reading things that make you laugh turns out to be great for winding down.

Elliott Allagash:
Last Woman on Earth:
Free Range Chickens:
Ant Farm
Spoiled Brats

Audiobooks

I haven’t listened to audiobooks quite as much. I have a hard time getting as much out of them. I can get through them, but I don’t know if I’m retaining what I listen to. (I also think this is overestimating how much I retain from what I read in books.) One book that stuck out is Grit. I suspect it’s because I was writing book notes each day as I listened. Actually, whether it’s an audiobook or traditional book, writing notes while reading helps get the most value out of reading.

Grit
Bull’s Eye
One More Thing
Daily Rituals
Do you Talk Funny

Nobody Wants to Read Your Sh*t

I never took swimming lessons. My dad loved swimming and would try to take me out to the pool with the arm floaters and then he’d let go and I’d be yelling within a couple seconds.

Nobody wants to read your sh*t. The title can be backed up by opening up my site’s analytics. I enjoyed Steven Pressfield’s other books on writing: The War of Art, Do the Work, and Turning Pro.

They’re sometimes referred to as a trilogy. I’d say this is more like Prometheus than Alien: Resurrection. I think it’s more like, “Ok, you’re doing the work. You’re writing. Now it’s time to get better.”

I sat down at my laptop (again, right in the WordPress editor) to do the work. I knew I had a bunch of highlights from the book, so  I could just grab one and write thoughts on it. Except those highlights and notes seem to be gone after upgrading my phone. (I was highlighting in the Kindle app, but it was a free non-Kindle version of the book. I’m guessing they disappeared when I got an iPhone 7.)

Sometimes I use book excerpts a little heavily and they can be like the arm floaters. Today I’ll write without excerpts from the book.

It’s been a few months since I read it, which is great to gauge what really stuck with me.  I wrote it as a directive in my “Books I Read This Year” recap and it’s the lesson that stuck with me: always tell a story. That’s clear for novels and movie scripts. It applies in other fields, too.

The best ads tell a story in a few words. Even technical posts are more interesting when there’s a clear beginning (what’s the problem), middle (what’s can some technology do), and end (this is how the technology solved the problem).

In 5th grade, I went to the pool with some friends. I wasn’t allowed in the deep end because I hadn’t passed the swim test. Now I’m forgetting how they even knew who passed and who didn’t. I don’t remember them checking before you get in the pool. Maybe you get in trouble for running near the pool but you get in super trouble if you drown and haven’t passed the swim test.

Anyway, it was never great being one of the kids that couldn’t go to the deep end. There weren’t any pre-requisites for the swim test other than being ten years old. One day I got fed up and walked to the gym alone to take the test. First half: swim down the lane once, swim back once. No problem. Under control. To finish it off, I just had to wade for two minutes. I remember rising up as the lifeguard one-armed me to the surface.

Fall seven times, rise up eight, right? Right now I’m going sentence by sentence into the deep end. I’m seeing how far I can go and still keep my nose above the surface. Eventually I’ll be able to wade out there. Maybe I’ll write something worth two entire minutes of someone’s attention. Until then, I’ll write two crappy pages over and over until someone wants to read my shi*.

Body back October

I want to focus on my health in October. It’s just been slipping. Or it’s just becoming thirty. I am not sure. Here’s a list of things to improve on:

  • Sleeping more: Likely the most return on effort. If I can nail my sleep, the rest of this list will be a lot easier. If I do all the others but sleep 4 hours a night, I’ll feel horrible by the end of the month, guaranteed.
  • Workout consistency: I want to work out 3-4 times a week and lately it’s been more like once or twice a week. So I think I need to find a workout I can do every day, knowing I’ll miss a few days each week.
  • Eating less: I eat somewhat clean, but I eat more than is optimal for my goals. Between cleaning up my diet further and just eating less, I think I should focus on eating less right now.
  • Meditating more: I need to just do this. I believe it works. Which might be one of the first steps for it to work. I get less stressed and more focused when I was starting meditation. That also might mean I had less on my plate and felt like I had time to meditate. I’m sure I’m not the first one to say it: maybe I don’t have time not to meditate.
  • Fixing my knee: This is in line with the workout consistency. I need to get my knee checked but the last time I did, my PT suggested a few exercises (clamshells, various leg raises) to do every day. I need to do them.

I’ve read it’s bad to start a bunch of habits at once. A few of these are things that I’ve done consistently for long stretches. I think I’ll be able to make it a productive month. I’ll be sure to keep you updated when the month is over. I’ll even add it to the todos.

Mise En Place

I’m giving the Chromebook another spin. I was so enthusiastic about it initially. Then I finished my 100 posts and shifted over to tinkering more to work on layout and how to present what I had written. I didn’t really share the project widely. I still haven’t.

I’m writing directly in the WordPress editor. Here I’m trying to summon some of what Seth Godin says about writing his posts directly in the Typepad editor. I wrote about this in “Seth Godin and Stephen King’s pencil“:

The significance of writing in Typepad is not that it’s the best editor or anything, it’s that it’s the location where Godin goes and knows exactly what he’s there for and what he should be doing.

I just block quoted myself paraphrasing what Godin said on Tim Ferriss’s podcast. But I shouldn’t ramble so much. Godin is top of mind because he was on Brian Koppelman’s podcast this week, in an episode titled “Seth Godin Doesn’t Believe in Writer’s Block”. 

Godin and Koppelman discuss writer’s block after Godin says it doesn’t exist. I was also happy to hear Koppelman mention But What if We’re Wrong by Chuck Klosterman. Something from that book is that other explanations will come up but it doesn’t really change the day to day. Whether we’re in this dimension, in a simulation, or in a  multiverse, tomorrow is still going to happen the same way.

Koppelman relates that to writer’s block in that we can say it doesn’t exist or give it a different name, but the feeling is there. He found it helpful to define it as a block to acknowledge that there’s something that can be removed.

Godwin has a request for people with writer’s block: show me your bad work. You would rather be a stuck writer than a writer who is writing stuff you are not proud of.

What I’m arguing is, let’s begin by saying “I am writing work I am not proud of. I would like to to be better.”

While they might not agree on what it’s called, they seem to agree with how you deal with it. Writing a lot. Koppelman is a big proponent of Morning Pages (I’m a fan and always want to do it more). Seth says you just get into a place where you’ve got what you need and you just write. Even if it’s bad.

Mise En Place—it’s its own reward. The chef lines up all the ingredients, pre-cut ready to go. So that when the things are fired up, you just cook.

Well my friend Isaac Asimov, who published four hundred books before he died. Isaac got up every single morning, he used to near the Lincoln Center. He sat in front a manual typewriter and he typed for five hours. And if he didn’t have anything to say, he still typed. And that’s the answer to having enough good ideas. You have to have bad ideas.

Oh I’ve got bad ideas alright. Let’s see if I can learn to get to the good ideas.

I sat down forty minutes ago and thought I wouldn’t have anything to write about tonight. I felt blocked, but I resolved to sit here and type.

I am writing work I am not proud of. I would like it to be better.

In your head, then on paper, then on screen

I guess it’s pretty clear that the programming portions of Flash Boys were most interesting to me.

They had been forced to learn to program computers without the luxury of endless computer time. Many years later, when he had plenty of computer time, Serge still wrote out new programs on paper before typing them into the machine. “In Russia, time on the computer was measured in minutes,” he said. “When you write a program, you are given a tiny time slot to make it work. Consequently we learned to write the code in ways that minimized the amount of debugging. And so you had to think about it a lot before you committed it to paper. . .

I don’t plan as much as I should.

Even with this website (and its previous Jekyll iteration), I open the files up and do some HTML/CSS edits. Live coding! I think there’s a place for it but for laying content out I think the results will nearly always be better by doing it in a graphics editor first.

When I’m designing in code, a lot of it ends up being ready, fire, aim. Then I stop when I have something acceptable. There’s a chance it’s good, but it’s unlikely to be great.

Doing a layout on paper and then in Sketch (or other graphics editor.

On a project with a team, there’s usually some kind of project management. Design and development might be done by completely separate people so this isn’t tightly coupled.

Working on this site solo, I just need to be better about remembering to plan and design before writing any code. I’ve tried restricting my time by saying “Oh I’ll only tinker on the weekend. I’ll write during the week.” The restriction is artificial though, so I’d find myself in a code editor on any random day instead of writing.

This time around I’m just keeping an updated list on a todos page. It gives me the satisfaction of knowing it’s written down somewhere that I might possibly get to down the road. Then when I set time aside to tinker, I’ll have a list of things to better prioritize.

It’s not quite programming on a 1980s machine with a limited amount of computer time. Or programming on paper while in prison. (Like Serge did later on.)

This reminds me of something from Founders at Work. The del.icio.us founder talks about building the site in small pieces over years.

I could come in and look at it, figure out what I’m doing, do it, and be done for the day in 15 minutes. So if I could get one thing done a day, I was happy. A lot of stuff, if I could spend more time, I did, but as long as I could get one or two things done a week total, if I didn’t have time, I didn’t have time.

If I didn’t have time, I… skipped sleep to get it done, stressed over it, got frustrated? Those are certainly options, but a lot of times it might be best to just not do it.

It’s one of the luxuries you can take with a side project. And I’d say it’s a luxury you need to take if you’re in it for the long run.

Todo: break the items in the todos page into smaller pieces.

Sunday Journal: 30 Days, No Tinkering

I won’t edit HTML/CSS until I hit 30 (new) posts in WordPress. How’d I get to this point?

Basically everything I hoped for with WordPress in terms of not tinkering has absolutely not come to light. I tinkered with so much stuff this weekend. I even went back and forth between themes. I went about it pretty poorly. It makes a nice demo to code things live. And is relatively fast. But if I sat down, sketched it out, thought it through, then moved it into code, I would’ve been better off. It’s fine. I think it’s in a good place now for the types of posts I plan to focus on: book notes posts, photo posts, and link posts.

I used WordPress for my blog in high school. Prior to that I tried Greymatter and b2. WordPress has changed a lot in over ten years. What hasn’t changed is my development approach. Change some things. Check it out. Change some other things. See if it works. It didn’t work. Google around for some snippet to try.

You can spend many many hours doing this and I did. I’m going to hit the gym for a mental break, then I’ll try to do these things for a few quick wins:

  • Move more book notes posts over. These are going to be the bulk of what I want to write about. A main motivation for moving over to WordPress is that a lot of times I’m reading and want to write about a passage. But then I think it should be a part of a bigger book notes post that I’ll write after I’m completely finished with the book. Eventually I forget and these things I had a lot of ideas about get lost in the rest of the highlights. I’m betting a collection of 3-5 individual posts as I read will be better than trying to do one long post at the end of reading.
  • Create a to-do page. I’ll write down things to do in the future when I set aside time to tinker.
  • Migrate my 100 Days, 100 Posts page. This will still link to the Jekyll versions of the posts. I’m oddly happy with the collective pile of garbage this is. Because it’s my pile of garbage. This blog will slowly swallow all my other online work as I figure out sensible ways to present them here. The easier part is everything from my Jekyll blog that used to live here. The harder things will be moving my designsprints.com stuff over.

iPhone 7 Plus Sample Photos

Thought it’d be good to share some first impressions of the iPhone. Not sure if the phone is using optical zoom. I can’t seem to trigger it manually. The photos seem pretty great. I think my iPhone 6 photos were good too. (Quality wise not like my photographic ability.) I’d need to do some side by side stuff to really be able to tell the difference and what kind of improvement it provides. I’m not gonna do it. I just want to show what’s possible with an iPhone.

c00d385c-0323-4c60-88e4-b00eda7700ae

ad3b9f32-1a26-4122-86bd-2dc5b8ce4da4

7f6e0bc4-018b-4b3d-b1a0-c3353a0cd70b

50b17c84-7f93-4cef-b846-e8b38060c2cd

106208a1-7925-44bb-bec2-f386e78d963e

8994638f-b822-4794-b2be-c6623449dbaa

aca56d61-6051-4599-b1e5-ba74528502db

Thirty days of WordPress

I did 100 days and it was a good amount of time to figure out a bunch of things I shouldn’t do. I still want to nail down what I should be doing. I want to write. I want to improve as a writer. That means sharing some work. Maybe not all the crappy pages. Just some of them. We’ll see.

Anyway for the first 100 days I used Google Docs and Jekyll. I was familiar with Jekyll. I love using it for putting sites with some structure together. I saw that it could handle hundreds of posts. Paul Stamatiou has a Jekyll blog with thousands of posts. Ten years worth.

Now he writes great, very (very) in-depth posts every couple months. I think Jekyll is great for that. I also think it’s great for a custom photo blog like he has.

Jekyll sometimes made me feel more like Mr. Hyde. I would just want to post something then a couple of hours of HTML and CSS later…

So I installed WordPress. Something I realized about a lot of people I’m looking at whose path seems to make sense as a writer—they aren’t using Jekyll. Even Paul’s thousands of posts were converted from WordPress posts.

I want to write shorter pieces more frequently. (Taken to that extreme you’ve got Twitter.) Docs and Jekyll allowed me to separate writing from the code. But not always the publishing part. I’d need to finish things in Markdown. It’s too close to code. Keep me in a rich text editor.

I want to be able to go through the entire thing on my phone. (Without setting up a bunch of scripts.) Everyone likes the feeling of completing a post. I’ve had WordPress blogs in the past and there’s something to hitting “Post”. It’s more satisfying than running a deploy script.

While I was a little too optimistic thinking I’d avoid tinkering (trading Ruby for PHP and MySQL—all of which I know next to nothing about).

So here it is. Just another WordPress site. Hello world!

100 Days, 100 Posts

Two crappy pages to two (hundred) crappy pages. And 98 other posts in between. I want to have a place hold the 100 posts as I continue adding more to the site. This page has the posts in categories.

Japan Trip

I started the 100 days by posting twice and then getting behind by about 14 days to go on a trip to Japan with my girlfriend. The trip also gave me a good amount to write about.

Writing

A lot of the things I wrote were about writing. And about blogging and this project itself. Navel gazing. Still, I think there’s value because it was at least a small step up from recalling the day’s events. And I’ve read and enjoyed plenty of other people writing about writing and blogging about blogging.

I wrote a couple posts as stray notes. The idea here was that I could write one-off notes as I went along.

Friday Links

Heavily inspired, mostly stolen from Tim Ferriss. I wanted a weekly post that was heavily structured so I wouldn’t have to think. Find four links and this would write itself.

A lot of times, these took the longest to write. The links I gathered were usually good to read through again and then I’d go read other stuff from the author and on and on. I guess a better description would be that these were the hardest to focus on.

I also think they’re a great place to start to get a sense of what topics I’m interested in.

Sunday Journal

I was writing about writing a little too much and it was seeping into every post. Toward the end I tried to be more conscious of this and moved these thoughts to journal posts.

I usually wrote about something I heard in a podcast. Major major navel gazing. When I do send out a newsletter, I suspect it’ll be some mix of Friday Links posts and Sunday Journal posts.

Design

When I started, I wanted to deliberately avoid writing about design. Then I wanted to do some design exercises to see how I could improve this blog before sharing it with others. Then I thought it’d be good to share that process and wrote a few posts.

In all that, I remembered I enjoy writing about design. It’s probably because writing about design process means I can create content by sketching or playing in Keynote instead of strictly writing.

Sketches

Here’s my second note for Comedy Writing for Late Night TV (here’s the first note). Some meta points: I tried reading this with the tips I linked to about How to Read a Book (PDF).

  • I did a one hour reading session.

    • 6 minutes previewing: I always estimate that I can read 1 minute per page so I marked off the next 44 pages. I also thought of some questions to keep in mind after skimming.

    • 19 minutes reading: For a pomodoro

    • 5 minute break: Ok so this break makes it 65 minutes total

    • 25 minutes reading:

    • 10 minutes writing: That’s when I did the vomit draft of this post.

  • I ended up reading 83 pages in 44 minutes of reading and I felt very focused. I’m not sure if it’s meditation or what. I think it’s meditation. I noticed a lot faster if I wasn’t paying attention to the book so I didn’t need to re-read. I also was reading a hard copy of the book. I’ll see how helpful it is when I try this on a Kindle book.

Okay, enough writing about reading.

As mentioned, I had some questions in mind while reading. I’ll answer those now, for this post.

How can I apply what I learn?

I don’t work for a late-night TV show. I don’t write comedy regularly. I’m not part of a writing team. What I have in common is that late-night TV is the schedule. I’m trying to write every day. Their writers write every day. I’m trying to write entertaining posts. Their writers are focused on entertainment.

This reminds me of Ben Orenstein (developer at thoughtbot) mentioning that a tech talk should be entertaining. It’s not always the underlying point of a talk, but entertainment is the most effective use of the medium. If you want to get your actual point across, be entertaining. Here are some of Ben’s tips and a great talk about this: How to talk to developers (Rails Conf 2013).

The challenge in applying this is that I might not have an actual point.

What are the main points of the chapters I’ll be reading?

The chapters I read were about sketches. Beyond the monologue, writers create jokes for the other segments. Here are the different types of sketches in each chapter:

  • Joke basket sketches: These are collections of jokes built around a theme but without a storyline. Joe Toplyn explains how to create characters for these sketches. I mentioned my first post on this book that I used to catch a lot of The Tonight Show. My dad would watch a VHS recording of it every morning when I was growing up. I really enjoyed seeing Jay Leno’s Mr. Brain as a character example.

  • Story sketches: A story sketch is your traditional comedy sketch. He explains the steps then breaks down a story sketch called “SFX Burglar” on Conan O’Brien, showing how each step is applied. It was really cool to read his step-by-step explanation, read the raw script, and then finally watch the sketch on YouTube.

  • Parody sketches: Similar to a story sketch but based on existing things. He does another explanation and breakdown. This time it’s the “Oil of OJ” sketch on Jay Leno. I thought everything was on the internet but I couldn’t find this clip. The explanations are detailed. Joe Toplyn even shows example lists of associations that lead to the combinations used in the “Oil of OJ” sketch.

I’m really really enjoying this book. And I liked the results of this hourly reading breakdown. I have about 140 pages left. I might be able to finish the book in a couple hours and have a couple drafts of book note posts to share.