I’m a technical kinda guy, doing technical kinda stuff.

  • 0 Posts
  • 71 Comments
Joined 1 year ago
cake
Cake day: September 27th, 2023

help-circle
  • Effective advertising has a clear and simple visual language, and this is what UIs should strive for.

    Interfaces can be needlessly complex regardless of being flat or skeuomorphic.

    But flat interfaces still require mental effort to parse. Especially when the interface is complex and/or crowded and you’re trying to pick out active UI elements amongst decorations like group boxes/panels.

    Essentially, flat interfaces are currently popular because of touchscreen devices. Touchscreen devices have limited space and thus need simplistic UI elements that can be prodded by a fat finger on a small screen.

    But I don’t need a flat touchscreen-friendly interface on my non-touch dual 24" monitors with acres of screen real estate. I need an interface that nicely separates usable UI elements from the rest of the application window. That means 3D hints on a 2D screen, which allows my monkey-brain with five million years of evolved 3D vision the opportunity to run my “click the button” mental command as a background process.










  • Blu-Ray USB drive and M-Discs is about the best you can get at present. Keep the drive unplugged when not in use, it’ll probably last 10-20 years in storage.

    Seeing as there hasn’t been much advance past Blu-ray, keep an eye out for something useful to replace it in the future, or at least get another drive when you notice them becoming scarce.





  • Letting it ring has no impact. They have autodiallers that call, and when someone picks up, only then is that call assigned to someone in the call centre.

    You can often tell this because there is a marked delay in the response to your initial “Hello?”. Long enough that you can reliably just hang up if you don’t hear a response in two seconds.

    If it’s a real person who actually wants to call you and they you call again straight away, you can just shrug off your hang-up as a network issue.


  • Dave.@aussie.zonetoLinux@lemmy.mlCompanies that use desktop Linux
    link
    fedilink
    arrow-up
    38
    arrow-down
    1
    ·
    3 months ago

    how the IT team tries to justify being locked into Microsoft, and then telling me I could potentially become a point of vulnerability

    Because they can manage and control all the windows PCs , pushing updates automatically, restricting what users can do locally and on the network, they have monitoring tools and whatever antivirus and antimalware tools they have, and are able to easily manage and deploy/remove software and associated group licensing and so on and so forth.

    Meanwhile you’re a single user of unknown (to them) capabilities that they now have to trust with the rest of their system, basically.

    The first rule of corporate IT is, “control what’s on your network”. Your PC is their concern still, but they have no effective control over it. That’s why they’re being a bit of a pain in the ass about it.


  • Dave.@aussie.zonetoProgrammer Humor@lemmy.mlStop
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    3 months ago

    There was a series of books in the '80s where a systems programmer gets pulled through a portal into your typical magical world, good vs evil, etc.

    They subsequently look at the magical spells in use and realise they can apply Good Systems Programming Practices™ to them. And thus, with their knowledge of subroutines and parallel processing, they amplify their tiny innate magical abilities up to become a Pretty Good Magician™. So while all the rest of the magicians basically have to construct their spells to execute in a linear fashion, they’re making magical subroutines and utility functions and spawning recursive spells without halting checks and generally causing havoc.

    It’s quite a good allegory for modern times, where a select few build all the magic and the rest just have useful artefacts they use on a day to day basis with no idea how they work



  • Have a look here at the ICMP source code in the Linux kernel at line 400. That is the ICMP reply code.

    At lines 433/434 you can see the collection of the source and destination MAC addresses from the incoming packet. The source is just lifted directly from the packet, the destination is done with a helper function that presumably looks at which interface it arrived on and returns the MAC address of that interface.

    Lines 441 onwards construct the reply packet and push it to the generic ICMP transmit function (which is a bit higher up in the source code), which then pushes it on to the network stack.

    Hope that gives you an idea of how it works internally! It’s really only a slightly more detailed version of the actual standard, there are a few checks to make sure that we are not exceeding network rate limits in the stack and etc, but it’s a quite simple bit of code.

    Added edit: it’s “simple” at this point because a lot of the work has already been done. The packet has arrived via the network stack, it has been determined to be an ICMP packet, and it was sent here to this function. There are already functions that send packets out via the network stack, so this chunk of code just builds an appropriate packet and hands it on to be sent.