Well, they do it Japanese style - by forcing developers to leave due to burnout.
Well, they do it Japanese style - by forcing developers to leave due to burnout.
I’m working with a legacy codebase for the last few months, where a simple PR often ends up crossing a 1000 lines count due to testing and commenting, and I can’t stop apologizing for those.
Yet there are people out there bragging about 10x changesets.
I made my statement as a BDD/TDD practitioner.
The code goal of software engineering is not to deliver said code, but to deliver it in a framework that lets others—and consequently me in a week’s time—to contribute easily. This makes both future improvements and bug fixes easier.
Dumping a ~25000 lines changeset with a git history that’s almost designed to confuse is antithetical to both engineering and open source.
The size of that changeset means that it’s inherently unreviewable.
The commit history is something I’ve seen only in the PRs that even the most dysfunctional companies would demand a rewrite for.
Also, 2-3 weeks review? PostgreSQL support could be added in that time without the need for a damn „vibe check”. Hell, it would probably take less time than that.
we age due to our telemere buffer shortening
Telomere shortening is a marker and there is a correlation, but aging is a process that happens on multiple levels and many of those aren’t fixable by DNA restoration.
We experience wear and tear, we accumulate damage, we accumulate waste, we lose body parts, we constantly fuse our bones together, we have body parts that grow surrounded by tissues capable of maintaining them but then operate outside of them, the list goes on.
But most importantly, death is such a beneficial feature, that it outcompeted everything else. Producing new generation of individuals regularly is a simple and terrifyingly effective solution to a vast array of problems. Many aspects of aging can be seen as adaptations to inevitability of procreation and death.
That aside, I like pointing people at professor Michael Levin’s work. Be very skeptical, as it’s a small field in a world that goes through reproducibility crisis, but it does fill me with a cautious hope.


Well, IIRC it’s not indirectly. Sam Altman negotiated pre-purchase of massive chunk of wafer supply, which OpenAI backs up with its virtual money.
So DRAM manufacturers are facing a wafer shortage in near future. Which translates into prices now.
Cue sheets are important.
Heracleum sosnowskyi in Ukraine. Fucking commies decided to start seeding it en-masse for cow feed without even checking whether it would work.
It bitters the milk, making it unusable as feed. It is poisonous and hybridizes with native edible species. Skin contact results in horrible blisters that tend to not heal cleanly. Its juice is toxic and mutagenic.
A war crime in plant wrapping.


The windows have all the modern anti-burglary features and the plumbing is immaculate
— excerpt from a sale advert for a house with its front wall missing and the living room exposed to the elements


The market can stay irrational far longer than you can stay solvent.


Oh the fucking irony!
Did you lose track of the written words after the first question mark perchance?
Every bit of code a maintainer accepts becomes their responsibility to maintain. Considering that half the time „improvements” don’t even have tests to help maintaining them, feel free to maintain your own fork.
„How do you know” is such a powerful question.
I especially like the Electrolux one. It’s simple, memorable, and once you see a butt and bikini, you can’t unsee it.
Thanks, I hate it!


A naive answer:
Replace “Lemmy” with a “Nazi manufactured gun”.
A less naive answer:
Consider various meanings “use” takes in your question and decide accordingly.


First, Omarchy doesn’t need funding or partners. It’s backed by a Nazi multimillionaire.
Second, the whole apolitical argument is bullshit. Everything is political. Support for a distro that doesn’t really need support by nature of being a child of a Nazi multimillionaire is a support for that Nazi multimillionaire.
“We didn’t support them because of that” means nothing. The support still sends a message. Just like artist loses control over interpretation of their art the moment they release it, people lose control over interpretation of their actions the moment they act. Does it sound fair? Maybe not, but it’s how reality works.
He’ll rather gain strange kinks. Losing weight with Polish cuisine is impossible.
Power users rebase with squashes and fixups multiple times a day. Especially if the job’s integration process isn’t enforcing long living branches.
Reflog is useful then, because you literally rewrite history every rebase.
Senior backend engineering definitely doesn’t see 99% windows adoption rate.