tl;dr:“I had some requirements in mind: (1) I want to tag notes, track things like date, who was there, what the key topics were, and be able to search based on tags. (2) Create action items, and be able to ask “what action items have I not yet done?” (3) It has to be super easy. I want to be able to jump into a meeting and have my meeting notes ready to go.”
tl;dr:“I had some requirements in mind: (1) I want to tag notes, track things like date, who was there, what the key topics were, and be able to search based on tags. (2) Create action items, and be able to ask “what action items have I not yet done?” (3) It has to be super easy. I want to be able to jump into a meeting and have my meeting notes ready to go.”
tl;dr:“In this post, we're going to explore queueing in the context of HTTP requests. We'll start simple and gradually introduce more complex queues. When you're finished with this post, you will know: (1) Why queues are useful. (2) 3 different types of queue. (3) How these 3 queues compare to each other. (4) 1 extra queueing strategy you can apply to any type of queue to make sure you don't drop priority requests.”
tl;dr:“In this post, we're going to demystify hash functions. We're going to start by looking at a simple hash function, then we're going to learn how to test if a hash function is good or not, and then we're going to look at a real-world use of hash functions: the hash map.”
tl;dr:“I had some requirements in mind: (1) I want to tag notes, track things like date, who was there, what the key topics were, and be able to search based on tags. (2) Create action items, and be able to ask “what action items have I not yet done?” (3) It has to be super easy. I want to be able to jump into a meeting and have my meeting notes ready to go.”
tl;dr:“In this post we're going to focus on the ways that a single load balancer might distribute HTTP requests to a set of servers. We'll start from the bottom and work our way up to modern load balancing algorithms.”