Skip to content

Instantly share code, notes, and snippets.

View benguillet's full-sized avatar

Ben Guillet benguillet

View GitHub Profile
@ChuckM
ChuckM / farewell.md
Last active June 7, 2021 18:21
On my departure (fictional)

Dear non-executive team members,

All of my options have vested, and I haven’t been offered any new ones so my earning potential here is no longer all that great. Worse, as we’ve operated and developed better understandings of the problems we face it seems less likely than ever that we’ll achieve the vision we set out to achieve. Finally, the blackout periods are having a real negative effect on my ability to diversify my wealth and avoid the high risk of this company’s success chances. Therefore I’m leaving on a “high note” while we can still plausibly call this endeavor a success, and after I’ve left will convert all my equity in this venture into other forms of wealth while not having to report it

@clarkdave
clarkdave / ecs-interactive-console.sh
Last active January 31, 2023 19:26
ecs-interactive-console
#!/bin/bash -e
##
# Use this annotated script a base for launching an interactive console task on Amazon ECS
#
# more info: https://engineering.loyaltylion.com/running-an-interactive-console-on-amazon-ecs-c692f321b14d
#
# Requirements:
# - `jq` must be installed on both the client and server
##
@yossorion
yossorion / what-i-wish-id-known-about-equity-before-joining-a-unicorn.md
Last active April 7, 2024 22:55
What I Wish I'd Known About Equity Before Joining A Unicorn

What I Wish I'd Known About Equity Before Joining A Unicorn

Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.

This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would

@rgabo
rgabo / empire_vs_elastic_beanstalk.md
Last active December 4, 2015 17:26
Empire vs Elastic Beanstalk

Reasons why we did not go with Elastic Beanstalk

tldr;

Elastic Beanstalk with Docker is great at having a standard way of running and scaling out web and worker applications, if you are OK with AWS abstractions and further lock-in. For instance, auto-scaling web apps using autoscaling group policies is extremely powerful, but I believe there is a lot of accidental complexity that comes with Elastic Beanstalk so we chose something that we believe is simpler and easier to understand or change.

not so tldr;

  1. AWS is great at taking an existing technology, wrapping it into AWS-specific concepts and creating a proprietary JSON/XML API around it. This is why ECS Task Definitions exist. Elastic Beanstalk goes one step further and creates yet another layer of API on top of ECS and ELB aptly called Dockerrun.aws.json v2. The format is proprietary and we preferred ex
@jboner
jboner / latency.txt
Last active May 5, 2024 03:12
Latency Numbers Every Programmer Should Know
Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference 0.5 ns
Branch mispredict 5 ns
L2 cache reference 7 ns 14x L1 cache
Mutex lock/unlock 25 ns
Main memory reference 100 ns 20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy 3,000 ns 3 us
Send 1K bytes over 1 Gbps network 10,000 ns 10 us
Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD