gladiatorAsh

        private static void Measure(string what, int reps, Action action){
            action(); //Warmup

            double[] results=new double[reps];

            for(int i=0;i<reps;i++){
                StopWatch sw= StopWatch.StartNew();
                action();
                results[i]=sw.Elapsed.TotalMilliseconds;
            }

gladiatorAsh

1. String equals vs ==
public static void main(String[] args)
  {
    
    System.out.println("abc"=="abc");
    System.out.println("abc".equals("abc"));
    OtherClass my1=new OtherClass("Hello");
    OtherClass my2=new OtherClass("Hello");
    System.out.println(my1==my2);
    System.out.println(my1.equals(my2));

gladiatorAsh

Docker: Images and Containers: Runtime instance of an image Kitematic

Containers and VMs: On Linux, containers run natively and shares the same kernel as OS. Runs a discrete process and is lightweight. VM runs a separate guest OS with access to resources through a hypervisor. 

Containerization because:
1.	Flexible: Most complex apps
2.	Interchangeable: Deployment on the fly
3.	Portable: Build locally, deploy and run anywhere 
4.	No installation needed except docker
5.	Lightweight, makes CI/CD seamless. Dependency management becomes seamless.

gladiatorAsh

Deploy to AWS (For Windows)

Tools

1. RoboMongo (For testing Mongo DB
2. Kitematic (for easy containers)
3. WinSCP (transfering files)
4. Postman (For Testing API)
5. Cygwin (For easy terminals)

Libraries

1. helmet (for security)

gladiatorAsh

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?

gladiatorAsh

Demo: Coordinating async React with non-React views

tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.

A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.

But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.

How do we solve this with React?

gladiatorAsh

I bundled these up into groups and wrote some thoughts about why I ask them!

If these helped you, I'd love to hear about it!! I'm on twitter @cvitullo or send me an email [email protected]

Onboarding and the workplace

https://medium.com/@cvitullo/questions-to-ask-your-interviewer-82a26e67ce6c

• How long will it take to deploy my first change? To become productive? To understand the codebase?
• What kind of equipment will I be provided? Will the company pay/reimburse me if I want something specific?

gladiatorAsh

A top-level App component returns <Button /> from its render() method.

1. What is the relationship between <Button /> and this in that Button’s render()?

2. Does rendering <Button><Icon /></Button> guarantee that an Icon mounts?

3. Can the App change anything in the Button output? What and how?

---

gladiatorAsh

FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.

---

Effective Engineer - Notes

• By Edmond Lau
• Highly Recommended 👍
• http://www.theeffectiveengineer.com/

What's an Effective Engineer?

gladiatorAsh

The Beginning

Yes...it's true...redux is smart....smarter than you even know. It really does want to help you. It strives to be sane and easy to reason about. With that being said, redux gives you optimizations for free that you probably were completely unaware of.

connect()

connect is the most important thing in redux land IMO. This is where you tie the not between redux and your underlying components. You usually take state and propogate it down your component hiearchy in the form of props. From there, presentational