Showing posts with label learning. Show all posts
Showing posts with label learning. Show all posts

Sep 4, 2018

rethinking

I've had the opportunity to really rethink some things this weekend and I honestly couldn't have thought of a better way to spend the time. I also read a metric shitton and it was the best thing I could have imagined doing with my time. I feel like I'm finally getting over some really big hang ups with algorithmic thinking and computational problem understanding. It's huge in a way I can't describe, really. The ease with which I can flip through a textbook on programming topics and really grok what they're talking about is mind-bendingly new and radical. I mean, I've had this happen to me before in other domains, but this honestly feels like a new kind of superpower. It's not just a problem domain, it's a way of understanding problem domains.

Honestly, what's helped the most is all of the difficult, non-fiction book reading I've been doing lately. I've really dug in, in the last year, to reading dense, long form non-fiction books. It felt really crazy to be devoting so much time and energy to reading such difficult stuff in my free time, but man has it paid off in spades. What really helped me get through them was picking stuff that I find genuinely interesting and that's just blow-your-socks off amazing. Which is to say, authors that sincerely reward the effort. Ok ok, it's mostly just Hannah Arendt. Her stuff is so good though. Finding someone that can really reshape the way that you see the world is intensely powerful. I made it through Origins of Totalitarianism, The Human Condition, and Eichmann in Jerusalem. I'm really glad I started with Condition, it was by far the most difficult of the three, but incredibly worthwhile. I've got her short book On Violence floating around somewhere -- I seem to have lost track of it but I'm super keen to get to it, if and when it ever shows up.

I took my personal vanity, which has always given me much personal grief in the form of guilt, and put it in this new, intelligent, true context. I look at myself because I want to know what I look like. It's a curiosity. The real negativity comes from feeling like I shouldn't want to look, and really, who needs that kind of negativity weighing down their features.

Slowly drying you out of my head one table turning conversation at a time. It's a weird thing to evict a tenant of any standing. It's not like it's been long, but I know you're better off elsewhere. It's been nice to have my perspective back though, and to really see instead of watching the picture window my fantasies have been projecting out onto reality. They don't call it a reality distortion field for nothing, sweet jesus. One of the biggest reframing of it though, has been to realize how much having you inhabit my head was, in some ways, not unlike having a muse. I agree, it's a very strange and grandiose comparison, but, in some ways, not totally inaccurate. The real tragedy would be to have been inspired by the experience and not embracing that.  In fact, more people should be upfront about their muses, traditional gender roles be damned.

I looked in the mirror today and the first thought was that I'm turning into a terrible looking middle aged woman. Then I tried looking at myself as if I were a man: was I handsome, how strong is my jaw? and, well fam, I don't look particularly striking as a man either. Some things are just good to see.




Jul 9, 2016

journeys

i've been on a lot of journeys, over the years.  one involved learning how to run. one involved learning portuguese. one involved learning to program, android specifically[1].  the journey i'm sort of on now is vocal -- i'm learning how to sing.

there was a point in the portuguese journey, and in the programming journey where i got to where i am now with singing.  that is, where you see that you're not as far along as you would like to get, where you're not sure what the end game is.  all you feel is that you're not where you want to be yet.  there is a moment that i remember well, when I was on a training run along the East River Park, rounding the eastern most point of Manhattan.  There's a building that stands at this point, just a further bit north of the amphitheater.  i had the thought that i didn't really know how to do a certain, fundamental thing in Android programming.[2]

this realization called into question two things.  one, why would anyone employ me to be an android developer since i didn't know this very basic thing.  and two, why i didn't spend more of my free time trying to get better at this thing.  i knew what i was afraid of, and what it would take (sort of) to get better at it.  why didn't i try to do this thing?  i didn't try to get better on my own.  and eventually, i did figure it out.

in my portuguese journey, it was when i went to talk to a portuguese professor, in my sophomore year of college, about what level portuguese she thought that i should take.  i had spent 3 months the previous summer in brazil, and felt that the experience had at least earned me some amount of ability to skip forward, to be in some higher level class than my course work, on paper, put me in.

the conversation did not go well. she could barely understand my portuguese, and i could barely understand what she was telling me.  she switched back to english and finally just said: look, i think you had better take the beginning grammar class with everyone else.

i took the beginning grammar class.  and then i took classes on portuguese literature. and i went back to brazil, and learned how to actually speak.

