8,504 karma · joined February 12, 2010
wonderfuldev_snrxn5rhbzc0kox8ykwk3ev0
But they think they can do it because they can spin it as "you did it first".
This just makes the point that there is nothing to gain by framing the issue as a grievance.
There are real prejudices and real systemic disadvantages to fix and while it's important to understand the history of them, I believe we put too much focus on that and less on what we can do to put that past behind us instead of dwelling in it. I don't think this approach of grievances has done anybody any favour in practice.
Let's not focus too much on the past problems that a group of people had, but let's make sure that the situation is improved for that group right now.
Focusing too much on past and try to tip the scale _because_ the past was so bad may lead to bad outcomes today. It may be perceived as a search for grievances and retribution and not the equalization of outcomes that one claims it should seek.
Whenever I need to change or fix ccwt I just spawn an agent with a fix and then I merge and rebuild the tool and it automatically autoupdates and restarts in the herdr tabs. This way I don't have to replace the "outer shell" of my agents for every change I make. Only when herdr itself gets reinstalled (often herdr can reattach to the same sessions but sometimes you just need to stop everything and restart all the agents. Losing progress notification state in the process)
I found a more modular approach that works for me:
1. Herdr terminal multiplexer 2. My custom orchestrator, which I grew out organically based on what I actually need and I feel I can easily change. It started like a minimal reimplementation of wt (worktrunk) but grew out into an integrated constellation of TUIs that leverage herdr API to drive herdr and help me navigate in herdr
Just sharing as an example of the pattern. It's not meant to be an useable tool by anybody else I think.
Such an explainer would contain for example a simulation of the feature, where it shows how data flows between components and allows the reviewer to tweak parameters and see how it affects things. The explainer can visually show edge cases or introduce faults.
Basically my problem is that agents can write a lot. They can write a lot of code and also a lot of natural language design/spec which ultimately becomes hard to review (sloppificarion of design documents)
Sometimes you can tame this by focusing on very high level, human curated specs, but since often the devil is in the details, you need a way to see these details.
I found that interactive visual exploration tools are a very good way to both iterate on your problems and to share it with your colleagues.
Inspirations:
works quite well
Latin didn't have two letters to distinguish V and U. You can still find inscriptions with VVA (modern spelling UVA)
Later that sound morphed to a voiced labiodental fricative which is what we think of V now
Once we get out of this hypergriwth phase the very same AI companies that now are giving you llms will provide a service that employed a rich mixture of optimized models that will reduce the operational costs to achieve the required results
There are also consequences in letting Russia take Ukraine militarily.
Whatever you think about the motivations and the desired end goal, actions and lack of actions both have consequences
Superstition in pigeons: https://psycnet.apa.org/record/1948-04299-001
There is a good reason why traditionally filesystem access was mediated by the OS layer, but there are many use cases where you just want to give processes a different view of what they already can access and it could be done as a library in the same userspace process.
However, for that to work across all the processes in a session we'd need a standard way to install such a hook in all peocesses and that's achievable to some extent using LD preload but falls apart quite rapidly with statically built binaries or different libcs
This is a very big hammer and reveals how foreign entities are deeply dependent on the American financial system and thus exposed to the political whims of the US.
https://en.wikipedia.org/wiki/Autistici/Inventati
Italian Postal Police wiretapping (2004–2005)
Luckily there are also people who manage to have impact while giving out a different vibe
If selling the weapons is "ok" because business must be allowed because the motive is purely selfish (I just want to make a living for myself and my family), and giving away weapons is "suspect" because "you clearly have an ulterior motive", if just means that we live in a world where selfishness is the norm being altruists is suspect.
I think this is the core divide of our society, much more useful than the obsolete "left" and "right" divide