2025-12-10 10:28:31
Had to turn my LinkedIn job notifications off. I’ve been practically hyperventilating at the wall of job noise I’m met with every time I open my email.
#redundant #redundancy #job
Had to turn my LinkedIn job notifications off. I’ve been practically hyperventilating at the wall of job noise I’m met with every time I open my email.
#redundant #redundancy #job
#Steady
Unterschätzen #Arbeitnehmer die Auswirkungen von KI auf den eigenen #Job?
Wie realistisch schätzt man eigentlich die eigenen
Worked on some more #Gentoo global #jobserver goodies today.
Firstly, Portage jobserver support patch: #PyTest jobs will also be counted towards total job count.
Again, it's not a perfect solution, but it works reasonably. The plugin still starts -n jobs as specified by the arguments, but it acquired job tokens prior to executing every test, therefore delaying actual testing until tokens are available. It doesn't seem to cause noticeable overhead either.
A great opportunity is now open for a Tech Team Manager in the Discovery and Delivery Program at the California Digital Library where I work! This is a great group of folks doing innovative work in core library areas. #jobs #libraries
Wenn dir „irgendwer einen Termin reingedrückt hat“, obwohl du da bereits Termine hast, dann ist dieser „irgendwer“ entweder ein Arsch oder Deine bisherigen Termine sind DIR nicht so wichtig.
#Erkenntnis #Job
#Gentoo #jobserver revealed another problem with steve in particular, and (I believe) the jobserver protocol in general: blocking clients are prioritized over polling clients.
The problem is simple: when handling blocking reads, steve can issue a job token immediately. When handling a poll, it merely indicates that a token is available, and the client must issue another read request to get it. So if tokens are scarce and there are both blocking and polling clients running, the former are likely to be taking all the incoming tokens.
My idea of working around this is to implement temporary reservations. If a client polls for a token, we reserve one for it. The reserved token can afterwards be only read by the same client. This way, both blocking and polling clients get a token — the former get it immediately, the latter get it reserved for them. And if there are no tokens available, both get into a single FIFO queue, for a poor man's round-robin (steve also throttles all reads to one token at a time).
However, polls technically don't guarantee that the client will eventually read the token, so we need to handle reservation expirations as well.
Tja, dann hab ich beim Gespräch mit dem Chef plötzlich doch gesagt, was ich denke, obwohl die Erfahrung mich gelehrt hat, dass das selten gut endet.
Schauen wir mal, ob ich es bereuen werde.
#job
Jetzt ganz diese Scheiße schon wieder an und man will meinen Mac fremdverwalten
🤮
#job
„Hier…. *gehirndurchfall*…. nächsten Dienstag bräuchte ich das!“
„Klar, soll ich dir übers Wochenende auch noch einen Kuchen dazu backen?“
#job
Heute ist ein Tag, der mich beruflich etwas frustriert zurücklässt:
Als ich damals anfing, war das ein begeisterter kleiner Haufen, der zusammen hielt und der alle Probleme unbürokratisch und schnell löste. Genau das fand ich immer super.
Und jetzt ist der Laden nur wenig größer, aber ein Paradebeispiel für Passierschein A 38
#job
#Steve the #Jobserver has undergone a major rewrite over the last week. It's now implemented using CUSE, the #FUSE API for character devices. It is using pidfd to track processes acquiring job tokens, and automatically reclaims them if processes die without returning them, preventing dead processes from effectively locking the system jobserver.
The code's still a bit ugly — it's a C-changed-midway-to-C , with libevent for event loops and (still) FUSE's ugly argument parsing.
If someone wants to play with it, the live ebuild is available in #Gentoo as dev-build/steve.
https://gitweb.gentoo.org/proj/steve.git/