Home Archives Search Feed

# Build your metadata library

source: https://ift.tt/xICYSLb tags: #literature #northstar #projects #productivity uid: 202301291444 —

Tracking these activities has served as a helpful reference for when a friend asks me what I’ve read lately or for a good recipe. Everything is in one place. I was also surprised to learn that I made 96 new recipes last year, a number I wouldn’t have known, or even been able to guess, had I not tracked.

I want to do this - tracking the projects I’m working on and the hobbies I’m working on as a means to reward myself for doing them. This is absolutely something I want to prioritize this year.

Over the years, I tried to make tracking frictionless and rewarding. Each costs me seconds of my time or is fully automated:

This is my dream! I tried to do this with blogging, but it wasn’t frictionless enough. I definitely want to use this website as a reference for triggering these automations for myself. In fact, I could do this with the articles I read! And exporting my highlights #todo

I have found this iOS shortcut to GitHub issue pipeline to be ideal for data that doesn’t have an API, for when I want to pull data from many sources, and for activities I complete on or near my phone. I also like to avoid added logins. For example, while Goodreads is a known service to track books, it’s more than I want.

My private data repository builds a public site. I mentioned earlier that I tried to make the process of tracking rewarding — this site is it. Like checking something off a checklist, I have found a sense of accomplishment that makes me want to continue, to do more, to read more, to try a new recipe.

I think this would be me too. I’m glad I recognized this. Currently, I have a bunch of different source for tracking information - my own script for Things 3, Pinboard for articles, Goodreads for books, other random scripts for my personal notes, Fitbod for workouts, etc, but nothing that’s centralized. I tried out exist.io earlier because I was very intrigued by the centralization of it, but turns out it just didn’t work for me.

February 22, 2023

# Why and how to write things on the Internet

source: https://ift.tt/s3DeLnq tags: #literature #inbox uid: 202301152336 —

In my opinion, the strongest reason for any random person to start a blog is that you will have more awesome friendships—both in the sense that you will meet new awesome people as a result of your blog, but also in the sense that writing will cause you to have more interesting ideas, which will make your existing friendships more awesome because you’ll have better stuff to talk about.

Write to make stronger friendships 202301012159

Most people dramatically underestimate the impact that their writing has on others.

So: lower your bar for what’s worth writing about! My personal standard is anything that I’ve said more than once in a conversation.

Note from Jeff:

There is a tradeoff here, though: my signal to noise ratio is low enough that many people ignore all my posts even though if I only published the best 5% of them they’d happily read them. Except, at least for me, this isn’t a real tradeoff: I’m not able to just write the 5% of posts that will be the best. When I try I end up just not publishing anything for months. I wrote about this some a few years ago: https://www.jefftk.com/p/blogging-thresholds

Here are my top two pieces of advice for writing things on the internet:

Publish consistently.

Notice and pay attention to feedback.

In fact, my suggestion is to make all your writing-related choices to optimize for this. If something seems like a good idea in principle, but would make it harder for you to write consistently or slower to get feedback, don’t do it.

Finally, blog posts are one of the ultimate examples of searching for outliers—the best ones are massively better than the average. And one of the best ways to improve your chances of getting an outlier is just to take lots of shots on goal.

This is why you should build a consistent writing habit.

The most important thing here is to write about whatever you’re most excited to write about (n.b. not what you think you should be most excited to write about, or what you’re most excited to have written about), since this is the most likely to generate consistent output.

February 22, 2023

Access policy sketch notes

Look at public API access middleware

Harden the access policy authorization calls main

Understand how main is used for access policy getValidatedAccessPolicyIfPolicyStringIsValidAndIsAuthorizedAsync

Do we need a flag like api access middleware? Everything you can share externally is based on access policy

Maybe we can deprecate this for internal requests (not going to do this right now)

Use cases: Shares, workflows, blocks, syncs

Generation side

Things that need to be

uid: 202212201536 tags: #airtable

February 22, 2023

ordinary claims require ordinary evidence

In the context of Bayes 202212092211 One contributed example:

