https://www.youtube.com/watch?v=Wx_kugSemfY
Andrew Huang's video on the harmonic series does a really cool dive into this
HN user
https://www.youtube.com/watch?v=Wx_kugSemfY
Andrew Huang's video on the harmonic series does a really cool dive into this
The author wrote 'Writing an Interpreter in Go' for reference.
There's a lot of truth to this statement in my experience. I just finished rewriting my homework for my operating systems course and the first version looks awful compared to when I rewrote a chunk of it as a state machine
I took a course that used that textbook last semester and I got the international edition for around $30, and it was the exact same book with less problems.
Personally, changing my sleep schedule day to day almost never works. I usually end up going to bed and waking up about the same time regardless. Once I start waking up at 4am, I will always end up waking up at 4am.
My introduction to computing course had us read about the Therac-25 and write an essay about it.
While code we write doesn't always have such dire consequences, it was an eye opener to me as a freshman in college. It definitely made designing software/hardware to never fail have a much higher priority on my list of priorities.
Used this text for my Introduction to Proofs course I took this summer. Good quality text and exercises are pretty good.
I had a similar thing happen, where I had this insane aspiration of dual majoring in computer science and engineering and music. After doing marching band my first semester, which was 6+ hours of work a week ignoring games, and seeing how hard the music majors were working, I realized how difficult that'd be.
I still do the occasional ensemble, but the time you need to commit to those courses are insane.
I always use :x