Live data from Hacker News

Ask HN: Stanford CS 153 help

news.ycombinator.com

11–20 of 34 posts

Re: Ask HN: Stanford CS 153 help

#12
couldn't find the syllabus

deploy something like cassandra and make a system that can update the kernel on the servers running the databases without downtime or losing data

or come up with some distrubuted blob store thing/cdn for world wide users

my whole career has been automating updates for software or operating systems lol

Re: Ask HN: Stanford CS 153 help

#14
Rachel by the Bay (https://rachelbythebay.com/) has long impressed me as someone who clearly is deep in the actual work of systems, day in and day out, and can write well about it.

Julia Evans has a wonderful approach as well, and has amazing talent for teaching: https://jvns.ca/

Kellan Elliott-McCrea (https://laughingmeme.org/) has given the world some of the better advice on the hardest parts of software scaling, which is of course scaling the human organizations. New grads are virtually always underestimating that part of the work; eventually you realize the hard problems are usually social and not technical.

Re: Ask HN: Stanford CS 153 help

#17

Rachel by the Bay ( https://rachelbythebay.com/ ) has long impressed me as someone who clearly is deep in the actual work of systems, day in and day out, and can write well about it. Julia Evans has a wonderful approach as well, and has amazing talent for teaching: https://jvns.ca/ Kellan Elliott-McCrea ( https://laughingmeme.org/ ) has given the world some of the better advice on the hardest parts of software scalin…

i've followed Rachel and Julia for a long time, but didn't know about Kellan - thanks so much for that.

re: human org scaling - true and this was the most surprising thing for me when i was running the platform org at discord. companies ship their org charts whether they like it or not. and refactoring org charts correctly, at scale, is essentially untested in the modern era

Re: Ask HN: Stanford CS 153 help

#19
post #10

A progression of projects that comes to mind: 1) CI and IAC that deploy a web app running in a container 2) Add horizontal scaling and load balancer 3) Add long running tasks / scheduled task support 4) Deploys will likely break long running tasks. Implement blue/green or rolling deploys or some other sort of advanced deployment scheme 5) Implement rollbacks

Love this. Easy to Advanced, with 5 for extra credit. Thank you
Post reply on HN