b3nsn0w

and yet you should be allowed in a kfc? double standards smh

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

they spent 10 figures on openai already. 8 figures for the whole openai team is pennies

yup, and when in doubt, just do some few-shot prompting

do you have an example of the russian federation getting attacked by a near-peer adversary without the now defunct soviet union defending it?

no, the premium stuff doesn’t give you api access. which is total bs, but yeah, it’s only for that grey interface. (i’m also quite salty that the playground has no easy to access image inputs but that’s beside the point)

you’re completely right about self-hosting sd, it’s just a matter of prompting. sd workflows tend to get a little more experimental but i guess you could still make chatgpt write a few prompts that are close to correct and just manually rerun if an image failed

you can already api into chatgpt and dall-e 3 as one cohesive service, and make a system in an afternoon’s work that reads the article, decides on a thumbnail, and automatically generates one. the whole thing costs like 8 cents per article.

baldur’s gate did that and other companies were complaining about the high standard it set

yup. anti-piracy is about control, not profits. this is trivial to deduce from the simple fact that no one ever measures a drm solution’s performance in total sales recovered, they only ever whine about hypothetical lost ones, which is the corporate equivalent of sideways for attention, long way for effect

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

yeah, let’s just put all the important tools in the hardest to reach spot on the screen

top makes sense on desktop, but on phones bottom is just logical. took way too long to get to it already because of the exact notion you expressed

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)

basically just a phone number you can call and it autoplays rickroll for you. i don’t have it unfortunately, seen it ages ago and never wrote it down

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