A callback function, also known as a higher-order function, is a function that is passed to another function (let’s call this other function “otherFunction”) as a parameter, and the callback function is called (or executed) inside the otherFunction. A callback function is essentially a pattern (an established solution to a common problem), and therefore, the use of a callback function is also known as a callback pattern. (Source)
Trees are a commonly-used data structure in web development. You interact with a very common example of a tree every time you use your browser, likely without knowing it — the Document Object Model (DOM).
When self-teaching, almost all of us start at the same point. Where do I start? How do I “pick a language”? What do I focus on? I know I did.
Quicksort is a sorting algorithm, used to place the elements of an array into an order. That order is based on comparison — the things being sorted must have a “less than” / “greater than” relationship. (Source).
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.
Week 11 saw the conclusion of our thesis projects. Our project idea centered around solving the problem of scattered personal health information. Throughout your life, your personal health information gets scattered and lost — at doctors’ offices, in various health systems, on paper records you’ll never find again. With no centralized way to store and access this data, often it’s just lost. When you need it, it’s not there. Our goal was to prototype a product that would serve as a personal health information vault — like a 1Password for your health.
Last week, we began work on our final project of the program — a three week long thesis project. Our team convened and quickly began working together to brainstorm a strong core idea. Ultimately, the idea that we selected was based on a concept that has been wandering around my brain for quite a while. I’m delighted both to be at the point now where executing something like this is a possibility, and that the group of people I’m teamed up with found the idea interesting. The idea itself… I’ll leave as a surprise 🙂