Home Archives Search Feed

11-23-2022

Outcomes

Summary

Notes

  • #projects idea:
    • Make a script that can output a list of all the Zettel notes that I edited on a given day, which I can then paste in the journal of a given day.
    • Update: done!

uid: 202211230801 tags: #journal

February 22, 2023

Empower Yourself In Every Situation

Source: https://app.sparkmailapp.com/web-share/XOuIy-7AnL5wUZ-sMX5VXsFY1KoJ0B7okfhIrbZa

Without altering the facts of the situation I am facing and without ignoring the reality of what must be done, what is the most useful and empowering story I can tell myself about what is happening and what I need to do next?

10-25-22: I am feeling socially down (feeling like I’ve been very anti-social at work, feeling down about it, haven’t had food with people at lunch, feels like people haven’t been texting me or even really care about me). Also feels like I haven’t been working out much. Given this situation, what’s the best way forward for me? Facts: If I want the gen z Airtable people to like me, that means I need to put in more effort (even when I might not be feeling like it, or it might feel awkward). This means that I need to sit with people at lunch. When I pass by people, I should say hi to them. I should take opportunities to say hi to people. I should text people to catch up with them. I should also work on getting better at conversation / social stuff if I’m unsure about it.

uid: 202210241004 tags: #productivity #quotes

February 22, 2023

Searching For Things In Your PKM Should Be Like Kibana

TODO: Write this post using the why/what/how framework 202210042153 Why:

  • Being able to search things effectively is one of the most important ways to reflect on your ideas and create new insights from your notes, which is one of the fundamental components of a Zettelkasten. I’ve already talked about the value of using search history to understand your browsing patterns (and by extension, your interests) here: Search history is observability for web browsing 202204062059. Just as important is being able to search for stuff within your own notes. What: While searching, you should be able to narrow down what you’re looking for easily. Having a query language is very important for that.

How: Something I really like about kibana: it shows available tags in an already filtered query, allowing you to easily further filter your query.

How to Write Better with The Why, What, How Framework 202210042153

If your notes have a pre-determined schema to them 202207051412, then this is even better. You can search for things like

include this, but not that, and only some of these

And also easily visualize specific attributes about the notes that you want to see.

Tangent 202207051621 is attempting to do something like this with its query syntax:

#update 01-29-23: I update

uid: 202210042306 tags: #blog-ideas #notetaking

February 22, 2023

# How to Write Better with The Why, What, How Framework

source: https://eugeneyan.com/writing/writing-docs-why-what-how/ tags: #literature #writing #advice #howto uid: 202210042153 —

^ See the article itself as an example of this template.

Why: Start by explaining Why the document is important. This is often framed around the problem or opportunity we want to address, and the expected benefits. We might also answer the question of Why now?

Think of this as the hook for your document. After reading the Why, readers should feel compelled to blaze through the rest of your doc

What: After the audience is convinced we should solve the problem, share what a good solution looks like.

Together, they enable readers to evaluate and decide on proposals, make trade-offs, and provide feedback.

Another way of framing What is via requirements. Business requirements specify the expected customer experience, uplift to business metrics (success measures), and budget (constraints). They might also be framed as product or functional requirements. Technical requirements specify throughput, latency, security, privacy, etc., usually as constraints.

What should give the reader context on the problem / issue at hand / whatever the thing is trying to solve. Tell the reader what a good version of the solution that your thing is trying to solve looks like.

How: Finally, explain How you’ll achieve the Why and What. This includes methodology, high-level design, tech decisions, etc. It’s also useful to add how you’re not implementing it (i.e., out of scope).

February 22, 2023

Reflections On Debugging With Mulan

Last night, I spent ~4-5 hours trying to debug this nasty bug with Mulan. We weren’t able to figure out exactly why the issue is happening, but I had some interesting takeaways after the fact.

  1. Mulan and I work really well as a team, if we make sure that both of us are in the right mindset. If we’re both on the same page, then it’s game over.
  2. Mulan is very insightful, and often points out things during debugging that other people miss. Some of her weaknesses include implementation keeping track of things in her head. Some reasons why these could happen (from mulan herself):
    • shorter attention span
    • doesn’t feel as clear about solutions
    • doesn’t enjoy as much as me
  3. Mindset matters a lot.
  4. Having your work setup be shitty affects your rate of iteration so much. Mulan’s setup with her laptop is soooo slow, but I don’t think she even realized how much she was missing out on by not having a faster laptop. I guess this is in favor of investing the time to find a setup that works really well for you. There’s quite a lot of investment cost, but you definitely make up for it by just being 20-30% faster than other people at basic ass things. Although there’s a limit to how much the incremental improvement actually helps; at some point, you need to just make sure you’re prioritizing more important things 202210031316

uid: 202210031304 tags: #self-reflection #relationships

February 22, 2023

Error Injection Pr

Goals:

  • find the minimum set of shard assignments that must have resilient behavior for shard assignments callsites to work end to end.
  • guard against regressions for CRUD requests that are known to work correctly given current resiliency protocols.
  • Make slight augmentations to our resiliency job to allow verifying resiliency for only a subset of all MySQL main queries.

TODOs:

  • figure out how to make the shard assignments runner a variant of the existing runner.

PR chain -> live shard helper refactoring — withCompositeConnectionAsMainConnectionAsync becoming object, and scanShardsForObjectAsync having a callsite -> resiliency runner with:

  1. new queryHashesToForceInject field
  2. New beforeEach and afterEach, where we’re doing only shard assignments setup
  3. New crud requests that will run in all environments — do this first, make sure that existing tests work.
  4. Uncomment out the “only some processes tests”
  5. Add comments about the weirdness for certain things — Need to add a new crud request end-point for helper

Things to talk about with Keunwoo –

  1. Things like row comment notification renderer

uid: 202208291247 tags: #airtable

February 22, 2023