_bramses

We also have an official meeting once a month to do book club matchmaking in person.

https://www.commonplace.nyc/

As such, people who are interested in learning more about how to have an intentional relationship with their library are left with a freshman level understanding of the topic.

The goal is to provide a comprehensive overview of the problems and solutions tried in the past, and give people access to creative ways to build (and share findings from) their libraries.

The whole discourse around PKM is a problem of the pluralistic framing in modern society that we hide behind individuality while missing the basic points. "Use whatever works for you" is intellectually lazy, and the opposite isn't an authoritarian ontology that people think they are protecting against.

Instead the basics are this: Whatever system you currently have to store/search/synthesize/and share information CAN and SHOULD be introspected to improve itself. Some functions are matters of time and space cost/benefits, other metric functions are qualitative, but can be experimented against and improved greatly with creativity and testing.

Remote: Yes

Willing to relocate: No

Technologies: JS, Claude, OpenAI, Python, Postgres, React, Node

Résumé/CV: https://www.bramadams.dev/share/

Email: [email protected]

Only interested in contract/part-time!

I'm a senior developer who is good at taking your prototype ideas into a more stable form. I have been a developer ambassador at OpenAI, a developer relations at Algolia, and a software engineer at HBO. I can either help you communicate technical ideas internally or externally, or build something.

I've been helping people achieve their reading goals by hosting workshops at libraries and helping adults become more intentional about their reading goals and how to achieve them.

I agree with your point wrt fragmentation, but my point is to actually assess the underlying mechanisms and address them more directly.

> Reading something you don't want to is going to stifle retention regardless of how you try and quantify it.

I agree and in fact, I point that very thing out in the slide about bad habits of holding onto a book that is not serviceable.

As a meta point many of the things I would talk about are lost in the medium of cutting text for slides, and I apologize that the examples (like the Illustration sections) must be on the responsibility of the reader. It makes more sense when delivered alongside talking!

- Life’s Articles, a personal Wikipedia

- Counting Worms, a very fast calorie tracker

- BookTalk, a audio based reading companion for capturing annotations

- Kindle Blocker, a Chrome Extension that earns you minutes on websites by reading with the Kindle app

[1] https://www.bramadams.dev/working-software/

[1] - https://gist.github.com/bramses/d59fb1659ec53fda9ec33f60200f...

[2] - https://linear.app/integrations/claude

my pride and joy with many easter eggs, including:

- random post surfacing

- animated book progress html [1]

- creative code [2]

- code poetry [3]

and much more!!

1 - https://www.bramadams.dev/book-progress-1-11-26/

2 - https://www.bramadams.dev/202308081300/

3 - https://www.bramadams.dev/202306131131/

Each of us is reading sixty books over 2026, five a month, where every book is self selected by each member.

It’s small, six people, all brought in by application only.

You can check out our shared bookshelf here! (Heavy inspiration from Stripe Press)

https://bookshelf-bookclub.vercel.app/book/cmj4pfpom001gqsbj...

(swipe left/right on mobile, up/down arrows on pc :))

The trick is to always keep the book queue filled, so long books that take a while coexist for a while with a number of shorter length ones

- Sixty books a year (five books a month)

- Self Chosen Books (no forced reading)

- Two recorded Salon style meetings monthly

- Bespoke software for the group including: shared embedding graph of highlights and annotations, IRC chat with @ for members and books and authors, collective bookshelf

- Six members max

Learn more here if interested!

https://www.bramadams.dev/sixty-book-club/

I’ll say this: between store, search, synthesize and share, store and synthesize are consistently the most difficult to nail down.

A society that wishes to succeed in creating an activated and knowledgeable populous should be interested in how to train people to notice better, and to create insightful follows.

In the words of David Deutsch (paraphrasing): knowledge consists of conjecture and error correction

I'm curious as to what you'll think of the UX layer I applied to embeddings for public perusal. I call it "semantic scrolling" since it's not searching exactly, but moving through the cluster by using <summary>/<details> as a tree.

[1] is a single starting point (press the animated arrow to "wiki-hole") and [2] is the entire collection (books, movies, music, animations, etc.)

[1] - https://www.sharecommonbase.com/synthesize/1009?id=1009 [2] - https://www.sharecommonbase.com/