Skip to content

Instantly share code, notes, and snippets.

View eliekawerk's full-sized avatar

Elie Kawerk eliekawerk

View GitHub Profile
@eliekawerk
eliekawerk / normcore-llm.md
Created August 23, 2023 12:57 — forked from veekaybee/normcore-llm.md
Normcore LLM Reads
@eliekawerk
eliekawerk / pyro_logistic_regression.ipynb
Created May 18, 2023 19:16 — forked from jamestwebber/pyro_logistic_regression.ipynb
A iPython notebook showing how to use SVI for logistic regression in Pyro
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@eliekawerk
eliekawerk / grokking_to_leetcode.md
Created May 5, 2022 09:16 — forked from tykurtz/grokking_to_leetcode.md
Grokking the coding interview equivalent leetcode problems

GROKKING NOTES

I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.

So below I made a list of leetcode problems that are as close to grokking problems as possible.

Pattern: Sliding Window

with
dau as (
-- This part of the query can be pretty much anything.
-- The only requirement is that it have three columns:
-- dt, user_id, inc_amt
-- Where dt is a date and user_id is some unique identifier for a user.
-- Each dt-user_id pair should be unique in this table.
-- inc_amt represents the amount of value that this user created on dt.
-- The most common case is
-- inc_amt = incremental revenue from the user on dt
@eliekawerk
eliekawerk / Dockerfile
Created June 28, 2020 12:29 — forked from igjit/Dockerfile
Use reticulate with pyenv
# https://github.com/rocker-org/rocker/tree/master/r-ubuntu
FROM rocker/r-ubuntu:18.04
RUN apt update && \
apt install -y \
make build-essential libssl-dev zlib1g-dev libbz2-dev \
libreadline-dev libsqlite3-dev wget curl llvm libncurses5-dev libncursesw5-dev \
xz-utils tk-dev libffi-dev liblzma-dev python-openssl git
RUN curl -L https://github.com/pyenv/pyenv-installer/raw/master/bin/pyenv-installer | bash && \

FXCM Webinar

Algo Trading: REST API & Python Wrapper

Tick Data, Historical Data, Real-Time Data, Backtesting, Orders

Dr. Yves J. Hilpisch | The Python Quants GmbH

Online, 04. April 2018

Executive Program in Algorithmic Trading (QuantInsti)

Python Sessions by Dr. Yves J. Hilpisch | The Python Quants GmbH

Online, 07. & 08. April 2018

Market-Based Valuation of Equity Options

CQF Lecture, 09. April 2018, London

Dr. Yves J. Hilpisch, The Python Quants GmbH

Resources

@eliekawerk
eliekawerk / clean_code.md
Created September 3, 2018 07:02 — forked from wojteklu/clean_code.md
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules