Monthly Archive: July 2014

What I Wish I Knew About Computer Science in High School

I wish someone had explained Computer Science to me when I was in middle or high school.

Not the syntax of whichever language the school’s computer lab chose to use, not the same-old contextless exercise of adding two numbers together and producing a result, but what it would mean to choose a life in computer science.

A life as a maker, not a consumer. A life of flexible work options based on my own skill, drive and preferences. A life of curiosity and endless learning, with earning potential directly dependent on risk taken. A life of developing the ability to benefit society firsthand, either alone or in a team.

That’s what I wish I knew.

I majored in journalism — not a terrible choice in the 1990s, but better as half of a double-major with a more practical complement.

Fortunately for me, I taught myself HTML and Linux, then chose to work in online journalism and enjoyed several years of walking on fresh snow. I never forgot that feeling.

I went back for a technical master’s degree but shied away from pure Computer Science because I was afraid. Afraid I couldn’t compete with people who’d been coding since they were 12, who majored in CS at college the first time around, who were wizards.

I tried a few CS classes or books periodically — C, Python, JavaScript — but always found them incredibly difficult compared to other subjects, so I assumed I wouldn’t be good at programming.

I didn’t realize that intense difficulty is normal in CS. No one told me that everyone goes through it, that the learning curve is so steep you can’t even seen the first base camp when you start climbing Code Mountain. All you see is clouds.

I finally picked up Aaron Hillegass’ awesome Objective-C book in 2012. And an amazing thing happened: From cover to cover, I understood it.

Which is how Objective-C became my first (real) programming language.

I spend a lot of time now thinking about how to change this story for future nerds. Why didn’t anyone mention computer science to me when I was in high school? Why did it take so long for me to find the right explanation? What was it about Aaron’s book that made it the right explanation? And why don’t more people talk about the broader context instead of M_PI when teaching CS?

Simplicity in CS is just plain scarce. Addressing questions like:

  • What are the basic building blocks of code?
  • How can true beginners understand these concepts?
  • How can they transfer those concepts to different languages and build on them in more complex projects? (I found there was a true roadblock as I got deeper into iOS, which I overcame by attending the Big Nerd Ranch bootcamp in person, but not everyone has that option.)
  • How can they climb the intense learning curve successfully? (Just acknowledging up-front that it’s intense for almost everyone would help.)
  • How can they understand what studying computer science means, from a productivity and career-potential and lifestyle perspective, if no one ever tells them?

In short, how is computer science not required by default in public schools yet? And how is it so poorly explained by the vast majority of teachers?

It is not rocket science. And it doesn’t have to be explained that way.

Hulk, Smash! C for Fun

I struggled with Learn C the Hard Way. I wasn’t engaging with the exercises. I typed and typed and tried to motivate myself, but C’s function-based flat-file-ness and inscrutable function names stymied me.

This was the language I’d failed to learn twice before.

This morning I spoke with Jessica McKellar, a resident at Hacker School, and she turned this whole thing around.

She suggested ditching Learn C the Hard Way and instead learning C a different way, by diving into a book called Hacking: The Art of Exploitation. This made sense to me for two reasons:

1. Although I have no significant background in C, I studied information security in grad school and have broad context around network security.

2. It sounded much more fun.

After speaking with Jessica, I sailed through 100 pages of Hacking: The Art of Exploitation, typing code when I felt it would be useful and reading the book when I felt that would be useful and even, as a bonus, learning a little bit about how assembly language works.

I can’t wait to get back to it tomorrow. This experience reminded me that pivoting is not just for business ideas. If I’m learning something and not loving it, there is almost always a way to switch tracks without giving up.

This is some kind of basic life lesson that I have been forced to learn over and over. Keep adapting, and it’s almost impossible to fail. Fail to adapt, and failure becomes almost inevitable.

The Startup Weekend Roller Coaster

One thing I promised myself when my journeys began was to do things that scared me.

This weekend I did something that scared me. I jumped into Startup Weekend Social Impact Edition with no plan and no idea what to expect, and emerged amid a solid team working well together around a good idea.

Friday night, I pitched an idea that I came up with on the spot. I wasn’t planning to pitch anything at all, but thought it would be a good experience to try it. My idea wasn’t selected, so I joined a team and prepared to work all weekend toward our goal and have a great time.

