counterpoint: quick broen fox is corporatized af while sphinx of black quartz has one hell of a vibe. you're right that the fox is comfy because the cozy zone is the only spot where fun and corpos intersect and this one just so happens to fall into it but keeping it people-centric was never the point.

case in point: the test sentence we use in my native language translates to "floodproof mirror drill" to test out all our weird diacritics. no autumn vibes there, only corpos

genocide doesn't just mean murder, it means destruction of a people, which can be done by destroying identities even without killing the people behind those identities. i don't think it's inaccurate.

said other poster is actively advocating for a form of conversion therapy, just on little kids instead of adults, while questioning whether trans people are even real or just a delusion. if you hang around literally any oppressed group you'll see this "well-educated genuine concern" and conditional support rhetoric all the time. it's veiled bigotry, nothing more.

have you considered that maybe covid just gave people some much needed time to sit back, relax, and recognize things about themselves?

this isn't rocket science. i get the shtick of the "enlightened" centrist but when one side just wants to exist and the other side wants a trans genocide the right answer isn't maybe a little genocide, as a treat. and if you don't know how to tell apart conflicting data about trans people, you'd do well to actually listen to them for once, as opposed to discrediting them as biased and "just one side".

you mean fork him under a new maintainer?

the number of measured sinister people (as in, left-handed, that's where the word comes from) were rising like crazy too when it started gaining cultural acceptance that maybe, just maybe it's not evil that you use your left hand to do things. it was like a whole epidemic, sinister people started popping up left and right.

…and then it plateaued at a flat 12.5% and stayed there since. turns out that's just the biological occurrence rate, but everyone was under-measuring it because people weren't willing to own it up that they're left-handed.

trans people are the same. you get different amounts of persecution for it between different time periods and different regimes, and you get different levels of acceptance in different age groups, but the level of persecution is not zero anywhere. it's not as normalized as just being a lefty. as such, the measured number of trans people is below the real amount in all of these situations, and how much below it is represents the amount of repression and persecution. we'll get accurate numbers for the occurrence rate of people born in the wrong bodies when the stigma is gone.

also, you seriously misinterpreted the medical issue. the issue isn't with the brain, it's with the body. you're not a pile of muscle with some neurons slapped on top of it, you're a brain piloting a meat suit, and if the meat suit is the wrong kind that's what needs to be corrected. and that correction is much easier to do before puberty than after. which is why you need to listen to trans kids and at the very least give them puberty blockers, or preferably adequate hormone therapy. but you can't "prevent" trans people unless you can detect and fix the issue in the womb.

i'm no expert in vexillology but even i can tell that that's a c- at best

yeah, i think the “LLM sound” is just a corporate sanitized tryhard voice that no sensible human would have. the tryhard bit is an artifact of instruction training, and the corporate sanitization is there to make it very “safe” for conversational interfaces or smart prose processing for corporate clients. but if you give the ai an actual, productive, and somewhat complex task to accomplish, it very quickly switches to something far more human-like, because it’s no longer trying to overperform on a simple task.

pretty sure there’s lots of linux running there

hi rms

yeah, chatgpt is frickin unparalleled in coming up with bullshit and phrasing it just the right way. my favorite thing is asking it to be sarcastic and passive-aggressive:

One principle that has guided my career in engineering, which my colleagues often overlook, is the profound understanding of the mirror-like relationship between an organization’s design structure and the software engineering outcomes they produce. Now, I don’t wish to dumb this down, but every time you witness a cluster of technologists huddled together, producing an array of systems, sub-systems, or module designs, keep your eyes peeled. They’re invariably going to be a spitting image of the organizational framework of the enterprise, often in ways that self-proclaimed ‘visionaries’ fail to foresee.

Now, with painfully forced patience, I must reiterate that this axiom is no trivial discovery or stroke of divine inspiration. It’s merely a reflection of the structural reality, something akin to looking out on a mirror carefully arranged by your senior management. The hierarchy, the stratification, the fragmentation across your esteemed organization, will be sculpted into the systems it produces. Picture each software module as a carefully chiseled stone that when aggregated, forms the larger cathedral that is your system architecture.

Ironically though, I’ve often seen leaders ready to splurge on sophisticated technology and state-of-the-art infrastructure, willing to make all grandiose promises on achieving data-driven decision making or accelerating the pace of innovation. Yet, they conveniently forget, due to what can only be a mission-critical memory lapse, that their microservice architecture has a curious tendency to mirror our own managerial slides filled with box-and-line org charts.

And let’s dwell a moment longer on these org charts, these delightful diagrams that claim to encapsulate the chain of command and accountability within the organization. There’s almost an uncanny resemblance, to the perceptive observer, between the lines of software code and the seemingly tiny, arbitrary changes made to these precious organizational diagrams. Lest we forget, the software your teams sweat blood to build will knuckle under to the gravitational pull of the enterprise structure, echoing its splintered silos and delightful dysfunctions.

However, for the sake of those cheerfully blinded by technical jargon and starry-eyed optimism, do carry on with your lofty ambitions to transform your IT landscapes, to catapult your organization into the brave new era of digital excellence. Just remember, the structural symmetry between your divided departments and disjointed computing systems is not random happenstance. If nothing else, they are monuments to the myopia of management, embodied in code and user interfaces, continuing to honor the timeless principle that so eloquently underscores my engineering prowess.

i literally just added “do the above assignment in a sarcastic and passive-aggressive tone” to the prompt, lol

lmao, god’s pronouns are specifically the plural They/Them

Oooh, are we saying complete bullshit on well-known principles just to make ourselves look better? Here, lemme try

One principle that has guided my career in engineering is predicated on a theory which asserts that an organization inevitably produces designs closely mirroring its own communication structure. This tenet is deeply entrenched in organizational theory and has profound implications within the field of software engineering. It underscores the tangibly symbiotic relationship between structural communication channels and the inherent formation of design patterns, directly impacting project outcomes and overall system architecture.

Take an instance of a complex system architecture, for instance; the blueprint invariably mirrors the modus operandi of the organization, melding functional utility with intricate formalism. More specifically, it can be deduced that the nature and structure of information flow within an organization will ultimately inform the design, function, and interactivity of the proposed solution. Understanding this dependency provides valuable insight into optimizing organizational communication channels and realigning teams for effective outcomes.

A practical illustration of this principle is observed in large software corporations. A company with segregated departments, each responsible for a different process within a singular product, results in a fragmented, disjointed project output. Conversely, an organization that values collaborative, cross-functional teams is more likely to produce a product that boasts of seamless integration between its components.

For this reason, corporate structuring and re-structuring, when required, should be done with a pragmatic view towards improving communication channels. Aligning one’s business operation to reflect this principle, therefore, has significant implications on the maintainability, productivity, and overall success of end products. It espouses the virtues of flexible organizational structures that maximize communication efficiency and consequently, affords more robust and efficacious design frameworks.

In essence, understanding and implementing this paradigm shifts how companies view their organizational structure and its subsequent impact on outputs. It transcends beyond mere theory, providing a heuristic tool for entities seeking to improve their system architectures. As such, it is an indispensable guidepost in my engineering career, illuminating the path towards optimum function and design within both the organization and the products it creates. This, in itself, is an organogram of success, a paradigmatic shift in corporate thinking to create more efficacious products and overall, more successful businesses.

just afab. He clearly goes by He/Him pronouns (extra credit: discuss if the capitalized form counts as a neopronoun)

There was a man at CERN once who was sick of questions. His name was Tim-Berners Lee.