







“markdown quotes” 😆


Crane decided to ask his AI agent why it went through with its dastardly database deletion deed. […] So, the agent ‘knew’ it was in the wrong.
No, you asked the confabulation machine to confabulate a reason/excuse after the fact, and it confabulated something that looks like a reason/excuse. At no point was there knowledge or introspection.


Do you write your tests in meetings? Do you do code reviews in meetings?
Do you think testing and reviewing code was a waste of time before “AI”?


roadmap definition, sprint planning, unit tests, regular independent code reviews, etc. etc. etc. that those of us who “knew what we were doing” mostly looked down on as the waste of time that it was
You sound insane.
Fuck off with that AI shit.
“AI” has also successfully found security vulnerabilities that don’t exist.
C++: [](){}
Yes, it’s sent to posthog.
That’s not what the Github ticket says.


Debuggers don’t go back; you have to restart and run through the whole thing
Yes, they do: https://rr-project.org/
https://sourceware.org/gdb/current/onlinedocs/gdb.html/Reverse-Execution.html
This is an entirely new way to misuse “strongly typed” that I was not aware of before. Amazing.
Thank you!


I, too, love living in a society that never makes errors, ever, as I myself am quite infallible. https://www.web3isgoinggreat.com/


Transfers are predictable and rapid.
And don’t forget how easy it is to reverse them in case of error.


That’s just syntax.
>>> 10 .yearsTraceback (most recent call last): File "<stdin>", line 1, in <module>AttributeError: 'int' object has no attribute 'years'


Does Ruby require the use of [] and {} there? Because those %w/%i/etc things look like custom quoting operators and at least in Perl you can use any delimiter you want: qw(a b c) is a list of strings, but so are qw+a b c+ and qw;a b c;.
$ python3 -c 'f = (lambda x: x + 0.5 - 0.5); print(f(2**52))' 4503599627370495.5
If you had let me write the C++ code, I could have literally destroyed your dataset in a couple of seconds.


I believe now it is my turn to say you’re spewing nonsense. Have you ever used a language with a type system? Because this whole idea of “testing external data to see if it is the right type” doesn’t really make sense.
At the lowest layer, generally, external data is an array of bytes. It has no other type you could “test”. However, you can decode or parse it into a form that makes sense for your program. And why couldn’t I cleanly recover from parse errors? (And how do you think Python does it?)