github: https://github.com/skritch
site: https://samkrit.ch/
substack: https://sketchingtowards.substack.com/
- sixoNo, not at all, the word trauma is predominately used today as the name for a sort of "psychic damage", like that which sometimes occurs when one is severely injured but which can also occur in many other circumstances, often purely social or emotional.
- Related: "Putting Differentials Back into Calculus " at https://bridge.math.oregonstate.edu/papers/differentials.pdf
- Location: Currently NC, but I'd like to move back to NYC. Open to in-person in either state.
Remote: Open to full remote or hybrid in NC/NYC
Willing to relocate: only on the East coast.
Technologies: Python, SQL, some Scala, some Typescript. DBT, Postgres, Spark, Flink. Various AWS like Kinesis, Firehose, Glue, Redshift. Various data pipelines
Résumé/CV: https://github.com/skritch/resume/blob/master/resume.pdf
Email: sam.kritch@gmail.com
I'd be interested in working on any of: data platforms, data pipelines, data engineering, or data-intensive backend applications. I would enjoy either a greenfield/early-stage data team where I could create a lot of value quickly, or, a more mature team with some veterans I can learn from.
- Almond milk is an economic substitute for dairy milk, making the comparison appropriate. No need to be dense about it.
- ah, I recall seeing that feature but had not taken a look at it for imports.
Imports ARE the case where untyped cell arguments are most annoying, but of course it would be nice to get it for free in all cases.
- That would be wonderful. A lot of the arguments are just imports, and these would have probably have the largest upside. It would be great if there was a construct like
I do not use Python enough to know if something like this can be hacked together. But if not, I imagine could be PIPed into the standard library if a convincing case were made for it.import numpy @app.cell def my_cell(np: types.ModuleType[numpy]): ... editor treats np like `import numpy as np` ... - Unfortunately the code in Marimo notebooks implements cross-variable references as untyped function arguments, meaning that nothing passed between cells can be type-safe. This makes it very hard to use tooling directly on the Python representation of notebooks.
- If so it's a big one, 1M solar masses.
- Can someone knowledgeable weigh in: is the "dark object" here believed to be a localized blob of dark matter? A dark star or black hole? Or is "dark" being used generally to mean "not bright enough to see at this distance"?
- Two extra characters per rep, each involving a "shift", and it's furthermore an eyesore to read
How is it that the comments on this post seem to consist 100% of people who think JSON is the perfect language and that any deviation from it is an unnecessary complexity? Use JSON for configuration for literally 5 minutes and you will get annoyed at quoting keys, lacking comments, escaping long strings, and juggling commas. MAML is almost exactly what I'd come up with (although I wouldn't have made commas optional, that feels weird.)
- Because it's supposed to be pleasant for humans and quoting keys is the least pleasant part of jsom config files.
- Similar: for years I've been lugging around the idea of making a game like Civilization but where all of the different theories of history can be turned on/off as modules. Maybe going back to prehistory:
- did fire lead to cooking lead to big brains lead to tools lead to agriculture?
- or was it ice ages ending that lead to agriculture?
- or did oxygen levels change leading to more efficient brains?
- or were we Born to Run?
- or did women's hips change shapes to allow bigger brains?
- or perhaps 2001: A Space Odyssey occurred as written
- or Ancient Aliens...
Repeat for every other highly-debated period of history.
Somehow having all of these in the same modular system feels like it would metabolize them in a way that reading a bunch of separate theories can't really do. Same for OP's anatomy.
- well yeah this is not itself the product, this is a demonstration of the need
Obsidian/etc really isn't it either, though; clearly OP wants to be able to do calculations with this stuff. They want both the knowledge graph AND an executable code environment. (I imagine Emacs can do both.)
But think more broadly. Imagine just
```
import <established knowledge>.anatomy
import <established knowledge>.high_energy_physics
import <established knowledge>.microeconomics
...
```
into a notebook-like environment, with good intellisense and completions. But not quite as a programming language—somewhere between that and a wiki.
- the absurd things people come up with to meet their own needs are usually good indicators of products and services which want to exist
- I find it helpful to think of that physical barrier as your own emotions barring you from entering a state where the uncertainty as to whether you'll be safe grows too high to trust yourself to operate in real time.
The problem isn't really being liked or not being liked, the problem is the cognitive overload of trying to predict what will happen and respond to it in realtime, which is sure to set in when one's mental model of the potential interaction is very uncertain. Of course, if your brain quits in a conversation, the other person is not going to be very impressed with you, so this kind of failure carries social risk itself.
The way to fix this is to have as many interactions which are bearable as possible so as to build out the mind's mental model of itself and others in social situations. Gradually the danger just fades away. There's no substitute for firsthand experience; no amount of premeditating, ruminating, or brooding will fix this.
- The weird thing about "The idea of being liked is just as anxiety-producing as being disliked" is that it is an incorrect prediction of reality: actually being liked would. Thinking about it is really a different thing: it overestimates the stakes involved, it mistakenly invents "ideas of people" to do the liking which do not behave like actual people, and is unable to build any self-esteem by imagining people liking you because these imagined people are under your our control; being liked by your own imagined people doesn't "count" the way being liked by real people would...
The human mind is not really designed to handle under-socialization well, and seems to fill in the empty space with imaginary figures which fail to meet its social needs. Taken outside its natural tribal operating regime, it bugs out in all kinds of strange ways.
> the idea of someone examining my own stories and thinking such thoughts about me is extremely distressing
This is a very familiar feeling to me, and in my experience it actually is a fear of being disliked, or more specifically about not being able to control others' reactions to me. But the fear is so great and unapproachable that the mind cordons it "out of sight" of conscious feeling.
It becomes better to not be thought of than to expose myself to the possibility of others seeing me poorly, especially if I'm not able to defend myself and make the case for my being seen with grace. I suspect that it is over-exposure to human meanness and judgement and under-exposure to kindness and grace which brings about this expectation of others' dispositions towards oneself; this perhaps is the reason for the Christian injunction that humans not judge one another--it guards against this particular failure mode of the social mind.
- Location: Currently NC, but I'd like to move back to NYC. Open to in-person in either state.
Remote: Open to full remote or hybrid in NC/NYC
Willing to relocate: only on the East Coast.
Technologies: Python, SQL, some Scala, some Typescript. DBT, Postgres, Spark, Flink. Various AWS like Kinesis, Firehose, Glue, Redshift. Various data pipelines
Résumé/CV: https://github.com/skritch/resume/blob/master/resume.pdf
Email: sam.kritch@gmail.com
I'm interested in working on data platforms/data pipelines/data engineering. I would enjoy either a greenfield/early-stage data team where I could create a lot of value quickly, or, a more mature operation where I can learn from some veterans.
- If you use an UNLOGGED table in Postgres as a cache, and your DB restarts, you no longer have a cache. Then your main table gets a huge spike in traffic and likely grinds to a halt.
- I toyed around with the idea of using an LLM to "compile" user instructions into a kind of AST of scaffolding, which can then be run by another LLM. It worked fairly wellbfor the kind of semi-structured tasks LLMs choke on like "for each of 100 things, do...", but I haven't taken it beyond a minimal impl.