Big O Notation is a system that measures and compares the performance of code. It introduces specific vocabulary to relay information about how well an algorithm or piece of code is optimized.
This means we need a general language to say how fast a piece of code processes data and how efficiently it allocates and uses memory for its operations. Here we go through what this exactly means.
When a domain is registered, you need to somehow route visitors to your website through this domain. So how do you do that? You’re often asked to add a CNAME, A, MX, or TXT record. If you’re like me and have followed these instructions, somehow magically everything works. Your domain suddenly points to your website, your emails get into your domain registered email, and you can access the Google Search Console. But how does that actually happen? What is DNS or Domain Name System? What are DNS Records? I’ll tell you here…
We have been switching our local development setup slowly, but successfully to docker with NFS for speed. Almost everyone at the company is developing on a Mac system and so with the new Catalina release, everyone either pressed the “Update” button, or, like me, woke up to a new OS, got their cup of coffee, and typed in
Standard Ruby on Rails best practices suggest that we should define our validations on the model object. RoR gives you the tool, aka DSL (domain specific language), to implement these validations. For simple situations, say a signup form, this works really well, but what about more complicated scenarios? What if your model serves several different controllers? Or what if, for example, different types of users could submit different values to the same model? Do we want to use messy
ifblocks to check the
user type and apply the correct set of validations? Probably not. So what’s the solution? Enter Dry-schema.
I wanted to create a responsive react navbar from scratch. I’m going to do this without using any CSS libraries just because I wanted to see if I can… I also wanted to refresh my memory on React. So here we go.
So you have a bunch of jobs lined up in Sidekiq. But for some reason (user action, etc) you don’t need those jobs to execute anymore. So what do you do?