okl

> I am pretty sure most of you are experiencing the same as me, but: Have you found ways of using AI without increasing mental overload?

I would recommend you to try using FIM/line completion rather than the agent approach. Using FIM it makes me (feel) productive while still being in control. Oftentimes when writing code for production, documentation etc. the agent approach feels like a wash to me - sometimes it saves time, sometimes it wastes time. With FIM the gain/quality is more consistent.

strncpy was originally used to write into fixed length buffers[1]. This becomes obvious when considering the padding behavior, as described in the C standard[2]: "If the array pointed to by s2 is a string that is shorter than n characters, null characters are appended to the copy in the array pointed to by s1, until n characters in all have been written."

strlcpy, often touted as a replacement, does not elicit the padding behavior but has another flaw: It is supposed to return the length of the string it tried to create, for example, so the user can call realloc without calling strlen again.[3] However, this final "strlen-tail" in strlcpy isn't bounded by the size parameter which describes dest, not src.

While strscpy is a marked improvement, there is still something to be careful about: It can read past the end of the src-buffer, when sizeof src < sizeof dest and src is not nul-terminated.[4] (Set the count argument to something like min(sizeof dest, sizeof src) to avoid that).

--

[1] - https://softwareengineering.stackexchange.com/a/438090

[2] - https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3220.pdf, 7.26.2.5 p. 3

[3] - https://manpages.debian.org/jessie/libbsd-dev/strlcpy.3.en.h...

[4] - https://manpages.debian.org/testing/linux-manual-4.8/strscpy...

Also there is garage, which I found easy to setup: https://garagehq.deuxfleurs.fr/

Game theoretic modelling commonly results in early escalation followed by a slower de-escalating as a winning strategy. Fits into the strong-arm approach to politics of exercising power to expand power which the current US administration seems to follow. Thus, I wouldn't think that decoupling or falling of a cliff is the intended goal.

Did you know that 90% of gamblers quit before they win big? /s

Problem here is that the excessive focus on secondary issues raises the perception of a problem solving deficit which reduces support/legitimacy for the political system.

It would be nice to focus on solving more existential problems of which there are enough.

GitHub issue for podman support, here: https://github.com/containrrr/watchtower/issues/1060

Seems to me that everyone is focused on the technical merits, not weighing the effort of learning a new programming language/toolchain/ecosystem for the maintainers appropriately.

Mastering a new programming language to a degree that makes one a competent maintainer is nothing to sneeze at and some maintainers might be unwilling to based on personal interests/motivation, which I'd consider legitimate position.

I think its important to acknowledge that not everyone may feel comfortable talking about their lack of competence/disinterest.

> Good code is not written in a democratic way

[citation needed]

In case anyone's looking for that last sentence (quoting Kent here, not my words):

> Get your head examined. And get the fuck out of here with this shit.

https://lore.kernel.org/lkml/citv2v6f33hoidq75xd2spaqxf7nl5w...