By Saturday afternoon, our project was in disarray. Disarray. Our initial market research — the part where we actually left the building and talked to people — indicated our product might not resonate with people. We knew we should pivot. But we didn’t agree on which direction.

I felt myself curling up inside and imagined spending all weekend just arguing about the product, without actually making a product. I didn’t know which direction we should go, I just wanted to spend the weekend making something. So I put my head down and kept coding. At worst, I figured, I’d make an app prototype that we could tweak when we settled on an idea.

Two of our team members left. I felt bleak. It was late afternoon, and we didn’t have much to show for it. And then suddenly (I’m not really sure what happened here), it turned around. We decided on an idea, which was close to our team lead’s original idea, and just went with it. No one seemed initially overjoyed, but from that moment we were okay and things started clicking.

We spoke with mentors. We iterated. We shared ideas and split up tasks and generally worked productively and well together. It was fun. I’m not sure what changed. It’s like the pit of despair opened up and there was a path and we decided to get up and walk down it to somewhere.

We worked productively until 11 p.m. Saturday and then disbanded for sleep or social life, reconvening on Sunday. We created and refined our pitch deck and finished web and app prototypes. Finally, we presented our pitch and demo to a panel. Our service seemed to strike some right notes, and we received constructive and thoughtful feedback.

On the whole, I think our presentation was a success and our proposal was viable — nearly unthinkable on Saturday afternoon. I’m not sure what will come next. But this was a valuable experience, and I’d do it again.

Here is our web prototype and our app prototype code.

Key takeaways: It is so vitally important to seek customer and market validation early. Negative market feedback is a great opportunity to adapt and learn. Sticking with a team instead of an idea is a great idea.

The Last Days of Drifting

I wrote this during a long layover at Frankfurt Airport, on my way back from Barcelona to the U.S. in February. When I got home, I gave notice to vacate at my Manhattan apartment and gave away all my stuff, and this crazy adventure began.

At this point, I’m unifying my life, slowly merging my various social media profiles, learning and exploring and creating resources to help other people learn and explore. Looking back at where I was, I give thanks that I’m past that period.

Time in the airport spirals. It spirals in a haze of pleasant white light (in the business lounge) or harsh fluorescence (in the walkways) and becomes endless. I read half of a book (Nail It Then Scale It). I jot down ideas for iterating on a project. I get more tea. Then water. Then tea. Back and forth to the counter, aimless, sliding seamlessly on Lufthansa’s predefined paths. 

I’m bored. I thought a seven-hour layover was a good idea. 

I do like long layovers in a strange, undefined way. They are the fuzzy part of a trip. The pit of potential productivity. I could create something great here, in the airport lounge. I could write something, plan a new feature, get a new idea, implement new code, or just do nothing. Tea. More tea. Back and forth. 

Mostly people don’t talk to each other in the business lounge. I find I’m more productive, because I’m not constantly seeking the next conversation. I meet people on planes all the time, because we are stuck there and the proximity favors talking, at least before we fall asleep or tune each other out with headphones.

I imagine being stuck for days or weeks, walking endlessly from terminal A to Z in simulated comfort, buying boxes of Niederegger marzipan because it is the best thing in the airport. Washing it down with Courvoisier. Yuck. Or water, sold with a smile. Guten tag, Hola, Hello, Hallo, it all sounds the same. The food is better in Europe. 

The guy behind me left. That’s good, because I was uncomfortable writing with him there, felt that he was peering over my shoulder even though of course he was not. Airport privacy is transparent, artificial. We are each perfectly alone and completely seen. I am sure there are cameras in the ceiling. 

I wonder who is doing actual productive work here and who is aimlessly browsing the Internet or reading a book for pleasure or just staring into space. Staring into space is actually a good disguise for productive work, happening behind the scenes. 

Right now my life is in fragments. I am not on Facebook. I alternate between relief to have avoided drama, and wishing for a presence so I wouldn’t need to start a blog to post thoughts. I want to unify my social media presence, so my life is seamless and I can share what I want when I want with who I want. I have my LinkedIn persona and a new G+ page, a blog on organic food and general wellness, and a site for organizing MOOCs and online learning resources. I have a dormant site for people who want to move cities. 

I really want to unify my life, not my social media presence.

The airport is buzzing quietly with the noise of suitcase wheels and heels. People coming and going, in between. 

Hacker School, Day 3: Xcode Plugins and C

