I’m a software engineering developer from Ottawa, Ontario, Canada.

  • 1 Post
  • 19 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle





  • Lambda@lemmy.catoMemes@sopuli.xyzBet
    link
    fedilink
    arrow-up
    5
    ·
    1 month ago

    My embarrasing case of this was when I accidentally started using “up in this bitch” as part of my vocab. As a tenth grade white kid at a private school in Ontario. :/ It legitimately got to the point that I was abbreviating it as UITB (pronounced like You Whitby).



  • Thats exactly what I so often find myself saying when people show off some neat thing that a code bot “wrote” for them in x minutes after only y minutes of “prompt engineering”. I’ll say, yeah I could also do that in y minutes of (bash scripting/vim macroing/system architecting/whatever), but the difference is that afterwards I have a reusable solution that: I understand, is automated, is robust, and didn’t consume a ton of resources. And as a bonus I got marginally better as a developer.

    Its funny that if you stick them in an RPG and give them an ability to “kill any level 1-x enemy instantly, but don’t gain any xp for it” they’d all see it as the trap it is, but can’t see how that’s what AI so often is.








  • I think self hosting the proxy with the services at hobbyist scale mitigates most of the security risks. The single point of failure risk is another matter. I once had to effectively reverse-hack my services by uploading a Jenkins test job through an existing java project to regain access. Ever since then, I maintain a separate ddns address that’s just used for emergency ssh access.





  • Sadly front end, like “High Level” is a very relative term. For example, in compiler design, the bit that parses code is called the “front end” since the “back end” is what emits machine code. I think that’s what they mean here, the “front end” that understands D3D8 code has been added, presumably there is also a “back end” that converts the parsed/analyzed D3D8 code into valid opcodes for consumption by GPU/CPUs.

    In the other direction, a UI/UX is sometimes called a “back end” when it is part of a more complex embedded project where physical controls are the “front end”.