[0] https://old.reddit.com/r/ProgrammerHumor/comments/1teswot/pe...
1,756 karma · joined February 28, 2014
[0] https://old.reddit.com/r/ProgrammerHumor/comments/1teswot/pe...
Curious to know more about your work:
Are your agents working on tangential problems? If so, how do you ensure you're still thinking at a sufficient level of depth and capacity about each problem each agent is working on?
Or are they working on different threads of the same problem? If so, how do you keep them from stepping on each other's toes? People mention git worktrees, but that doesn't solve the conflict problem for multiple agents touching the same areas of functionality (i.e. you just move the conflict problem to the PR merge stage)
Otherwise, as a sibling comment said, incremental search/replace is your friend.
Right now AI is in its mainframe era (thin clients connecting to expensive compute somewhere else that you don't control), but I firmly believe that the AI version of the personal computing revolution is on the horizon. Democratized computing probably seemed pretty out of reach when all we had were mainframes, but in retrospect the progression from mainframe to personal computer to supercomputer in your pocket seems ordinary and almost expected.
I have no doubt that the technology needed to democratized personal AI will also advance in similar ways, and we will have no shortage of next generation's "640K ought to be enough for anybody."
Through a sufficiently narrow lens, any technological advancement can be perceived as a threat. If your job was to perform calculations for your company using a microscope and calculator (computer, the job title) then the invention of the computer (the machine) was absolutely a threat to your job security. That's not to say that there aren't challenges to adapting or considerations for how to do it well, but it has always been the case that the old way is a casualty of the new way.
I am neither anti-AI nor an AI evangelist but I think a more productive viewpoint is to think about how these advancements could open the door to new opportunity. For example, democratization of learning. It has never been easier for anyone in the world with an Internet connection and a computing device to have access to a personal math tutor or nutrition coach.
If that's not the part of my message you're referring to, then your message seems completely orthogonal to what I posted.
To those downvoting, please note that this person did not say that nobody should switch, only that the information provided was a clear indication that it is not the right fit for them.
I, for one, greatly appreciated the detailed pro/con list in the post, as many of these would be genuine annoyances to me, and would have probably taken several months to encounter all of them.
This started from a desire to avoid an unknown amount of bloat and untrusted code, but also because I'm pretty tired of getting Node deprecation warnings for installing/using something that has nothing to do with JavaScript at all.
I've always installed a pinned version of Trivy of my choosing, and installed by curl | sh.
Looks like curl | sh may have saved my skin, whereas even older versions of the github action were force-pushed to install the vulnerable binary.
The people who try to force everyone else to fit into a specific bucket of communication style, or who refuse to deviate from their own strict communication preferences no matter the audience, those are the people I see struggle to find success relative to their peers.
I've been a long-time Apple user (and long-time user of Linux for work + part-time for personal), but have been trying out Arch and hyprland on my decade+ old ThinkPad and have been surprised at how enjoyable the experience is. I'm thinking it might just be the tipping point for leaving Apple.
This resonates with me so hard. I'm not a "no external packages" purist, but there are a number of pieces of functionality that I wrote for myself because there wasn't anything quite like what I wanted.
One example is a function to expand the region (selection) to any arbitrary set of pairing delimiters that I define in a defvar (parens, quotes, brackets, or I can can supply a custom left/right regex for matching). Then, when I execute the function, it waits for a second keypress, which is the trigger key I've defined for that matching pair, and it will expand the region to the left and the right until it meets the applicable delimiter.
Repeating the same key presses results in selecting the left and right delimiters themselves, and another repeat will extend to the next set of matching delimiters, and so on.
Even though I use a treesitter-based expand-region plug-in, my custom function is still invaluable for when I want to jump past a series of valid treesitter object expansions, or when certain text objects are just not defined in treesitter.
Some of the helpful custom expansions I have defined are:
"w" to select what Vim considers a lowercase-w word
Space to select what Vim considers an uppercase-W word
"$" to select ${...}-style expressions
"/" to select everything between forward slashes
"*" to select between asterisks (useful when editing markdown)
It's really an invaluable function for me, personally, but I always talk myself out of trying to open-source it because it has some gotchas and limitations, and I just don't want to be on the hook for trying to make everyone who uses it happy.
> Matchlock is a CLI tool for running AI agents in ephemeral microVMs - with network allowlisting, secret injection via MITM proxy, and VM-level isolation. Your secrets never enter the VM.
In a nutshell, it solves problem #2 through a combination of a network allowlist and secret masking/injection on a per-host basis. Secrets are never actually exposed inside the sandbox. A placeholder string is used inside the sandbox, and the mitm proxy layer replaces the placeholder string with the actual secret key outside of the sandbox before sending the request along to its original destination.
Furthermore, because secrets are available to the sandbox only on a per-host basis, you can specify that you want to share OPENAI_API_KEY only with api.openai.com, and that is the only host for which the placeholder string will be replaced with the actual secret value.
edit to actually add the link
For Emacs, I use multiple cursors and a treesitter-based plug-in for incrementally expanding or reducing the selection by text objects. I also have a collection of my own helper functions for working with text that make my non-modal Emacs approach still feel very comparable to the power of manipulating text in Vim.
Curious to hear if your issues with modal editing are similar.
Another commenter mentioned needing to get alerts for fraud, but none of the financial institutions i'm currently doing business with have any trouble sending me text messages. In fact I have the opposite problem, I can't get them to stop using text for 2FA codes...