Kicked off this morning by writing an Xcode plug-in that loads correctly and sets a custom menu item. The next step is to make it function, and I fully realize the hard work lies ahead. I like that the goal of the plug-in is increased accessibility.

I also made slight progress in understanding C, which may be helpful since the iOS stack of Swift, Objective-C and C likely will coexist for a while.

I came home and researched Xcode plug-ins, Sublime Text, and iOS note-taking apps for hours. I know where I want to go, and I’ve specced out functionality, so it’s a matter of figuring out implementation details. I’m enthused and have a plan for tomorrow and Friday.

And I really do intend to learn C somewhere along the way.

I’m not tired at all, but it’s time for sleep anyway.

The Explorer’s Dilemma

Exploration is much harder and much easier than it once was.

Physical exploration is much harder. Humans have swarmed across the planet, marking territory, discovering caves, streams, mountains and seas. Aside from the deep seas and the magma lakes below Earth’s crust, little remains to be discovered. I’m immensely fascinated by northern Canada, which remains sparsely populated, especially in places like Baffin Island.

Intellectual exploration and innovation are exponentially easier. The Internet has made huge quantities of information available to nearly everyone at fast speeds. And it’s easier to find people to work with on projects and problems, because they can be next door or on the other side of the planet.

I’m engaged in this type of exploration at Hacker School. I spend all day in a room alongside other skilled people with various backgrounds and interests, and we try to learn a lot rapidly and solve interesting problems.

Today I made good progress: I brainstormed approaches to a speech accessibility project; worked on Learn C the Hard Way, including a pair programming session on C switch statements; and attended sessions by resident Mel Chua on learning styles. Learning styles aren’t destiny: They reflect personal preferences and natural tendencies, but it’s possible to become comfortable in a non-innate style.

My personal learning style is somewhat reflective, extremely intuitive, evenly visual and verbal, and somewhat sequential. I’m constantly seeking connections between different ideas, then piecing them together in a logical way toward a goal.

What’s great is that thought patterns and ideas are not a finite resource. They’re endless, endlessly renewable, and endlessly interesting.

Hacker School: Day 1

Day 1 at Hacker School. I wasn’t sure what to expect.

I imagined a loud space. A noisy place. An echo chamber, or a concentration vortex. I was a little worried, since I need quiet to concentrate sometimes.

I found a large space, a focused place, a concentration vortex of the good kind, and a group of people ready to share their expertise and make our first day as smooth as possible.

Any day that starts with meeting 60-plus people who are all interested in learning and creating is a good day.

Today, as expected, was a setup day — meeting our cohort and facilitators, a brief check-in to discuss goals, welcome and configuration sessions to make ourselves and our computers ready for three months of intensive work, a git session, and a bit of free time to work on our own projects. At night we headed to eBay for a talk on distributed systems, which I enjoyed and followed up with further reading.

A giant stretch of free time awaits me tomorrow. I am so looking forward to it. I’ll be surrounded by other people making the best possible use of their time — and that motivates me.

My Big Nerd Ranch Diary

I took vacation to attend the Big Nerd Ranch iOS Bootcamp last year. It was my favorite vacation ever. That’s when I knew I was on to something.

Today, I start Hacker School. I’m taking this moment to look back and share my Big Nerd Ranch diary. Every night in rural Georgia, I came back to my cabin in the woods and wrote my impressions of the day. Here’s what happened during that week:


I’m in my cabin after Arrival Day at Big Nerd Ranch — I’ve been anticipating this trip for about a year but wasn’t sure what to expect. I’m impressed so far.

First, the staff at Historic Banning Mills are heroic. Although I grew up camping as a Girl Scout and once could survive on Mountain Dew and Skittles, I am a city girl at this point in my life and had a health crisis that scared the Skittles right out of me. The thought of spending a week in the woods eating hush puppies from the lodge kitchen didn’t thrill me.

When I asked about food, Big Nerd Ranch staff said they would ask the kitchen at Banning Mills what they could do. The kitchen said if I could ship food direct from a provider to them, they would cook it for me. That scored about 1,000 points right there. I used Boxed Greens, which ships organic food nationwide overnight. The food arrived a few hours before I did.

THEN the kitchen staff kind of got into the idea. They said they wanted to buy more food to complement the contents of the box. They’ve considered offering an organic option for students, so I think they viewed this as an experiment. In return for their awesomeness, I gave them carte blanche to create whatever seemed interesting to them. My first meal, this evening, was delicious: a kale/peach/cucumber salad, followed by salmon over lentils with kale, tricolor peppers, and onions. (The regular food also looked tasty — salad and then herbed chicken over mashed potatoes with asparagus.)

