‘Just break things.’ ‘Get your hands dirty.’ ‘Just dive in.’
A simple, and infuriating piece of advice that I’ve been given, and given to others. So surprisingly difficult to carry out sometimes. I was reminded by this bit of advice while working on a project last week.
There are two types of people, those who understand recursion and those who understand that there are two types of people in the world… (r/ProgrammerHumor)
But really. There seem to be people who can very naturally digest the concept of recursion, and those whose brains absolutely reject it. I happened to be one of the latter. In this post, we’ll go over recursion generally, and then work through a diagrammed problem example.
I write this week’s post with mixed emotions, as yesterday marked the last day for the MKS30 cohort.
For those like myself staying on for the fellowship, week 12 was actually the beginning of our fellowship. We stepped into that routine, as our cohort-mates began focusing on their job searches. It was an odd, in-between space — knowing that after this week, we would no longer see each other nearly every day. The grind of an intensive educational program like this creates an intense interpersonal atmosphere, forging connections quickly. At times, it’s nearly unfathomable that you didn’t know each other three months before.