[0] https://old.reddit.com/r/ProgrammerHumor/comments/1teswot/pe...

Comments URL: https://news.ycombinator.com/item?id=47912387

Points: 2

# Comments: 0

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.

https://m.youtube.com/watch?v=jNa3axo40qM&t=23s

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.