• 1 Post
  • 375 Comments
Joined 3 years ago
cake
Cake day: July 14th, 2023

help-circle
  • Beautifully put.

    I especially like that they called out the “it’s just a tool” BS:

    Yet technological artefacts cannot be separated from the conditions under which they are created, or from the realities of who controls and profits from them. Today, developing these technologies expands racial capitalism, intensifies imperialist extraction, and reinforces the divide between the global North and South. The technology is inseparable from the labour that produces it — the expropriation of work by writers, artists, programmers, and peer-production communities, as well as the highly exploitative crowdwork of data annotation.



  • Big agree.

    But also: people seem to only focus on the output side of the task of writing code, and forget that the developer also receives input from the codebase in return.

    Even if you end up with exactly the same code artifact after completing a work item, you’ll have a better understanding of the codebase without delegating swaths of it to AI. But bosses tend not to consider this.

    Tech bros have successfully convinced people that mental states do not exist, or at least do not matter — for laborers, anyway, cuz they’ll happily claim that their superior thoughts are exactly why they deserve to be billionaires.















  • kibiz0r@midwest.socialtoCanada@lemmy.caBan Religion
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 days ago

    True. I’m just reading between the lines here, because of the phrase “until there is verifiable proof”. If it applies to god, then it applies to privacy of conscious experience, in which case… well, we have done pretty horrific things in the past because there was no verifiable proof of someone’s conscious experience, like performing surgery on infants without anesthesia.


  • kibiz0r@midwest.socialtoCanada@lemmy.caBan Religion
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    11 days ago
    • That’s unethical, but even it it wasn’t…
    • There’s no way to satsifactorily define religion in the way I think you’re going for, but even if you could…
    • People would worship their gods anyway, but even if they didn’t…
    • They would worship something else instead (see the ongoing AI cult for live evidence!), but even if they didn’t…
    • It wouldn’t suddenly make everyone empathetic, non-tribal, morally consistent, rational physicalists, but even if it did…
    • Physicalism is for edgy teenagers who haven’t taken the p-zombie question seriously (source: was edgy teenage physicalist)

  • I was once a fool like you :)

    Mike McShaffry’s book “Game Coding Complete” is a good guide to the practical side of using a game engine IRL to get things done.

    It’ll give you a good idea of how things should be shaped in order to be useful, and some things you can “skip ahead” to. Off-the-shelf engines have to be extremely general in order to be flexible enough to be useful to many customers, so game devs have to put in the effort to make them more specific. You’ll have to start off by being specific, if you have any chance of actually finishing something.

    Eberly’s book “3D Game Engine Architecture” deals with the nuts and bolts, the rigorous academic engineering stuff. It’s pretty solid, but it’s aimed at making a general-purpose engine, which is beyond the scope of a one-person project.

    Backing up though… You don’t have any language or library opinions? You might need 5-10 years of experience doing general programming (or game dev) before you can sustainably tackle this, or else you’re likely to paint yourself into a corner.

    Edit: Probably the biggest PITA with game engine dev is testing. If you’re not already an expert in setting up test harnesses at multiple levels of detail, you’re gonna find it impossible to keep moving after a few months.

    Good luck!