Recent submissions

Comment · 3 months ago
I lose about 25% if I do not clean during bushfire season
Comment · 3 months ago
Comment · 3 months ago
Comment · 3 months ago
now do usa
Comment · 3 months ago
Tjanara Goreng Goreng did nothing rong.

#LiarDreaming

Comment · 10 months ago
how is that a personal attack?

a personal attack would be eg calling him a DC.

all I did was point out the intellectual dishonesty of his argument. that's an attack on his intellectually dishonest argument, not his person.

by all means go ahead and ban me

Comment · 10 months ago
isnt the 1RM the measure of progress?
Comment · 10 months ago
anywhere you want hard isolation and only a subset of OS. especially multiple instances thereof.

so, generally at the edge (gateways, shims, protocol boundaries)

Comment · 10 months ago
container can be smaller at rest, but larger at runtime

if you're not sure which you want its probably container

Comment · 10 months ago
one reason i can imagine for this choice is that human review distributes new knowledge among human maintainers. Automated review might discourage that valuable interaction.

The comment is an artefact of an inherently valuable process, not the sole objective. So I'd prefer code is reviewed by a human who maybe initiates a discussion with an agent. I'd hope this minor workflow detail encourages the human to take a more active lead, rather than risk mere ceremonial approval.

Comment · 10 months ago
oh yeah well that's an extreme example of how one dev's use could overwhelm a team's capacity.
Comment · 10 months ago
Hi, the reason I have this expectation is that on a (cognitively) diverse team there will be a range of reactions that all need to be accommodated.

some (many?) devs don't want agents. Either because the agent takes away the 'fun' part of their work, or because they don't trust the agent, or because they truly do not find a use for it in their process.

I remember being on teams which only remained functional because two devs tried very hard to stay out of one another's way. Nothing wrong with either of them, their approach to the work was just not very compatible.

In the same way, I expect diverse teams to struggle with finding a mode of adoption that does not negatively impact on the existing styles of some members.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton