πŸ“š node [[2022 01 17]]

So I was thinking about the brief conversation we'd had about [[effective altruism]], and I started writing, and I wrote a lot, so my preamble is that I mean here to put words to a seed of a heuristic I'm working with, not just criticize. But I don't really have a clean phrase for the topic... so I'm tossing this in my daily note, and maybe it'll make sense to move later?

update: moved to [[criticism page]]


I don't know really how, but the absolute indignation in this captures something of the [[incrementalist's]] lament. Like, dang, y'all, the rest of the pie is right there.


Ordered this book of notebooks. It's shallow, but I do find the aesthetic of these things motivating.

[[2022-01-17]]

:PROPERTIES: :ID: 2cb450fc-ec6e-4cef-8df6-488f2a4030de

latency status quo is terrible - how can we do better?

https://danluu.com/input-lag/ what can force an improvement in experiences for most developers? not using javascript is a start, so is rust

lessons from phd

https://austinhenley.com/blog/lessonsfrommyphd.html#managers

  • lead or be led - actively advocate for yourself or you won't get what you want out of your experiences. you have far more information to determine how to prioritize than they do about you.

  • topic sentences. write the first for each paragraph, them flesh all of the bodies out.

  • managers are IO machines. your best use of them isn't to prove that you are productive; rather, it's to show up with something to answer questions and receive feedback

    • assume they forgot the last meeting

    • bring things to talk about and a goal

    • 3-4 sentences refreshing everyone

    • what did you do? what worked? what did not? what do you do next?

    • have something tangible - a demo or visual aid

  • daily progress tracking - a feq quick bullet points to summarize what you did that day, every day. trace progress towards goals!

πŸ“– stoas
β₯± context
β₯… related node [[2022 01 19 17 00 58]]