dhouston
Joined 19 years ago
Joined 19 years ago
And not just C but Linux (Slackware!), sockets, even kludging the single-player DOS port to be two-player by playing over a serial cable to another PC. And annoying my future Dropbox teammates by including an extra space after/before parens in function calls (and if/for/switch statements), putting { on its own line, etc as was the convention in that code base IIRC.
A single A100 or H100 with 80GB VRAM can fine tune 70B open models (and obviously scaling out to many nodes/GPUs is faster, or can use much cheaper GPUs for fine tuning smaller models.)
The localllama Reddit sub at https://www.reddit.com/r/LocalLLaMA/ is also an awesome community for the GPU poor :)
(I don't know Matt, and haven't been coached by him, but I do know a lot of the founders he's coached, and have read his book https://www.amazon.com/Great-CEO-Within-Tactical-Building-eb... which covers much of the same material.)
Remote-only cuts out the in-person experience entirely, which is problematic for building teams and culture; and ad hoc "WFH whenever you feel like it" gets a sort of worst-of-both-worlds situation where you neither get the same kind of flexibility nor the sense of community you typically get from an office (since a large percentage of the team isn't there on any given day, and folks that come in the office less tend to be at a disadvantage in terms of visibility & recognition).
The basic principle of HOM is that the fundamental job of an executive is to deliver results ("output"), and that the measure of an executive is the output of their organization. Importantly, there is no one right way to deliver results -- successful CEOs can have very different styles and techniques.
That said, for every effective way to deliver results there are vastly more that are ineffective. Complexity, ambiguity, and uncertainty are not your friends. Time is not your friend. Everything is situationally dependent. There are many skills to develop and principles that can help but there's no formula.
This also partially explains why the median CEO or exec is perceived as ineffective, often because they are. It's a hard job, otherwise everyone would do it well and there would be a surplus of good (and cheap) execs.
Contrary to what the post suggests, HOM does not say not that the job of an executive is to wave some kind of magic culture or "values" wand and rubber-stamp whatever emergent strategy and behavior results from that. CEOs and executives absolutely do (and must) make important decisions of all kinds, break ties, and set general direction. Occasionally they need to give commands but more typically you work collaboratively with and (as the post correctly suggests) empower your team and avoid doing too much as an individual contributor.
If you're curious about what execs do and how to be a good one, HOM is an incredible book. The Effective Executive by Drucker is another favorite.
https://hbr.org/2009/05/what-only-the-ceo-can-do is one of my favorite articles about the responsibilities of the CEO.
https://hbr.org/2018/07/the-leaders-calendar is a fascinating study of where CEOs spend their time and what they actually do day to day.
And thank you HN — I’m pretty sure the upvotes on the original screencast helped us get into YC and on Paul & Jessica’s radar to begin with!
Even you BrandonM — https://news.ycombinator.com/item?id=9224 — my favorite HN comment thread of all time :)
(actually, come work on it: https://www.dropbox.com/jobs :))