网络上看过的精彩讲座/课程/录像/视频等:

A Philosophy of Software Design | John Ousterhout | Talks at Google

Jul 15

A Philosophy of Software Design | John Ousterhout | Talks at Google

John Ousterhout, Professor of Computer Science at Stanford University, discusses complex techniques on how to become a more confident coder. John is excited to announce that he just published the first edition of a new book on software design, based on material from a software design class he has been teaching at Stanford for the last several years.

Prior to joining Stanford, John spent 14 years in industry where he founded two companies, preceded by another 14 years as a professor at Berkeley. Over the course of his career, Professor Ousterhout has built a number of influential systems (Sprite OS, Tcl.Tk, log structured file systems, Raft, RAMcloud, etc) and has taught several courses on software design. In this talk, he synthesizes these experiences into an insightful and provocative discussion on how to (and how not to) design software.

老教授太幽默了,看视频的过程中真的会笑出声来🤣,尤其是他的举例和模仿自己学生抱怨写单元测试和文档的语调,太有趣了。

一些摘抄:

We will invest in good design today because most of the code we develop today is going to be in the future. And so if we mess things up today, we are slowing ourselves down for the future.

Raft

Aug 11

关于Raft的可视化网页:Raft: Understandable Distributed Consensus

Project Code Rush - The Beginnings of Netscape / Mozilla Documentary

Oct 15

Project Code Rush - The Beginnings of Netscape / Mozilla Documentary

There’s no stability in here. So the very kind of weird irony is that very people who are inventing the future can’t see their own future.

耳目一新的论点。

终于看完了这个很久之前就想看的纪录片👏。

John Carmack Receives Honorary Degree

John Carmack Receives Honorary Degree

Oct 16

忙了一天,早上被系统环境问题折磨,下午画UML图按触摸板按得手疼🙃(尽管Mac触摸板很好用)。最近一直盯着电脑敲键盘,慢慢会习惯这种强度吧,毕竟发现也是自己想要做的事情。

晚上休息看了John Carmack的这个视频,本来想浅浅记录下一些句子,没想到自己跟着视频一个字符一个单词地敲了这么多。很多话真的是莫大的鼓励,就在想,很多东西到底需要重复多少遍才可以轻而易举呢?

So almost everything that we work with has really great depths to explore. Now you can’t know everything, but you should look at this as you can know anything, anything that you turn your attention to, you choose to focus on, you can understand nothing is magic and you can tear things apart if you need to find the details.

Now knowing all the details can have some consequences because sometimes the details are really ugly or even frightening to think about and this can lead to people thinking: no, things aren’t awesome, they’re actually horrible if you look at it.

I take the more optimistic view that this means that’s tons of opportunities, especially with the exponential growth of Moore’s law slowing down. Being able to dig deep into our systems and find efficiencies there is one of the ways that we can continue delivering significant value.

5年前上传的视频。不知道是自己长大了还是时代真的变了,疫情核酸裁员就业难,仿佛是最坏的时代。但“危机”,有‘危“才有”机“,代表着更多的机会。

Now to really understand the details you have to understand history. Many times things are the way they are for important and valid historical reasons but sometimes things are the way they are because we didn’t know any better or because we didn’t have time to actually make something good.

有意思的观点,所以计算机也有必要了解历史?一门课程一本书刚开始都会讲历史,也看过一些计算机相关历史发展的书籍,但大部分都是美国人发明的倒是真的😮‍💨。

(这边英文实在没精力写啦)作者不鼓励重复造轮子,但是尝试去做或许会造出更好的轮子。

Whatever path you’re on, I advocate for long, hard work. You hear a lot about work-life balance, working smarter not harder and that’s all fine but there’s a quality to obsession that’s really hard to match any other way.

Sometimes important insights come only from a total immersion in a problem or fileld and even when the work is mundane there’s value that you can extract from that.

Mastery comes from practice.

I urge you to embrace the grind.Pay attention to the details, fill your products would give a damn. You’re building the future.