

Every month is a straight pride month. By default.


Every month is a straight pride month. By default.
Vast majority of plants are net consumers of oxygen. Almost no edible plant gives us shade. Farming is technically a net contributor to global warming.
In all fairness, neither did lettuce.


https://youtube.com/watch?v=-X6YzlY_8tM presents a good summary.
https://youtube.com/watch?v=IHD8BDFYyGI is a longer analysis coming at it from a slightly different angle.


The way SpaceX IPO got crammed into index, it’s invulnerable to anything but an immediate incarceration of everybody involved.
Index funds will be required to buy the stocks at a listing price before market can decide how much they are worth exactly.
Afterwards, “economy in a recession” is synonymous to “free buffet” to those at the reins.


What the fuck is quantum AI?


Codeberg or sourcehut.
Gitlab was always cringe.
Left: imagine having slaves !!
Right: ew, slaves !!


Have you ever picked your nose?
You’re good, don’t worry.
The two are not mutually exclusive.
Sexual attractiveness also doesn’t mean sexual drive. One doesn’t need to be gay to understand that a man is sexually attractive in the way they find compelling. A desire to look good is all it takes.
IIRC the goal wasn’t to have a loyal workforce, but to have an army that isn’t dependent on a small number of elites.
Basically “we won’t stop with the death of our officers, our soldiers can step up to the occasion”.
«гр.» is for grams
Senior backend engineering definitely doesn’t see 99% windows adoption rate.
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.


Kids the days… are entirely relatable.
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.
Would you look at that, a wild genocide connoisseur appeared!
Go fucking extinct with your comparisons of human suffering. The only thing you prove is your own lack of morals. The only thing you achieve is total disrespect to those suffering.