Now I’m in the cabin, relaxing. Speaking of the cabin, it is huge and gorgeous.  More good things about today — the wonderful shuttle driver at the airport who did not leave anyone behind, and my fellow classmates, who are friendly. I’m looking forward to spending a week getting to know them better while my brain gets a workout in the class. It’s a challenging (grueling?) schedule, but I’m ready and plan to make the most of this opportunity.

Which means I’m going to sleep soon. More tomorrow.


Class today was surprisingly easy and doable — but I am so glad I worked my way through the BNR Guide to Objective-C Programming last year! Struggling with this book over four months helped me rush through half of it today. We cover the other half tomorrow. If I’d walked into this class with no programming experience at all, I’d be in trouble on Monday, when we dive into iOS apps.

I still may be in trouble on Monday. The reviews I’ve read say the pace picks up fast then, so the fact that I’m finishing challenges quickly puts me somewhat at ease, since I may be able to keep my head above water on Monday and Tuesday. After that it’s anyone’s guess, because at some point we will start covering material beyond the point I’ve reached in my BNR iOS Programming Guide self-study. Then I’ll be learning entirely new stuff. And that takes longer, but we’ll still be flying through the material. I’m hoping that by getting the basics down well in this weekend intro, I’ll be able to survive through the week with some understanding and real ability to get the most from the class.

Also, I learned that there is an advanced book for the advanced class! It is, sadly, not available on Amazon or in any bookstores. Another reason to possibly take the advanced class later this year or next. I’m hoping that between now and then, I can dive in and create some real apps for free on the app store, just to test the waters and see what happens.

Anyway, more tomorrow. I was surprised not to find myself tired or burned out by 9:30pm, when I came back to my cabin. Maybe it’s a good sign, but I’ll wait and see how tomorrow goes. Food was delicious, as it was yesterday, but I am afraid my statement that, “I eat fish,” was received as, “I eat fish at every lunch and dinner.” In truth, I eat fish a couple of times a week. If fish continues to appear at every meal, I may have to say something — but what can I really say, anyway? They are preparing custom organic meals for me! Today some little potatoes and wax beans appeared — I think they are shopping for me, to supplement the stuff I sent in the box. Amazing kitchen, amazing place so far.

More tomorrow.


My brain is starting to get tired. We rushed through many topics today, and while I understood most things, they are starting to jumble together in my mind. I’m hoping my mind can sort it out by the end of the week, and that I don’t end up dreaming all night about coding, because that would be about 20 hours of coding per day, which is a lot more than 12, which is what we are essentially already doing.

Today we finished the Objective-C book and I reviewed the documentation for NSArray, NSMutableArray, and NSDictionary. Tomorrow we dive into iOS Cocoa Touch programming.

I am loving the class, despite my brain-whir, and found myself wishing I could attend for two weeks or a month and really delve into more and more advanced topics. We’ll see how I feel on Thursday and Friday; if I still feel the same, this may be amazing for me.

The classroom is light, bright, and free of awful bugs. There were some small winged creatures on my desk this morning, but I let them be and they flew away (or my neighbor squashed them while I was in the bathroom).

More good conversations with other people who are here to learn; I love being in a room full of people who are mostly there by choice, since the attitude is amazingly good and therefore so is the experience overall.

Organic food from the kitchen continues to be good, although also salty; today I learned that this is not limited to my dishes. All of the food is very salty/spiced. I keep drinking water; can’t bring myself to complain about it. Lunch was shrimp escabeche — over red cabbage with a tomatillo sauce (I’m not sure what was in the tomatillo sauce, but it was awesome). Some delicious cauliflower with dinner, and nicely cooked yams, plus more fish. I don’t know if I will eat fish for a while after I get back.

It rained today so there was no nature walk. I did see zip-liners breezing past through the pouring rain.

More tomorrow.


Day 4 of my adventure, Day 3 of class. This is where the blogs I’ve read have dropped off, and now I see why. We covered a prodigious amount of stuff — nearly 200 pages of the iOS Programming Guide. I am getting a better understanding of some things that confused me the first time around, but I still wish I had an extra day to put it all together — the basics, the new techniques — but we just keep steamrolling forward. I don’t have time to do all of the Challenges in the book, and I really wish I did, because I’m learning a lot and I’d learn even more then!

