Your Coding Teacher

Remember, the task in progress should always be so elementary that its execution is straightforward. Break your task into basic and simple steps that you can execute easily.

"Computer Science is no more about computers than astronomy is about telescopes" - Edsger Wybe Dijkstra

When estimating how long it'll take you to complete a task, remember: A feature will always be more complex to implement than it is to explain.

3 Random coding tips Focus on providing value Don't just copy & paste Don't give up

You don't just leetcode your way into a job. During an interview, what you do before the coding question is also important: - First impressions - Friendliness - Enthusiasm - Passion for learning - Communication skills - ... Friendly good developer >> jerk god

Google infrastructure is divided into: - Regions: Independent geographical areas where Google hosts datacenters. It consists of 3+ zones - Zone: individual datacenter in a region. Ex: us-central1-a - Edge Points of Presence: where Google's network and the internet connect

"Every program has (at least) two purposes: the one for which it was written, and another for which it wasn't." - Alan J. Perlis

A shell sort improves on the insertion sort by sorting incremental sublists. It falls between 𝑂(𝑛) and 𝑂(𝑛2).

What is the fastest way to sort a list of numbers? The answer is, like with many other things in life, it depends: - Size of the array - Almost sorted? - Arrays of integers, doubles, strings, ...? - Does it fit in memory? - Does it fit in one machine - ...

Write a design documents before coding: 1. Expose the problem to solve 2. Propose alternatives 3. Get other people's feedback 4. Design docs act also as doc 5. They save time: explain the design once and let people read it 6. Can help you summarize your accomplishments

Design patterns in 1 tweet Memento: capturing and storing an object's internal state Ex: save your progress in your favourite videogame.

"Every great developer you know got there by solving problems they were unqualified to solve until they actually did it." - Patrick McKenzie

Coding has more human interaction that people think. You need to interact with people to define tasks and ask questions. Also, when you read and write documentation and comments. Consider clear and effective communication as part of your job requirements.

Your career is your responsibility. Nobody else's.

Haskell was invented in 1990 (named after an American mathematician, Haskell Brooks) It is a purely funcitonal programming language and it introduced the concepts of type inference and lazy evaluation putStrLn "Hello, World!"

If you only know how to do only one thing, it's likely that you have gaps in other areas If you are a front-end dev, learn about backend or dive into the internals of Linux Learn other coding languages Play with machine learning, even if you are an Android developer

"One of my most productive days was throwing away 1,000 lines of code." - Ken Thompson

Things evaluated in systems design interviews - How do you deal with ambiguity? - Can you identify the key pieces of the system? - Can you define the scope of the problem? - Can propose a solution that meets the requirements? Because your daily job may look like this

Barriers - Thread synchronization mechanism - Allows threads to wait until other threads have reached the same point, before continuing execution Ex: Sorting a huge array: Split it into several parts, sort each of them in a separate thread and then merge all sorted pieces.

Sparse is better than dense - The Zen of Python