A few years back, a senior person at my workplace told me that a new employee wasn’t getting his work done on time, and that she’d had to micromanage him to get any work out of him at all. This was an unpleasant fact for a number of reasons; I’d liked the guy, and I’d advocated for hiring him to our Board of Directors just a few weeks earlier (which is why the senior manager was talking to me). I could have demanded more evidence, I could have demanded that we give him more time to work out, I could have demanded a videotape and signed affidavits… but a new employee not working out, just isn’t that improbable. Could I have named the exact prior odds of an employee not working out, could I have said how much more likely I was to hear that exact report of a long-term-bad employee than a long-term-good employee? No, but ‘somebody hires the wrong person’ happens all the time, and I’d seen it happen before. It wasn’t an extraordinary claim, and I wasn’t licensed to ask for extraordinary evidence. To put numbers on it, I thought the proportion of bad to good employees was on the order of 1 : 4 at the time, and the likelihood ratio for the manager’s report seemed more like 10 : 1.

uid: 202212092359 tags: #insights

February 22, 2023

Zookeeper

Often described as a “distributed key-value store”.

Why does zookeeper use a fault-tolerant consensus 202211232125 algorithm under the hood?

NOTE: People usually don’t Zookeeper directly. It’s often used by some other service, e.g., HBase, Hadoop YARN, OpenStack Nova, and Kafka.

Zookeeper is designed to hold small amounts of data that can entirely fit in memory (although they still write to disk for durability). That small amount of data is replicated across all nodes using a fault-tolerant total order broadcast 202211232155 algorithm. (Total order broadcast keeps replicas consistent with each other.)

Answer to the question above: Zookeeper has the following attractive features.

  1. Linearizable atomic operations
    • Using atomic compare-and-set, you can implement a lock: if several nodes concurrently try to perform the same operation, only one will succeed. The consensus protocol ensures that the operation will be atomic and linearizable, even if a node fails or the network is interrupted.
  2. Total ordering of operations, which serves as a fencing token 202211232306 to prevent clients from conflicting with each other in the case of a process pause.
  3. Failure detection
    • Clients and the server periodically exchange heartbeats to ensure that the other node is still alive.
    • Locks by a session can be configured to be automatically released when the session times out. (These are called ephemeral nodes 202211232312)
  5. Change notifications
    • Not only can one client can read locks and values that were created by another client, but it can also watch them for changes.

Several people have suggested using zookeeper as a service for shard assignments 202211232309

Created from: Raft & Paxos 202211231100

uid: 202211232246 tags: #software-engineering #algorithms #distributed-systems

February 22, 2023

202210261919 cool gray city of love

Things to look at later:

  1. Land’s End photos
  2. Tamales Bay
  3. How the Bay Area faults work - San Andreas in relation to the other ones.
  4. point San Pedro
  5. Montara mountain
  6. mount Davidson
  7. mile rock
  8. yerba Buena - Anchorage
  9. check out Russian hill and telegraph hill more
  10. fort funston
  11. Larsen peak
  12. cliff house
  13. sro hotels
  14. legion of honor
  15. aquatic park
  16. memorize San Francisco streets - spaced repetition
  17. tiburon
  18. filbert steps
  19. look up the post about steps in San Francisco
  20. drakes bay
  21. isle of the dead
  22. women atop the colonnade at the palace of fine arts
  23. lobos creek
  24. mission bay estuary
  25. mission Dolores building
  26. year zero pol pot
  27. Les halles
  28. ipanema
  29. copacabana
  30. waikiki
  31. point lobos
  32. go to Buena Vista park!
  33. El polin spring
  34. adobe material
  35. India basin
  36. Bayshore fwy
  37. Huntington park
  38. larsen peak
  39. mount davidson
  40. fort funston
  41. mount San bruno
  42. Bayview heights
  43. James flood
  44. black Orpheus
  45. great upheaval / Haymarket st bombing
  46. Horatio Alger
  47. tank hill
  48. SROs
  49. Lily pond
  50. aquatic park
  51. filbert steps / Greenwich st
  52. go to lands end!!!

uuid: 202210261919 tags: #sanfrancisco #bayarea #travel #exploring

February 22, 2023