How MrBeast learns
# forum
j
Pretty interesting, and good for making you feel like you've been wasting your life https://escapingflatland.substack.com/p/mrbeast
going to college remains my main regret in life so far
a
Jacob, this taps into a theme I'm planning to write about this year, pretty precisely. Thanks so much for posting this here.
oof, why?
j
looking forward to reading it!
you're gonna regret asking this, hold on while I write a mini essay haha
a
I will gladly attend your ted talk
l
Seconding the curiosity, since I suspect it might line up with my own regrets around going to college for CS
j
There are a few factors. probably the biggest one is just my personality/career path--I like working+learning independently. I've learned far faster from working on my own projects and reading books than I ever have in a classroom setting. (aside, I was also homeschooled, so that's how I was used to doing it until I got to college.) all the fake projects + homework + artificial deadlines + exams were just an impediment to learning imo. and since the workload is so high where was never any time for exploratory learning. it's like combining the worst of both worlds from work and school: you're basically in a production setting, doing mostly work, not learning, but the stuff you're producing is meaningless and you don't even get paid (the opposite in fact!) and the credential doesn't matter since I prefer to work as a founder/freelancer anyway. I spent more time getting my degree than I even spent working a job as a software engineer 🤦 I have sometimes wondered if part of my problem is that I went to a cheap school (byu) instead of a good school (university of Washington, since I'm from Washington, also it's like #4 for computer science apparently). I was trying to be frugal and stuff, but I wish someone had explained that software engineer interns get paid a lot and the internships you can get in Seattle (vs provo, lol) are probably more than enough to make up for the extra cost of tuition. though tbh my gut feeling is that I would've had the same beefs even if I went to UW. (to be continued, not done yet haha)
l
Wow, wasn’t aware that BYU had a ā€œcheapā€ reputation for CS. I went to Weber (another Utah one), which is 1000% a cheap commuter school that teaches the bare minimum to ship you off for Defense work, but had heard nothing but good things about BYU CS (other than the requisite trash-talking from all my University of Utah friends)
j
heh, it's relative I guess
byu cs is quite mediocre imo
a
The whole idea that one needs a CS degree has only come up in maybe the last 15 years or so? When I wrote about ageism, one of the people I talked to was an old boss who told me that the CS degree requirement was ageist, because back in the day there were very very few schools offering CS degrees.
My dad (now 90) was a programmer for his entire career (retired in the 1990s) and he and his peers did not have CS degrees. lol
Also back in the day, large companies trained liberal arts grads and people without degrees to be programmers.
l
based on my rough survey I’m pretty sure the only CS degree I might’ve liked was MIT circa 1980 (but my HS performance would’ve stopped me far short of Ivy League anyway)
a
(Or companies that bought IBM boxes also were trained by IBM)
l
I buy the ageism argument somewhat. A lot of the legends within CS are EEs or something else anyway (60% sure Rich Hickey is an EE or Music something-or-other)
a
Jacob, you probably would have loved college if you were my age -- it was before college was a sort of vocational track, right? You could kind of explore around. The vocational stuff was expected to happen at work. Sigh. I'm sorry.
I think there's also classism
When I worked at FNB Chicago (lol now part of chase) after college, I worked in a product area that I guess would be a "fintech" department today. So we had product people, bank client relationship people, and programmers. There was a whole group of programmers who were also musicians, many on the list for Chicago Symphony Orchestra auditions...sort of riding out the wait for CSO musicians to retire, and to see if they could make the cut.
l
Fascinating! I’ve wondered if the relationship between Programmers / Musicians was a coincidence or suggesting something Ć  la Graham’s ā€œHackers and Paintersā€. Although maybe I’m just looking for some company with my Sound Production Minor 🄲
a
We used to talk about it at the bank, I think programming is writing in another language; music is also code; instruments are machines lol. We're a musical family, and have had a number of programmers in the family...
But who knows?
l
I do want to throw out something based on the OP, though—I can tacitly agree that for the most part, reading/consuming/studying only the final product of successful examples and then relentlessly experimenting with mimicry is a fine way to learn something, and probably one of the shortest paths to success (where (= success money)). But something about that advice tastes funny. My example that might resonate with this crowd is that I don’t think anybody utilizing the MrBeastian (lol) approach would find Clojure or Vim or anything that deviates from the mainstream, and I guess I derive enough joy from using tools that I like that mainstream, billionaire success by doing the same things everyone else is doing seems sorta… unsatisfying. Even if you’re rich.
Now granted, I am the textbook example of the bikeshedding Emacs user, and certainly have fell victim to the ā€œsharpening the saw >>> shipping actual productā€ failure mode.
j
I played clarinet in orchestra šŸ˜‚ haven't had much time for it since having kids unfortunately (finishing up original comment) I did go to a community college during high school and get an AS degree, which I think was a pretty good experience. Washington has a program where you can do that in high school and the state will pay tuition, and then if you get the associates degree it comes with a high school diploma too. so were I to go back in time and give myself advice, I would've still done that, but instead of transferring to a 4-year college, immediately enter the workforce and try to start freelancing or something. maybe just get a plane ticket to SF and bum around till I found someone who'd hire me haha, and then go from there. I did enjoy the social aspects of college (I mean, I did meet my wife there), so maybe try to rent an apartment in a college town at least at the end of the day, at least I didn't spend a full 4 years at byu, and I didn't get a masters + take a bunch of student debt, so I try to not feel too bad for myself haha. and at least now that I've done the standard software engineer thing at least for a little bit I know it's not what I'm looking for [end rant]
that is an interesting point
maybe so! It does seem like college got corrupted a bit by trying be both vocational preparation and higher ed/lifelong ed/whatever it is college was originally supposed to be
re: ageism I guess it might depend a bit on if companies still strongly prefer candidates with cs degrees even if they have a lot of experience vs. being fresh grads--maybe they do. I think that's a thing at the big tech companies at least
l
My pet theory being that hiring fresh grads at insane salaries vs candidates with a proven work record is a major component of the twice-decade massive layoffs at Big Tech Companies
Well, that’s actually not a unique theory, and I think I learned all the evidence pointing towards that specifically from stuff I’ve found on Yakread 😬
j
idk, mrbeast seems to have taken a pretty non-mainstream career path the approach resonates with me thinking of it mainly in the sense of "learn by doing + taking in lots of raw inputs" rather than "learn by seeking out people's advice". I think there's been a fair amount of stuff written about tacit knowledge that's relevant. The other half of it is "if you're completely obsessed with something you'll probably get good at it" -- my hot take is that if you find that your obsessed with something, go for it; but probably a bad idea to try to mimic someone else's obsessiveness just for the sake of trying to be ambitious or whatever (I'm trying to make myself feel better about not having time to work more than 40 hours a week haha)
that sounds plausible
l
Ah, I can see it from that angle. The ā€œmimicking obsessivenessā€ reminds me of my maybe-all-time-favorite Substack article https://sashachapin.substack.com/p/if-you-have-writers-block-maybe-you
j
I'll give that a read! once I get out of surgery today (getting a cyst removed)
if you never hear from me again, then something went wrong with the surgery lol
l
don’t scare us like that šŸ’€
a
Feel better soon Jacob!
j
this was a good article, thanks for sharing
thanks!
while the topic is fresh on my mind, the bit that my internal therapist has figured out is that I'm sad about not being able to throw myself into my work as much as some people do, like mrbeast, because I have a family now--and while I don't regret that at all, I do regret that the phase in my life in which I did have time to work obsessively was spent on coursework. and that regret flares up every time the topic/argument of people-working-a-lot comes up, which incidentally has been a benefit of not using Twitter anymore haha anyway, I try to take my own advice of not worrying about stuff you can't change. but in thinking of how to productively channel that whole experience, it does motivate me to try to help build a better career path for other people. if either of my daughters want to do programming I can at least help them out šŸ™‚
OK, and digging deeper: maybe I need to come to terms with the reality that I am a "medium ambitious" person and not necessarily an "extremely ambitious" person as are celebrated in our culture though, hm... I'm not sure if that's the right framing. I consider myself highly ambitious, but I'm not really a short-bursts-of-high-intensity person. I'd rather work at medium-high intensity, but keep at it at a long time, which is a strength/liability that I do certainly have at least. (it was a liability when the thing I was keeping-at was a previous 4 year relationship lol). that's something I admire about research culture, in contrast to startup culture
l
that sort of feeling is basically why all the 37Signals books/writings resonate with me—the idea that software shops (and knowledge-work companies in general) should be built around profit at a sustainable pace, rather than the explosive high-income/high-debt crazy work schedules of startup founders like you’re saying
in a way, it does seem to me that the sexiness of Bay Area startup culture is generally losing its luster among the hacker community, but that may be temporary
j
Fantastic article, thanks for sharing! Bookmarking for easy access when I’m feeling unmotivated to write
j
#1081327074549174272 is a good post in that genre I read recently. I emailed the author and he said he's currently working on raising a fund and hoping to start doing investments sometime in Q2
(I survived the surgery BTW)
I wonder if the SVB thing will/has had an effect on that
a
Oh, good.
One of the things I appreciated about the article was his view that that he couldn't offer advice without really knowing someone and their context. (my paraphrasing.) I think he worked out how to align his actions/work style with his talents and inclinations. Other people could do exactly what he did, but not have the level of insight (or maybe luck or timing?) that enabled his success. Like, I could play chess for 18 hours a day for the next year, and might still be bad at chess.
j
Yeah, that's a good way to put it!
2 Views