"someone please..."

"...please..."

"...please review my code"

Watching a video is like skimming the material where by the end, you'll know where it's all headed and the mind is already working on recognizing the independent points of agency, a traversal in the graph if you will.

Then as a second pass, slowing re-reading the transcript to help the mind affirm/reaffirm or even break assumptions, is gonna have a lasting impact in the learning process.

This explains why I remember random lore/moments in stories I adore. Watch something end to end and then meticulously revisit parts with a new perspective (akin to multimodal recall).

Inspired by this wonderful piece of writing: https://cse.buffalo.edu/~rapaport/howtostudy.htm

I might have to experiment with daily setup and teardown rituals because mission critical work can be energy draining.

i wrote myself a neovim command and a keybinding on top of that to help me save and push the current file to remote git branch.

If I want to quickly save current file and push to remote all i need to do it

The Pen Is Mightier Than the Keyboard by Mueller and Oppenheimer found that students who took handwritten notes retained concepts better than those who typed them.

Taking notes in your own words along with verbatim (quotes) and can help later validate and rethink your assumptions.

Hand writing in your own words + digital / analog verbatim transcribing i feel is in line with the Lollapalooza[^1]

[^1]: "Lollapalooza effect: Munger used the term "Lollapalooza effect" for multiple biases, tendencies or mental models acting in compound with each other at the same time in the same direction. With the Lollapalooza effect, itself a mental model, the result is often extreme, due to the confluence of the mental models, biases or tendencies acting together, greatly increasing the likelihood of acting irrationally" ~ via wikipedia

I wanted to improve my code review capability and I found this blog post useful!

so sharing it here just because:

https://consulting.drmaciver.com/code-review-quick-fixes/

Rosetta 2 creator on efficiency:

Q(zmb_ ): [...]As someone frustrated in a team of 10+ that is struggling to ship even seemingly trivial things due to processes and overheads and inefficiencies, I would really appreciate some insights on how do you organize the work to allow a single developer to achieve this.

A(cwzwarich): Well, the first thing to realize about scaling codebases with developers is that an N developer team will usually produce a codebase that requires N developers to maintain. So by starting small and staying small until you reach a certain critical mass of fundamental decisions, you can avoid some of the problems that you get from having too many developers too early. You can easily also fall into the reverse trap: a historical core with pieces that fit too well together, but most of the developers on the team don’t intuitively understand the reasons behind all of the past decisions (because they weren’t there when they happened). This can lead to poorly affixed additions to a system in response to new features or requirements.

As far as Rosetta in particular was concerned, I think I was just in the right environment to consistently be in a flow state. I have had fleeting moments of depression upon the realization that I will probably never be this productive for an extended period of time ever again.

sourced via comments to the HN post Rosetta 2 creator leaves Apple to work on Lean full-time

I rewatched Manchester by the Sea last night.

Casey Affleck really did a phenomenal job portraying unease and depression but Michelle Williams stole every scene she was in.

Moreover what kept me fascinated was the portrayal of climate/weather metaphorically and literally carrying the emotional journey and plot respectively.

The latter which is something that stood out to me because I've been dabbling with such metaphors in a story I've been brewing in my head.

I've been doing this fun thing lately.

Whenever I recall a concept that is practically not relevant to what I'm doing in my daily life (you can call me a normie) and I wanna see how people are dealing with said concept in their daily lives, I do this simple trick.

I search site:news.ycombinator.com {{concept}} on google and honestly I'm not disappointed. Instant rabbit hole material.

all this given that I have time to kill :P

Excerpts from "The Shape of the Essay Field" https://paulgraham.com/field.html

So the three reasons readers might not already know what you tell them are (a) that it's not important, (b) that they're obtuse, or (c) that they're inexperienced.

so by implication,

If you're writing for smart people about important things, you're writing for the young.

Now that I know it, should I change anything? I don't think so. In fact seeing the shape of the field that writers work in has reminded me that I'm not optimizing for returns in it. I'm not trying to surprise readers of any particular age; I'm trying to surprise myself.