barubary

There's some insane ideas in there, like:

• Only release every two weeks.
• This includes bug fixes.
• Emergencies can be dealt with immediately, but any root cause analysis or deeper work on underlying issues must wait for the next sprint.
• If it can't be done in 4 hours, it can't be done at all.
• Don't document things.
• Don't write bad code. (Also: You must use classes and methods, and variable names must be words.)
• Rigid adherence to the "agile process" is required.
• The job of a software developer is to crank out code and nothing else, especially not design, testing, or documentation.
• Don't even think about ethics.

"AI" has also successfully found security vulnerabilities that don't exist.

What, no COBOL? No 5GL?

C++: [](){}

Do you think the Luddites were wrong?

Yes, it's sent to posthog.

That's not what the Github ticket says.

https://en.wikipedia.org/wiki/In/_the/_Beginning.../_Was/_the/_Command/_Line

BEFOREHAND: close door, each window & exit; wait until time.    open spellbook, study, read (scan, select, tell us);write it, print the hex while each watches,    reverse its length, write again;    kill spiders, pop them, chop, split, kill them.        unlink arms, shift, wait & listen (listening, wait),sort the flock (then, warn the "goats" & kill the "sheep");    kill them, dump qualms, shift moralities,    values aside, each one;        die sheep! die to reverse the system        you accept (reject, respect);next step,    kill the next sacrifice, each sacrifice,    wait, redo ritual until "all the spirits are pleased";    do it ("as they say").do it(*everyone***must***participate***in***forbidden**s*e*x*).return last victim; package body;    exit crypt (time, times & "half a time") & close it,    select (quickly) & warn your next victim;AFTERWORDS: tell nobody.    wait, wait until time;    wait until next year, next decade;        sleep, sleep, die yourself,        die at last

https://infosec.exchange/@barubary/114697898020548880

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

Look up history-search-backward in your favorite bash/readline manual.