1,379 karma · joined August 10, 2015
Having the kind of network and connections you do connects you with the actual needs of your community
At which point, it's not necessarily Transactional, but fostering connection and collaboration in order to create win-win situations for everyone in your community.
That's what politicking Should be.
I've been exploring spec driven workflows, but from a different angle.
I've been thinking about how to describe systems with a standard format, recursively. Instead of one 10 page doc, you might get 10 one pagers, starting from the highest level of abstraction and recursing down into the parts and subsystems, all following the same format. Building out this Graph of domains provides certain reusable nodes/bits of context.
This then extends to any given bit of software, which is a system in itself composed of the intersections of a lot of different domains and subsystems.
Cue looks interesting and is something I'll be digging into more
Now if it changes _again_ that's a different story. If it changes Too Much, it becomes a distraction
If, for code, there is a parallel "state" document with the intent behind each line of code, each function
And in conjunction that state document is connected to a "higher layer of abstraction" document (recursively up as needed) to tie in higher layers of intent
Such a thing would make it easier to surface weird behavior imo, alongside general "spec driven design" perks. More human readable = more eyes, and potential for automated LLM analysis too.
I'm not sure it'd be _Perfect_, but I think it'd be loads better than what we've got now
There's less suffering, sure. But if I were in their shoes I'd want to have a choice. To be manipulated into wanting something so very obviously and directly bad for us doesn't feel great
One thing I wish for encompasses the idea that I might want to share different slices of my life with different groups
Fancy validator selection sounds like the individual financial institutions are still responsible for managing and maintaining their nodes, which gives them a fair (as in balanced not fair as in a lot) amount of liability/responsibility/control.
A distributed database, afaik, while geographically distributed, entails more centralization of power/control.
Some initial notes:
- On the very first initial load, ~~there's no default tool selected~~ it selects the 'hand' tool in the bottom left, which hides the cursor. It seems to select the pointer tool after a refresh. I'm able to replicate in an incognito browser or by clearing site data. After scanning your documents, it appears its touchscreen related. My guess is that it got confused because I'm using one of the ASUS Duo laptops.
- I personally think it makes more sense to start docs on "What is Context" (on the documentation drawer), but that's a matter of opinion. The sandwich icon isn't as obvious as I'd like though, and it'd be nice to have a link to the next page at the bottom of every article.
- my initial thought from the sequence diagrams panel was that I could type to generate an initial image, then drag that into my canvas for position changes.
- this actually makes me think about mermaid's rendering engine, and how hard it would be to support moving and "pinning" an element, such that further diagram changes need to work around the pinned elements.I love the idea of epicenter. I love open source local-first software.
Something I've been hacking on for a minute would fit so well, if encryption wasn't a requirement for the profit model.
But uh yes thank you for making my life easier, and I hope to return the favor soon
This is the comment that spawned this tragedy of miscommunication.
My interpretation of this comment is that no current programming agents/llm tooling utilize commit history as part of their procedure for building context of a codebase for programming.
It is not stating that it Cannot, nor is it making any assertion on whether these assistants can or cannot be Trained on commit history, nor any assertion about whether commit history is included in training datasets.
All its saying is that these agents currently do not automatically _use_ commit history when finding/building context for accomplishing a task.
I guess I hadn't considered the existence of generic TCP proxies And I'd probably have concerns around how much latency it would introduce in an environment where we have some requirements on the rate of data collection.
That said our service Does act as a kind of proxy for a few protocols.
Plus we have a case where a certain type of request should skip to the front of the queue.
Leaning on promises does cut out a lot of the user space complication though.
A game of learning your homelab into a cyberpunk mystery adventure | Hacker News https://share.google/WedMuRgx5WgreNqSN
Or hey maybe they could charge for these expiration notifications.