svidovich

Before you run any of the test files, run chmod +x build_venv.sh && ./build_venv.sh to get all of the necessary packages in a virtual environment. Then, source venv/bin/activate to activate it.

svidovich

import random
import time


def generate_big_list(size) -> list:
    big_list = list()
    for _ in range(size):
        big_list.append(random.randint(1, size * 2))
    return big_list

svidovich

import random
import time

from typing import Tuple


def generate_big_list_and_big_set(size) -> Tuple[list, set]:
    big_list = list()
    big_set = set()
    for _ in range(size):

svidovich

import random
import time


def generate_big_list(size) -> list:
    big_list = list()
    for _ in range(size):
        big_list.append(random.randint(1, 100))
    return big_list

svidovich

import random
import time
from functools import lru_cache

def generate_big_tuple(size) -> tuple:
    big_list = list()
    for i in range(size):
        big_list.append(i * random.randint(1, 1000))
    return tuple(big_list)

svidovich

from typing import List

dartboard = [
    20,
    1,
    18,
    4,
    13,
    6,
    10,

svidovich

#!/usr/bin/env python3
import argparse
import csv
import datetime

import matplotlib.pyplot as plot

from typing import Dict, List

svidovich

You, too, can learn PySpark right on your Linux ( or other Docker-compatible ) Desktop with a few short, easy steps!

Before we begin, make sure you have docker installed. Here's the official documentation: https://docs.docker.com/get-docker/

Got that done? Good! Let's get started.

First let's get our bashrc set up so that we can just use a command instead of remembering complicated docker flags. Nobody likes those.

echo 'alias pyspark-jupyter="docker run -it --rm -p 8888:8888 jupyter/pyspark-notebook"' >> ~/.bashrc

svidovich

THIS IS A UTILITY FOR GETTING PRODUCT KEYS FROM REGISTRY FILES ON A COMPUTER THAT DOES NOT RUN, NOT FROM A RUNNING MACHINE

Recently, a friend of mine was building a computer and had lost his product key. He couldn't boot the old computer, but his partitions were intact.

So, I went searching for a way to pull the registry keys from the partition so I could get his keys back. He had tried produkey, etc. but I thought I could give it another shot.

He zipped up his C:\Windows\system32\config folder and sent it to me, so I grepped around looking for product keys. As it would turn out, they generally live in a file aptly called SOFTWARE.

I wandered around looking for tools and found one that could decrypt keys, but not one that could open just... files. So, I found a library called python-registry that could open up files, and from there it was pretty simple.

svidovich

W/ David Black-Schaffer

See https://www.youtube.com/watch?v=V4RfPfHQPC8&list=PLiwt1iVUib9s6vyEqdpcgAq7NBRlp9mAY

OpenCL is:

• Low Level
• High-Performance ( HW dependant )
• Data-Parallel ( A kind of parallelism )

It lets you access all of the system compute devices. It's based on C99, which is sad.