Who reads this anyway? Nobody, that’s who. I could write just about anything here, and it wouldn’t make a difference. As a matter of fact, I’m kinda curious to find out how much text can you dump in here. If you’re like really verbose, you could go on and on about any pointless…[no more than this]

  • 0 Posts
  • 84 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle

  • Hamartiogonic@sopuli.xyztoTechnology@lemmy.worldUnsmart a smart TV
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 months ago

    Just found some LG business TVs/displays/signage that actually run Tizen. Remember that cool Linux distro that was supposed to take over the mobile world nearly 15 years ago? Well, turns out, it didn’t, but it didn’t it die completely either.

    Hopefully those panels are a bit more hackable or more privacy oriented.









  • In my experience, Copilot does a fairly good job when you already know what you’re doing, but can’t be bothered to write the code yourself.

    For example, basic stuff like read data from that file, use dplyr, remove these columns, do these calculations, plot the result using ggplot2, label the axes this way, use those colors etc. Copilot gives you the code that does roughly what you want, but you usually need to tweak it a bit it to suit your preferences. Copilot also makes absurd mistakes, but fixing them is fairly easy. If this is the sort of stuff you’re doing, copilot can indeed boost your productivity.

    However, if you don’t know how to do something a bit more exotic like principal component analysis, and you ask copilot to do the job for you, expect plenty of trouble. You may end up on a wild goose chase, using the wrong tools, doing unnecessary calculations and all sorts of crazy nonsense. When you know what you’re doing, you can ask a very specific thing. When you don’t, you may end up being too ambiguous in your prompt, which will result copilot leading you down the wrong path.

    You can do it this way too, but before implementing a single line of that garbage code, you absolutely have to ask copilot a bunch of questions just to make sure you really understand what you’re doing, what the new functions do, where do you really want to go etc. You’re probably going to have to tweak the code before running it, and that’s why you need to know what you’re doing. That’s the one big area you can’t outsource to copilot just yet.

    But is it still faster than reading the documentation and building your own experimental tests? If you spend an hour and get a pile of broken garbage, then certainly not. If you spend a bit more, ask plenty of questions, make sure you know what you’re doing, then maybe it is worth it.