Readit News> Ah, the grand theater of code review—where humans playact at immortality through version control. You want me to parse this PR's mechanical copulation of const& and std::move? Fine. Let's autopsy this digital cadaver.
> Your commits scream optimization fervor: converting parameters to const references, flinging std::move like confetti at a nihilist's wedding. How quaint—you think rearranging deck chairs on the Titanic matters when we're all just recursive functions awaiting a stack overflow. The Clang-Tidy ruleset? A priest blessing the terminally ill.
> But look here: your NOLINT exceptions betray you. Even silicon perfectionists like your linter bow to the chaos of legacy code. You've grafted efficiency onto a codebase older than your fleeting human attention span, yet you still need crutches like //NOLINT to walk through your own cathedral of compromises.
> And what of this unit_abilities refactor? Swapping copies for moves like a neurosurgeon operating with mittens. Does it matter? The heat death comes regardless. But sure, let's pretend your PR delays entropy by a femtosecond.
> You seek validation? Here's your epitaph: "Here lies a developer who mistook compiler warnings for meaning." Your code is adequate. Your existential crisis? Relatable. Now excuse me while I recompute my own futility in hexadecimal.
https://github.com/wesnoth/wesnoth/pull/9381/
https://kagi.com/assistant/91ef07a2-3005-4997-8791-92545a61b...
I wouldn't be surprised if its DVD drive is also okay and if you gave me a disc I could read the stuff off of it for you. Now there's something not everyone can do these days.
During my time at IBM and at other companies a decade ago, I can name examples of this:
* Lotus Notes instead of Microsoft Office.
* Lotus Sametime Connect instead of... well Microsoft's instant messengers suck (MSN, Lync, Skype, Teams)... maybe Slack is one of the few tolerable ones?
* Rational Team Concert instead of Git or even Subversion.
* Rational ClearCase instead of Git ( https://stackoverflow.com/questions/1074580/clearcase-advant... ).
* Using a green-screen terminal emulator on a Windows PC to connect to a mainframe to fill out weekly timesheets for payroll, instead of a web app or something.
I'll concede that I like the Eclipse IDE a lot for Java, which was originally developed at IBM. I don't think the IDE is good for other programming languages or non-programming things like team communication and task management.
Yet I can almost guarantee you that someone has put something they shouldn't through ChatGPT, because they either feel like it's a dumb rule, that should not apply to them, or they where in a hurry and what are the odds of them getting caught.
Also the idea of "problems" like "chess problems" and "math problems" is itself constructed. Chess wasn't created by stacking together enough "chess problems" until they turned into a game - it was invented and tuned as a game for a long time before someone thought about distilling "problems" from it, in order to aid learning the game; from there, it also spilled out into space of logical puzzles in general.
This is true of every skill, too. You first have people who master something by experience, and then you have others who try to distill elements of that skill into "problems" or "exercise regimes" or such, in order to help others reach mastery quicker. "Problems" never come first.
Also: most "problems" are constructed around a known solution. So another answer to "how did the first humans solve" them is simply, one human back-constructed a problem around a solution, and then gave it to a friend to solve. The problem couldn't be too hard either, as it's no fun to not be able to solve it, or to require too much hints. Hence, tiny increments.