muddlebee

"A little bit of slope makes up for a lot of y-intercept"

01/13/2012. From a lecture by Professor John Ousterhout at Stanford, class CS140

Here's today's thought for the weekend. A little bit of slope makes up for a lot of Y-intercept.

[Laughter]

muddlebee

To find out where disk space is being used:

1. Get to the root of your machine by running cd /
2. Run sudo du -h --max-depth=1
3. Note which directories are using a lot of disk space.
4. cd into one of the big directories.
5. Run ls -l to see which files are using a lot of space. Delete any you don’t need.
6. Repeat steps 2 to 5.

muddlebee

### Hitanshu Gandhi Adivce

- I am not a product guy by trade and it is just critical thinking (after years of beating recieved in the consulting profession) I bring to the table.
- No rocket science - read a lot, ask stupid questions, find learning communities and debate vigorously. Be humble to recognize when you're on the wrong track
- What's the worst that could happen? You'd be wrong - but you'd be so much richer for it. Of course, find places with folks much smarter or experienced than you.
- You learn from getting schooled badly not from coming to the right answer. Not much growth there personally.
- Lastly, ask around - esp in product - always assume you are not your own customer. Always ask how would my grand mom or Ramu kaka (stereotypical tech illterate non MBA aam aadmi) reach?

muddlebee

Q. You should definitely learn something like Erlang/Elixir which completely changes the way you think about building software. Answer:

Yes. They are functional languages. They force you to think in terms of data manipulation through functions instead of objects. Elixir and Erlang have this ideology of "Let it fail". Distributed systems are hard, and there is no way you can code around all errors and exceptions. So you let a process fail if it catches an unhandled exception, and restart it using something called as a process monitor. They teach you how immutability is good. All these ideas you can start using in your day to day languages.

muddlebee

Header 1

Header 2

Header 3 ### (Hashes on right are optional)

Header 4

Header 5

Markdown plus h2 with a custom ID ## {#id-goes-here}

Link back to H2

This is a paragraph, which is text surrounded by whitespace. Paragraphs can be on one

muddlebee

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

muddlebee

# Definition for a binary tree node.
# class TreeNode(object):
#     def __init__(self, x):
#         self.val = x
#         self.left = None
#         self.right = None

class Solution(object):
    def invertTree(self, root):
        """

muddlebee

def secondMax(nums):
        
        """
        :type num: List[string]
        
        """
        if len(nums) == 0:
            return -1
            
        fmax = float('-inf')

muddlebee

def secondMax(nums):
        
        """
        :type num: List[string]
        
        """
        if len(nums) == 0:
            return -1
            
        fmax = float('-inf')

muddlebee

def secondMax(nums):
        
        """
        :type num: List[string]
        
        """
        if len(nums) == 0:
            return -1
            
        fmax = float('-inf')