A Social Network is a scheme for studying the relationships and interactions amongst groups of people.

• people: \(V\)
• relationship: \(E\)
• system: a network \(G(V,E)\)

Importantly, the “labels” of \(E\) often do not matter as we frequently want to study only the graphical structure of the Social Network.

degree (node)

The degree of a node is the number of edges that are touching that node (whether in or out, or undirected).

The in-degree and out-degree are the number of edges touching that node (going in or out) respectively.

Key question: can multi-agent optimization problems help reinforcement learning stuff

using deep RL for combinatorial optimiazation

• fast inference scals well with instance size
• maybe difficult to actually discover optimal solution: high sample complexity, or failing to find good solutions
• doesn’t generalize well

why multi-agent works

• decentralized training to improve sample efficiency
• adversarial training

New Concepts

• Social Learning
• Multi-Agent RL
• Human-AI Coordination

Important Results / Claims

• When is AI Bad?
• Solution for Satelite Assignment Problem

Social Security Administration is a welfare program to directly give cash to those who are in need.

\begin{equation} softmax\qty(x_{i}) = \frac{\exp(x_{i})}{\sum_{j=1}^{n} \exp(x_{j})} \end{equation}

its “softmax”!

• max: amplifies the probability of the largest \(x_{i}\)
• soft: because it assign some probability to smaller \(x_{j}\) as well

:clap: What. Does. The. Client. Want.

Web Applications vs Local Application

• scale—what levels of functionality and access do we want
• training
• speed

SOLID principles

SOLID principles is a set of OOP principles; its kinda famous but encourages mindless braindead Java devs.

• Single Responsibility: that a class should have only one clearly defined thing it represents, and the class should only change IFF the underlying spec regarding that thing changes
  • Easy pitfalls: mixing PERSISTENCE LOGIC with BUSINESS LOGIC (db should be moved to a separate class like ThingProvider/ThingPersistence)
• Open-Close Principle: classes should be easily extendable and closed to modification
  • “we should be able to add new functionality without touching what’s written”
  • so like interfaces are nice
• Liskov Substitution Principle: subclasses should act like base classes (and more); good inheritance systems should have this built in
• Interface Segregation Principle: you should build lots of interfaces + sub-interfaces based on what clients are and will need, such that a client only has to extend precisely the amount needed to do their job
• Dependency Inversion Principle: when possible, depend on abstract classes or interfaces and not their implementations

Dependency Injection

“Dependency Injection” is a 25-dollar term for a 5-cent concept. […] Dependency injection means giving an object its instance variables. […].