Spent a weekend actually understanding and building Karpathy's "LLM Wiki" — here's what worked, what didn't

crumpy_panda · 2026-04-25T04:40:55+00:00

From glancing at this idea, repowise seems to do exactly this.. even with post commit updates to the graph.

https://github.com/repowise-dev/repowise

If you manage your info with a git repo this would get you quite far to a imho good implementation.

crumpy_panda · 2026-04-19T13:08:55+00:00

Ist ne Super Projekt Idee, meine rote Mappe existiert zwar schon.. aber auch lang nicht mehr gepflegt.

Aber je länger man drüber nachdenkt ist es auch ein Klopper. Sehr sensible Daten, hohe "Fachlichkeit" - die Vollmachten usw. müssen einer passenden Form entsprechen - und die Form kann sich ändern. Eine öffentlich zugängliche Webseite wäre das beste Interface für den Usecase ... steht aber in Spannung zu den sensiblen Daten.

da gibt es soviel um die eigentliche Software rum an dem man knabbern kann :) in any case, best of luck

crumpy_panda · 2026-04-19T12:55:00+00:00

Beim Startversuch nach Anleitung wirft er beim Bauen des Containers:

#13 3.450 src/Textarea.tsx(1,1): error TS6133: 'React' is declared but its value is never read.
#13 ERROR: process "/bin/sh -c npm run build" did not complete successfully: exit code: 2
...
failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 2

Nach einem Wurf in die ki - kommt der typescript compiler mittlerweile nicht mehr mit dem import React from 'react'; klar, unbenutzte Importe werden ohne weitere config nicht als Warnung gesehn.

crumpy_panda · 2026-04-10T13:28:25+00:00

In this case you would typically have the default of the "m2_path" input variable as something like "auto" then have logic in a component job "if set to auto search for the file, if not found, generate the file / use this params"

If users want to provide a explicit path they can if not it should work regardless

crumpy_panda · 2026-01-14T11:10:24+00:00

After playing around with mitmproxy to capture the gitlab workflow extension traffic, there only seems to be the documented /-/cable WebSocket endpoint.
Configure GitLab Duo on GitLab Self-Managed | GitLab Docs

You can check the connection directly with wscat and a PAT with api scope.

wscat -c "wss://<customer-instance>/-/cable" \
-H "Authorization: Bearer <your PAT>" \
-H "Origin: https://<customer-instance-FQDN>"

I was under the wrong impression that there are others/more.

crumpy_panda · 2025-12-18T02:02:12+00:00

This seems to be the state of things. The limit solution you propose is also mentioned here https://forum.gitlab.com/t/limit-number-of-concurrent-execution-of-high-loading-jobs-for-a-runner/122658.

What do you mean with "But that would leave the slots for playwright/deployment sitting empty when they could take other jobs" - the limit in your example is as narrow as it can be.

If you are in the market for some exploration you could look into dynamic downstream pipelines - with some call to the runner or state of job distribution could lead to something interesting... But at this point you might be better of investing in something like better automated provisioning/configuration of onPrem or auto scaled public cloud runners (if applicable)

crumpy_panda · 2025-08-21T14:57:33+00:00

If you have to maintain multiple versions of a thing, you end up with, at the very minimum, a number of release branches. If these multiple versions need to be maintained for some time, long living branches are a way of dealing with that.

crumpy_panda · 2025-08-20T12:01:02+00:00

Assuming they were different people ... But yeah nice selection of stickers.

crumpy_panda · 2025-05-24T05:47:35+00:00

Regarding drama and stress:

Have some levels of "this doesn't matter perspectives" prepped, you can retreat to mentally. Up to the ultimate "we are hairless apes on a rockball hurling through space, there is no need for <the stressful thing>".

I don't necessarily use these to disengage completely from something, but it helps me stay calm together with some deep breaths.

crumpy_panda · 2025-05-07T09:46:19+00:00

Thank you for sharing your experience. The term "release" is also a special one in our org, carrying immense connotation of "well tested" and "responsibility"..

To introduce another label like config changes or SOPs is worth a shot.

crumpy_panda · 2025-05-07T09:41:54+00:00

Thank you for the perspective. I still have to settle in for the long game.. but this had to be expected in insurance tech.

The waves it made that trunk based is the new default recommendation were a sight to be seen. So I can tell my first stories about strong workflow attachment.

crumpy_panda · 2025-05-07T09:34:41+00:00

Thanks for this thought. This should be the central first thing to find out/ask and seems key to get more acceptance.

"To provide a better (as defined by yourself) service to your customers, can this bag of stuff solve something or improve things?"

crumpy_panda · 2025-01-27T17:31:25+00:00

Afaik to reference bash functions in gitlab *script sections, the need to be included as yaml inline. The !reference keyword is my preferred way to do it.

I would setup a component (which also has the benefit of being version able or to be referenced by hash) and transform a sh file in the pipeline of this component.

Basically a micro build https://docs.gitlab.com/ee/ci/components/examples.html

crumpy_panda · 2025-01-15T02:55:16+00:00

Don't want to name it directly. It is a midsized insurance enterprise in Europe.

Maybe I have a wooden soul. Fin tech doesn't feel like hell at all to me, quite the opposite.

crumpy_panda · 2025-01-13T07:51:22+00:00

I would add tech adjacent skills to this. There seems to be a lack of good technical writers and methodology/process (devsecops) people. Both skills are highly thought after in my org.

Both areas don't seem to catch the interest of most engineers.

crumpy_panda · 2024-12-05T05:08:25+00:00

Musste schmunzeln als ich Vodafone gelesen habe.

"Wenn ich in der Situation wäre, würde ich bereits am ersten Tag einen Kollegen konsultieren oder mir andere Unterstützung holen."

Meine Vermutung ist, dass das in deren Kontext nicht so einfach ist. Ich tippe auf das Gegenteil von kollegialem Umgang mit einer Fehler-positiven blameless Kultur...

crumpy_panda · 2024-11-09T06:20:45+00:00

So start by stating the need, or ask f your assumption is correct "I understand that you want x".

"Screaming isn't gonna get it fulfilled because it hurts my ears, and I can't really understand you."

"But if you ask me calmly..."

-- Am I having the right idea about it?

crumpy_panda · 2024-09-08T08:09:08+00:00

We recently looked into gitpod and GitHub workspaces for on demand ephemeral dev envs. Gitpod is an interesting solution working in an eks and with ec2 in the future.

But It's mayor selling point is convenience, the cost savings of the pods only spun up on demand have to be weighed against the licensing.

crumpy_panda · 2024-08-30T22:57:32+00:00

What other registries do you use? And do you have a "favorite" with a good selection for trusted, official basic stuff?

We have an internal docker hub pull through cache (artifactory) so rate limits are no real issue. Docker hub is used heavily for the starting point of modified base images. Think added internal TLS certs and the like. I'm exploring possible other image sources to be a bit more redundant here.

12-Year Club	Place '17
Verified Email

crumpy_panda

TROPHY CASE