i am telling myself these stories to remind myself that learning, exploring, growing has never been easy.  that the process is never linear, that jumps in understanding and elucidation comes from hard work, and practice and immersion and continuing to show up.  to taking risks and trying new-ish things.

why did i do this to myself?  why did i push forward to find things out?  because i was curious.  what would it be like to be fluent in a foreign language?  what would it be like to be able to run fast? what would it be like if i could make software applications?  what would it be like if i could sing?


i still don't think i know.  i do know that
i am not where i want to be,
not yet.


[1] i've been delighted to discover that some computer skills, however, are universal
[2] i realized i didn't know how to make a custom view on Android, or even how to make a Java class from scratch (not over-ridding a super class)

Mar 12, 2016

Lists

Sometimes I really want to write
A list
Of all the things I learned
From you

Because that's all that
to me,
really matters,

Anyhow

I worry that
those that really know you
may say that those aren't you
and that maybe you too
will fail to see
Where in yourself those lessons
began
And question

Whether they were you you
Or some internal
astral projection.
it's no matter.

I value this reality,
mine,
All the same

And maybe thats the biggest thing
Or maybe just the smallest
That would be
On the list.

Alongside stopping to
Let the photographer have
His moment
without me

And alongside
how objective truth
is universally
Momentary.

Nov 21, 2015

Mapping Learning

I'm currently writing an app for OSX.  I started it over a year ago, but when XCode ate my project, I gave up.  Before the XCode Apocalypse happened, I had a working prototype built.

In early April, while at DroidCon Montreal, someone asked me what my 'startup idea' was.  I told them about my XCode project that got eaten.  They said it was a good idea, so when I got home I tried to open XCode again.  No luck.

In early October, I was inspired by a tweet about octobuild.com to finish a project in October.  Or at least work on one.  So I opened XCode again.  It worked this time. (Huzzah).

I've been working on it, off and on, since then, just a little over a month.  The prototype no longer works, but instead I'm currently focusing my efforts on making the GUI look and work how I want it to.

I don't know Objective-C.  I've never done any OSX app programming before.  I have done .NET and a fair amount of Android programming, however.  Both of which are GUI-esque systems.  I've been having a hard time grokking how the new system (Interface builder, wtf?) works, so here's a short documentation of things I've learned so far that have been helpful for getting a footing on writing my first OSX app.

- Reading the Apple documentation.  Fairly helpful, but not the right granularity for the most part.  Either too much of a 10,000 foot view or way too granular 1ft view.
- Googling shit / searching for help on Stack Overflow.  Hard to do at the beginning because I don't know what I'm supposed to be Googling for.  What's the proper name for the text input field things?
- Doing an Apple tutorial. I found a really basic, pictoral tutorial in the Apple docs.  This was really helpful for learning the layout of XCode.  But I had mostly forgotten it a few weeks later when I went to do my own GUI.  I can't find the link to it now, either.  However, I did find this repository of sample code.
- Reading articles that are too hard for me.  This is actual a pretty decent strategy for getting a grounding in what the lay of the land is, provided you can hold the fuzzy/frustrated feeling at bay and work on building a relational map of unknown words.  Example: this article.
- Finding the right words.  I finally figured out that Cocoa is the name of the GUI system for Mac OSX applications.  I don't recall exactly what the name for the UI system is for iOS apps.  But it's not Cocoa.
- Asking friends for help. I found this to be slightly helpful, but mostly frustrating.  I asked for help via chat, and I really needed someone in person to show me what buttons to click on the Interface Builder.  Both people I asked were helpful, but neither of them were able to point me to the silver bullet for understanding Mac App programming that I was hoping for.  (One probably doesn't exist).
- Reading the Table of Contents of books.  I find this really helpful for giving the lay of the land - what topics are there to explore?  How are things called?  Sadly, I didn't think to do this until today.  Table of Contents are often available free of charge for any book listed on Amazon (or otherwise).

Something I'm considering trying:
- Buying/borrowing a book. Books are so good at starting at step A and explaining the lay of the land (which is usually what I need the most when working in a totally new paradigm/system.)


I still feel like I'm struggling because the thing that I wanted to have done is not done yet.  The reality is that I may not be moving very fast, but things are making more sense.  That's progress!  I'll take it :)

87 ways to die in brazil

There are an infinite number of ways to die. A good majority of those ways can be found in Brazil.  I was lucky enough not to directly encou...