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

  • 0 Posts
  • 157 Comments
Joined 3 years ago
cake
Cake day: September 27th, 2023

help-circle



  • I use them for a bit of coding leverage, and they require a fair bit of… not hand holding, but explicitness, maybe. Otherwise they wander down the path of statistical averageness, and the average code they saw during training was shit.

    So they’ll happily serve up a pile of inefficient dogshit, complete with working tests and docs and all of that. And then they’ll happily refactor it at your suggestion to slowly turn it into something that’s resource friendly and generally secure and generally expandable.

    But there’s no way for them to do that by themselves if you don’t have the basic domain knowledge to guide them in the right direction. You’ll just get average code, and once you’ve been in the game for a few decades, you realise that nice, efficient, quality code is the rarity, not the norm.










  • It’s often not possible on other operating systems. Especially the consumer versions of a certain operating system starting with “W”, that system will refuse to have duplicate IPs.

    But essentially it’s always been possible (but, probably not preferred these days) to have redundant routes/paths on Unix systems. The way you have it now is more of a side effect of being able to do more complex network setups, like using different interfaces to talk to different subnets, or using a slow link as a backup to a fast link.

    With your current setup you should get a slow failover ability, for example if you ping some other device and then unplug your Ethernet cable, you’ll have a bit of a pause in replies and then they will start again as the stack switches to the other link.


  • The “metric 600” on your Wi-Fi adapter indicates to the system that it is a higher cost route than your Ethernet one. So the IP stack will prefer sending packets out via the Ethernet port.

    Local devices who haven’t heard from you lately will send to whatever device gives them a response to their ARP (“who has IP address X?”) request first, and seeing as Ethernet is lower latency than WiFi, they will mostly use your Ethernet adapter as their target when sending data to you.

    Devices that have received data from you already will have the MAC address of your Ethernet adapter in their ARP table, so they’ll just send packets to that without bothering to issue an ARP request.

    Devices off your subnet talk to your router, so they don’t care about your MAC address, they’ll just use IP to talk to your router, who will then do the ARP request and hand the packets on to your computer via whatever interface answers first.




  • that has the potential to

    Of course it has “the potential to”, that’s the whole fucking point of this change.

    The compute hardware required to give you that obsequious-chatbot-on-demand is phenomenal. AI as a whole has been burning billions upon billions of dollars getting to these lofty heights where it’s alleged that everyone’s job is threatened, any day now.

    And now’s the time to get to the other side of the equation, the dreaded return on investment, where people have to pay what it actually costs. Plus a modest amount for that actual return of course, that’s the thing that all those investors actually want.

    Whether Microsoft has actually managed to get enough people hooked on the particular brand of crack they’re selling is questionable. In any case it’ll be fun to watch at least.




  • Do not remove my spam

    If I want to find something, I’ll look for it.

    Don’t dump a truckload of unsolicited information in my inbox/workflow/field of view.

    Otherwise you’re as bad as door to door religious folks. Oh yes, I’ve heard about Jesus, thanks. Now let me get back to what I was actually doing a few minutes ago before you begged for my attention.