I think I’m keeping pace reasonably well. A few people are behind me, some people are ahead of me who have a lot of coding experience, and some are about on pace with me. I think this is a marathon and not a sprint so I’m okay with it.

I do feel gratified doing something for my own self-improvement that is also productive and useful, potentially, for others who might use my apps someday. I hope I can build a lot of productive and useful apps upon returning home. I certainly feel like I’ll have a running start.

This is a good environment for learning. I have almost no time to myself, which is weird, but I’m getting a lot done and reminding myself that this is temporary and necessary. What I am getting is time to concentrate, even among others, which almost never happens. I forgot how much I enjoy super-focused days.

The food remains delicious — and today it was not salty, since when they asked me what I wanted to eat, I said I would eat anything they made for me but please to go light on the salt. It was a great food day.

It was a great learning day. I wasn’t tired at 10:15 and only left because I knew I had to get some sleep to keep up the pace for the remaining days here. I found a centipede in my bed when I came back, so I called to ask the front desk if it was poisonous. They said no and also sent a nice staff guy to pick it up and remove it from the cabin. It was a nice little creature, I guess, if I were used to creatures.

More tomorrow. Bedtime if I want to get a full 7 hours of sleep. (First night: 9. Second night: 8.5. Third night: 8. I see the pattern. It stops now.)


Unbelievable amount of learning happening today. I’m starting to connect the dots, and know why I need to make a change. Even when I make a mistake I understand what the mistake was after it’s pointed out to me. I still make mistakes nearly all the time; but I also do some really cool things, like find a method the instructor didn’t know about, and try to figure out how to make it work; or set up new functionality to make things more efficient — and it works!

I’m a little bit on overdrive and finding it hard to sleep, but it’s good — it reminds me that it’s still possible for me to feel alive when contemplating work tasks, and to concentrate hard on something for several days at a time. I spend most of my regular workdays so interrupted by multiple tasks that I feel like I never get anything done. This is a refreshing change. At 10pm tonight when I still wasn’t physically or mentally tired, I realized that this is something that’s been missing from my life for a while.

I’m going to sleep now so that I can function tomorrow morning. I want to hit the ground running — again.

I am in nerd heaven. I think I may have tapped into something really important for me — other nerds.


Today was the first day I felt tired, and I struggled to keep up. We were on a rushed pace to try to make up some time, since we’d fallen behind by about one lecture. By day’s end, we were caught up — but that meant about an extra 2 hours of time. Lectures ended at 8:15 and I wasn’t caught up until 10:30. Lots of other people were there too, and we were kicked out of the learning room around 10:40 (after a few well-deserved games of Typeracer).

There was one point in the afternoon when we were implementing an involved piece of code that only worked on a single image thumbnail and only on the iPad, and I just realized that if I spent time to understand what I was doing I would never get to the *really* cool stuff — Core Data and touch gestures — so I just started typing. Type type type. I implemented the thing, realized I might need to look back at this someday, and moved on.

At points during the day I could hear the instructor talking but couldn’t focus. Maybe it was just an off day for me; but I think my head is so chock full of new iPhone programming knowledge that it needed a bit of time to process it all.

I’m going to bed now to give myself the best chance of recovering and hitting the ground strong tomorrow. I’m still keeping up with the class, but I don’t feel the sense of mastery that I felt yesterday (and yes, I realize that mastery is a good way away — but I was putting all the pieces together yesterday).


Back on track today. We went at a slower pace, I absorbed nearly everything we covered, and I was able to implement some pretty cool apps, especially one that allows drawing. I now have the skeleton of something I actually want to implement when I get home. Exciting!

Class was fun but I can feel the pace winding down. I’ll miss my fellow classmates but have enjoyed the opportunity to spend a week with other nerds doing one of my favorite things on Earth — learning.

I’d love to be back for the advanced course in November, but we’ll see how the year goes. Will I use these skills in the next six months to build apps? Will I push through the frustration when I can’t make something work, and figure out how to persevere, work through the syntax and search the documentation (and Stack Overflow) to find solutions?

We’ll see. More tomorrow — and the next day, I hope.

I’m ready to go home but also not ready. I did better in this class than I expected when I walked in the door. I want to put my new skills to good use and produce apps that are productive for users and for me.

