Let’s jump right in!
Let’s jump right in!
A linked list is one of many commonly used data structures. The first thing to know about linked lists is that they are not the same thing as array-like primitives (eg.
List in Python). They are similar in some ways, but they have different strengths and weaknesses.
In this post, we’ll explore what a linked list is, why there’s a need for it in certain situations, and its general strengths and weaknesses, especially in relation to primitive arrays that you’re probably already familiar with.
Big O notation has attained superstar status among the other concepts of math because of programmers like to use it in discussions about algorithms (and for good reason). It’s a quick way to talk about algorithm time complexity.
While it’s a math concept that applies to various fields, programmers are probably one of the most frequent users of Big O. We use it as a shorthand to discuss how quickly and/or with how much memory an algorithm takes to go from start to finish.
Perhaps the part about Big O being most used by programmers is just my carpal-tunnel-visioned mind speaking, but nevertheless! It’s an important concept and here’s a post dedicated to understanding the Big O notation.
It’s 8:00am in the morning on a weekday and I’m sitting in my living room mindlessly having breakfast. My attention is being given to the Medium posts appearing on my feed this morning. In this particular week, I’m occupied by thoughts about careers, so I tap into posts that discuss the topic.
As far as I can tell, this has happened for many weeks or months, even. Since a lot of them sound flat-out like advice, I’ve basically become habituated to fishing for online advice every morning regarding important areas of life like career, relationships, personal growth, and more.
It’s almost the end of the year 2017. I’m 27 and I still don’t get poetry.
I’m inspired to log this here after trying to understand the poem Elon Musk recently shared on his Instagram account.
Hopeful that one day I’ll get a poem and happily go down that rabbit hole.
I dislike email HTML. There, I openly said it! I really had to get that out of my system before I go crazy.
It’s not perfect but it means something to me because I consider it to be the first real feature I’d developed and deployed to a live product with actual users.
While I thoroughly enjoyed the process of figuring out how to build a WYSIWYG (what you see is what you get) email campaign builder, I disliked the part where I had to figure out how to make it output HTML that would be compatible with over 70 email clients on multiple devices with different operating systems (surprise). Entire businesses have been built on how hard it is to get an email to look right on all devices.
Sass is a CSS pre-processor. Even though I’ve been using Sass in many projects, I realised recently at work that I’d only been using it in a very primitive way. Sass mixins didn’t even exist in my mind.
The main ways I’d been using Sass are:
But there’s an incredibly useful feature of Sass that I’d been missing out on. I only accidentally stumbled onto it recently – it’s called Sass mixins.
The air conditioner in my office is really loud but I just realised this: I hadn’t noticed it at all!
Today when the air conditioner stopped suddenly, the office felt almost pin-drop silent, except I could still hear the ringing in my ears. The machine had been bellowing like a Ferrari – unnecessarily loud, but without the sexy to make it at least slightly palatable.
While my damaged ears were still ringing, I scribbled this in my notebook: we adapt and forget that we adapted.