I ramble a bit whilst high on the potenuse about Big O notation. It's good to understand so go google it. In fact, I'll do it for you, click here. Basically means you should understand the amount of times your code may run. Bigger n is bigger problem. We then make a very smooth transition to the importance of walking. Or really any mindless process to help your brain think through your current problem. We then take a hard right to talk about the known unknown matrix. Scary stuff. We then finish the episode off with a couple of questions. "Why do developers use macbooks?", and "how valuable is leet code to web devs?".

Email me questions on software engineering: [email protected]

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]