I’m a Big Nerd.


Back home. We had class until 12:30, then lunch and then quickly piled into the shuttle back to the airport. I spent a few hours waiting for my flight there and then got home around 9:30.

I expected to feel mentally drained and tired, but I feel mentally turned on instead. This is awesome. It says to me that I did the right thing, and I love feeling this way. I’m going to keep working on the programming at home, and see what I can struggle through and make in terms of apps. I feel like the BNR class gave me the tools I need to keep learning on my own, and to work out problems when I run into them, because I’m starting to understand the underlying patterns and logic of programming.

Starting to understand. That’s key. There’s a lot more work to do — but I think I’ve got a running start. Now I just need to keep going.

DefCon Notes from a Patio

I found a note I wrote at DefCon in 2006. It’s on Mandalay Bay stationery (yes, because I had no idea where the Riviera was, I stayed at the Mandalay Bay. The upside was that I got to explore the entire Las Vegas Strip).

With HOPE X this weekend, it seems time-out-of-time timely, so I’m sharing some of what I wrote on that paper:

I’m sitting outside on a sun-heated patio, hoping I wore enough sunscreen. I’m at a self-imposed break in the conference action and exhausted, but not ready to give in and go back to the hotel. I’m loving every minute of this. Here there are people who are questioners, who rarely take anything at face value and aren’t here just because work requires them to be here. They all have spent considerable time and effort to be here and learn.

Las Vegas is a facade. I knew this, but it’s different to be here. I’m seeing one Las Vegas — the fake one — but there are four or five different other ones, I think. I want to see the Vegas where people really live, the one where, I’m told, fewer people than anywhere else go to college. If I were 18 and could make reasonable money as a dealer in a casino or unreasonable money as a dancer, I wouldn’t want to go to college either. When I was 28, I might feel differently, but it would be difficult to start over. That’s what I imagine, though I don’t know.

Vegas is lights and lights and fake shoes and gambling and trams and great bathrooms. Vegas is limbo. Vegas is hope. Vegas is faith, Vegas is a soul, in black on neon.

Now I’m late for HOPE X. Back to Manhattan to see what talks I can catch. And stay far away from nerf darts.

Hope X and Hacker School

Yesterday I went to Hope X, a conference I’ve meant to attend for years. The strange thing is that I lived maybe 10 blocks away from Hope for years. Now that I no longer live there, I made it.

I got hit just above the eye with a nerf dart. True story.

The conference is for makers but also has a journalism focus that appeals to me.

I was not the intended target of the nerf dart.

The week was incredibly productive, but not the way I intended. I was at the beach but never went to the ocean. Instead I did some low-level C work with Zed Shaw’s Learn C the Hard Way and worked through some of the Coursera Hardware-Software Interface course, which is amazing. There’s something about getting down with the bits and the bytes and the bauds that evokes the scrolling text of my very first BASIC program in third grade, and the endless efforts to draw colorful graphs on the screen. VLIN. HLIN. My brain actually enjoys this memory.

I didn’t focus on the flashcard app, due to a weird experience with expected help not materializing. I’ll need to tackle the remaining snags by myself, on my own time, to finish the app. The good thing is, I believe I’m creating a solid infrastructure for flashcard-based learning that can be repurposed for many types of content.

What I did instead is prototype a how-to-program video series for true beginners. As an advanced beginner myself, I can still remember what I didn’t understand — and how I wish it had been explained. I wrote a script last week, so when I saw a call on Monday for Lightning Talk topics at HopeX, I signed up. I had no video series ready. So I got to work, recorded three episodes and published two, and gave my Lightning Talk yesterday.

I’m surprised how nerve-wracking the talk was. I’m used to presenting to high-level executives and managers or to industry groups, but presenting to the community feels different, more raw and exposed. I got good feedback afterward, so I think it went reasonably well, but it was much scarier than expected. I also loved it. I’ll look for more opportunities to get more comfortable with this mode of sharing, since I normally love presenting.

I went to the eye doctor this morning and he said I’m fine. I hope I believe him.

Now I’ve just moved into my Brooklyn apartment. Me and my suitcases are settling in. I love having no stuff, because I don’t have a lot of unpacking to do.

Next step is dinner. With other Hacker Schoolers, because I start Hacker School on Monday. I am so psyched and excited to have gotten into this program. It’s going to be intense, productive, and hopefully unforgettable.