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

help-circle


  • Electric current moving through a wire creates a magnetic field. Creating that magnetic field is work and takes energy. If it has to do a lot of work, that energy all gets stored in the magnetic field instead of in the load. Then if the electric current stops, the magnetic field collapses and dumps its energy back into the wire. That’s impedance. It behaves like the electricity has been delayed and slowed down but it cannot be explained and understood as electricity alone like resistance or capacitance can, it is an electromagnetic phenomenon and can only roughly and imperfectly fit into an electricity-only model. The devil’s in the details, and reactance is the devil’s name.



  • Memorization is just repetition, and you can build successes and reinforce it for yourself by keeping things very, very small. If even a “simple number guessing game” is too complicated for you to remember at this point, that’s not a mark of shame, it might sound simple but one of most important things you can learn as a programmer is that a lot of things that seem or feel simple really aren’t. There’s sometimes a lot of hidden complexity, and your brain needs to form the internal tools it needs to unpack and untangle that complexity. Eventually you’ll develop the skills you need to see the specific issues making it more complex, but for now, all you can do is simplify. If there’s a part you’re not remembering how to do, discard it. Make it a sidequest. Iterate on one feature at a time, test it and see if it works the way you expect. Refine, and you’ll learn a little bit from each refinement. Keep doing little refinements and you’ll start learning stuff more permanently. It’s like any skill, you have to practice.

    If you read through a foreign language dictionary page by page, of course you’re not going to remember all the words. It’s huge. It’s overwhelming. Our brains can’t learn that much in a single pass. It’s all about doing little bits at a time. The absolute minimum required to get off the ground. Gradually, not overnight, you’ll learn it all.

    There’s a reason the stereotypical “first program” is:

    print(“Hello world”)

    It’s actually a good starting point. It’s all you need to get started, plus the workflow you need to compile/run it, which shouldn’t be changing a lot once you’ve got it established. Other than that, you can build tiny baby steps on top of that. How do you print “Hello again” after “Hello world”? Does it print on the same line or does it print on the next line? Try it out and find out. Learn what it does. Play with it. What’s next? How do you let the user type something? Maybe you need to look for some examples. Try them. Not just the first one that works, try them all. See if they do anything differently. Don’t copy and paste huge complicated messes of code blocks if you don’t understand them, because you’re getting back into the “reading the dictionary” problem, but a line here or there is something you can start to pick apart and understand what it’s doing as you go. Use your programs to explore and understand what the program is doing, not to create a “finished product”. Nothing’s ever really “finished” except by accident when at some point in the distant future you realize you haven’t needed to modify it in ages. Otherwise, programs are things you change as you go, and you learn something each time you change them.


  • AllTheMods has plenty of progression options that are reasonably casual but also quite deeply technical, at least depending on what path you choose to pursue. They tend not to be the kind of modpacks that force you into too narrow of a progression path, so as long as you can trust yourself to intentionally explore some new mods instead of falling back on familiar patterns, they’re generally a very friendly and well-made experience (and because they’re AllTheMods, you’ll probably also have a wide selection of comfortable, familiar mods to fall back on if you get stuck with some aspect)

    Without knowing too much about what you like and what you’ve tried before, that would be my recommendation. I can try to suggest some others if you want to go a bit deeper into what you’re looking for. How deeply have you played around with Create?






  • Not personally. I prefer to run bare metal whenever possible. It helps me understand how everything connects, it’s the difference between being handed someone else’s completed Lego sculpture and building it yourself, it takes a lot longer but you’ll have way more appreciation for it after building it and a much more thorough understanding of how it’s all put together and what’s involved, and you’re a lot better equipped to fix it if a piece breaks off.



  • I use a single centralized database running directly on the host (postgres) and make it accessible to the docker clusters.

    Pros: It’s all in one place to backup all important data for every service, I find this a much easier and more reliable way to backup all services, and I’m confident if you tried it you would too. The application data becomes a first-class citizen instead of hiding inside some nameless docker volume. Significantly less database overhead. Consistent database version and tools.

    Cons: Lots. You need to manage and backup the database. You need to manage the database users and passwords too. Making the DB accessible to the docker clusters is nontrivial and can be fragile. You can no longer use the default “official” docker compose files, since they will almost never support an actual database service without several modifications, they’re always built for spinning up their own docker container database. So you’re going to be doing a bunch of work setting up users and passwords and performing extensive surgery on the docker-compose before you even start up the application, which adds a lot of friction, with lots of opportunity for error. All things considered, it’s actually quite painful. Technically if one application abuses your database hard enough and exhausts its memory to crash it or something it would affect other applications too, but that’s true of any services running on shared hardware abusing anything on that hardware, so it’s not a realistically concerning con.

    I consider it worthwhile, but I might be wrong. Also I hate docker in general. I understand why people use it. It’s the same reason I use it. But I still hate it. I think system installations are so much easier to manage in the long run, but initially more work, and you need to invest that work at a time when you’re not even sure if you really want to run this application or if it’s going to be compatible with the rest of your environment. So docker is the easy solution. But then you’re basically trapped in dockerland. It’s not that bad, I just hate it in principle. I wish there were a better way.




  • If you have an option in the BIOS or drivers to set the battery charging threshhold to stop charging at 80% or possibly even lower (I believe Lithium Ion/Polymer cells are happiest at around 40-60% state of charge, which is why they are usually shipped that way). Sometimes this feature exists, but only vaguely described as “battery life optimization” or some similar wankery that they never properly explain.

    You can also just remove the battery entirely if it will be always plugged in, but setting it to a low/modest maximum charge gives you a nice, reliable, built-in UPS in case of power interruptions.


  • If this is about the bot I think it is, I haven’t personally complained but I have noticed it’s weird and often wrong, it seems to detect HTTP/HTTPS in every post (perhaps seeing links and URLs?) and it seems to maybe possibly be detecting any words with those strings of letters somewhere in them and presumably also doesn’t care about case sensitivity? The short ones in particular like “AP”, “CA”, “CF”, “HA” and “IP” seem to come up frequently almost every time it posts, and “NAT” and “IoT” seems common, and none of things seem to be actually mentioned in any of the comments that I see.


  • cecilkorik@lemmy.catoSelfhosted@lemmy.worldNextcloud or Seafile alternatives?
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    4 months ago

    I am questionning using it only for myself and use something else to share with family

    I’m confused, you don’t want your family to be able to know each other’s email addresses? That seems like a bit… extreme level of profile paranoia.

    I have my family on my Nextcloud and I can guarantee 90% of them don’t even know where their own user profile is nevermind anybody else’s. Maybe you have a different family than mine.