bionsystem

Ah, that makes sense actually. Thanks.

I don't get it, why would they be upset if somebody pays for the game ?

On mac AZERTY keyboard those keys are next to each other, maybe it was a typo ?

They changed licensing.

braid has been a treat for us to manage external dependencies. Much cleaner than submodules.

I have more trust in my senior dev without an LLM, than in my junior ops with one ; I saw the MRs ^^. But that's beside the point, because eventually the LLM will be good enough to operate, with or without my junior ops, myself, or anyone really, maybe.

oh I meant "reading" is slower not "running", but I guess you may still be right for large context. The article is about that though (a dev giving up on reading code entirely because that would be too slow).

Why would any of this make you a jerk ?

I guess it all depends on context, where I work ops stuff is clearly the bottleneck for a variety of reasons (technical debt that we are constantly working around, secret management for compliance reasons, etc). We self-host everything from bare metal. Some people would need to rethink the infra from the bottom up before it is "LLM ready".

That doesn't mean my job is not threatened mid/long term, in fact, thanks to LLM it is possible to rebuild that in a reasonnable amount of time I think. It's actually one of my side projects to offer this as a service. But if that doesn't work maybe I should have a plan C.

As an SRE I would be very interested on experienced devs point of view on that stance, "we don’t even necessarily need to read the code the LLMs produce". To me, that is the only way a single dev can manage > 1 agent. Because I feel running the code will always be slower than a single agent generating it. On the other hand, it implies lack of human understanding on what is going on under the hood. Which is fine if you trust the LLM to write great code, and great tests for the code, but fundamentally you have to have 100% trust, 99.9% is not going to be enough in any serious industry, would it ?

Also eventually you'll also have to trust it to write the deployment code or even run the deployment itself, otherwise SRE is going to be the bottleneck. And only then should I feel anxiety about the rest of my career (that, or my employer decide LLM are good enough to get rid of me, even if they are imperfect).

I also saw entities (mainly gov agencies) where it has a disastrous result. Because management know they will be out in 3 years, they spend as much budget as they can to initiate as big projects as they can and have them on their resume, plan beyond their 3-y stay here, and leave with a big bonus. This way they never get asked why it is not complete ("because it's plan for a couple more years"), the project fails eventually (people actually working on the stuff end up leaving too at some point), and the cycle repeats with the next guy.

Ah, I wouldn't know of any actionnable way to unlock this for yourself unfortunately. I think those people are gifted. There is definitely research (and documentaries around that research), you can look for Julian Stanley "Quick learners" or Maryam Mirzakhani and there are of course plenty of it. But again, it's not actionnable to watch a 13yo solve a very hard problem in 4 different ways in 20 minutes.

Unfortunately I think it is as much a curse as it is a gift. One of my parents' friend is a math researcher. He is not at the absolute end of the spectrum, but he is the kind of people who will write on the bathroom walls because he has an idea NOW and it cannot wait a minute to explore. He forces himself to do competitive cycling and can't enjoy more casual hobbies because if he does not spend 100% of his energy and focus to something, his brain will just do math.

I'll add my stories to the 2 brother comments, in my prepa my best friend was by far the best in class. He did the 2 year program in chemistry in the first 2 months by himself. He arrived once in exams after a full night of re-reading the 3 LOTR books and still nailed the best grade effortlessly. And to his own admission, he was far from the most productive / smarter guys he knew.

I remember listening to him and a teacher, the teacher would give some anecdotes on what he's seen at the ENS. People reciting world chess championship games at night to fall asleep. Reading massive math books (1000+ pages) in an afternoon. Another story I heard in a different context from another teacher, math students were assigned a python project, after an introductory course. They never did any programming before. One student wrote 300 LoC in a single function and showed it to the teacher. It didn't have a main function, so the teacher asked him how he tested it. The student didn't know what he was talking about. They added what's needed to run the function and it worked.

It is. Probably an even greater gift to earth from the NetBSD community than NetBSD itself. The ability to run recent packages on most arch without them forcing you to use NetBSD, but allowing you to keep the original OS in many cases if you want, is mind-blowing.

We have that in France already it is called bloctel

As an SRE/ops (and I'm talking some years ago) it was often a pain point, especially with devs with a "works on my machine" attitude ; you would never get the exact requirements from them, I even saw a team of 2 who worked together with different versions of stuff on their respective machines. I also worked in some "offline" environments where once in prod you cannot pull anything from the internet, and you cannot install a compiler too, so it's quite hard to ship because some pip packages require to be built.

I found a way using (can't remember the tool name) which if you loop through the imports and gives it to the tool you get the package name, then I would build wheels to have all binaries and build a container or a VM with all that's needed, thus working completely around python package managers. This was a good enough workflow for the kind of deployment we needed.

Jupyter added a layer of complexity, I deployed it alongside RStudio as browser IDEs in docker swarm. Everybody wants a different set of deps and versions, so you have to keep track of everything, and also people may use things just for development that must not be shipped to prod, so you have to keep track of that too. Also some would develop notebooks on windows and expect them to work in linux VMs/containers and even in prod.

Nowadays devs ship container images anyway through a CI so it is less of an issue. In this era docker was far from being the de-facto everywhere, some people were still afraid of this, security didn't like it, etc.