mastodon 4.7.3XXX TODO
Turned in my work self-eval yesterday.
Knowing I'm evaluated on whether I'm "leveraging AI" is demoralizing. Employers should think about it. I almost turned in my notice instead of the self-eval twice.
@DecaturNature Exception: github does apply patches in case of rebase/merge, but those are patches specifically generated by diffing trees, never patches provided by users (much less commit messages).
I'm not sure we even do that using any kind of custom code - probably we just use git.
I'm a GitHub employee.
To quibble with the framing of the original: the unsafe behavior is using patch to apply patches - good reminder to be super careful doing that. yow
reminder to myself:
- have priorities
- schedule downtime
- if you're reading this after May 2025, you're scrolling your own posts. cut that out, go for a walk or something
I am not superstrong at math-- I just like it :)
same! :)
I was wondering how you got a cyclic function out of ln and exp.
Perceptive. Yeah, I think it would be impossible if this weren't complex math.
Also wonder: is this idea similar to Taylor polynomials?
Seems unrelated, although a cool trick you can do is: start with (exp(ix) - exp(-ix))/2i, then replace both exp's with the Taylor series for exp, apply algebra, and see if you get the Taylor series for sin :)
@DecaturNature to be clear: github doesn't apply patches to your code.* The way git push works is not based on patches. That is, as the level of surprise in the original post suggests, not how any of this works.
But patch and git-am do take arbitrary text input and apply it as a patch, and patches are not a good data format. patch for sure can be tricked.
*see next message
Among my angry Luddite tendencies is my insistence that
> there are some things a computer just can not say to a human <
It suddenly occurs to me that I have never heard another person express this view.
I took a quick look at all four of these. They are valid bug reports (not security-sensitive; those are still locked and I can't see them).
I'm very familiar with SpiderMonkey internals and Bugzilla. I've worked with most of the people in these bugs. If you have questions, ask me.
In this kind of code, SpiderMonkey usually follows the spec step by step, including assertions. All four of these were in fact bugs in the spec.
`Cell` and `RefCell`: Do you use them?
I saw this article on here and I'm so tired.
It starts out like "your brain does not store memories" and like 2 paragraphs later retreats to the position that human memory doesn't work the same way computer memory works, which, sure, is a rhetorical move freely available to assholes, and then it's like "people used to literally believe human bodies were made of clockworks", omfg
Very good document on cancel safety in async Rust: https://rfd.shared.oxide.computer/rfd/0400
i have scheduled downtime every night, and for meals, but i also have sporadic unscheduled downtime
i can't aspire to any nines. in a good month i have one 3 of uptime
(playing on repeat in my head all day)
this song has a thousand verses
because of AI
and it's all clean, no sex or curses
because it's AI
so if you're a little bored, well i know why
because of AI
because of AI
because of AI