I’m @froztbyte more or less everywhere that matters

  • 13 Posts
  • 766 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle
  • a good post all over, and something that’d be a good thing if other people also introspected their use of these things in a similar manner. I get why they don’t, ofc (good lord so many tired people), but it’d be nice

    now every time you use the Google Assistant, you get a popup that compels you to switch to Gemini.

    this is one of the things that is so very mindbending for me. to me it is so very obvious that: because all of these things are a service, because the shape of service is subject to the whims of the organisation creating it, because that organisation will always feel the pressure of “market forces” (or in the more recent case, product desperation), these things will almost every[0] damn time result in some shit that an end-user cannot control. and yet that same person ends up reliant and expectant on these things, only for it to be ripped from their grasp, in a manner that may well amount to it being “murdered” in front of them

    the state of where we’re at with “service-shape” as it pertains to sociological impact is just very not good atm :|

    [0] - I hesitate to say “always” here, but it’s more or less what I mean







  • best advice I’d have for you is continuing with python is fine but

    1. find a good mentor
    2. read a lot of sourcecode (both good and bad), reason through stuff, try to understand the decisionmaking behind things

    on the good, you could read code by people like glyph, hynek, projects like twisted. they have years of experience, high mark of quality, care for their work, and also do a lot of teaching

    on the bad, you could read something like the code to home assistant (and/or esphome), or bits of calibre code (and calibre plugin code). I will say that these are not bad intentionally, but bad out of “someone inexperienced trying their best”. it ends up creating a very particular kind of other thing.

    you can, and should, learn from both

    µPython is a bit of a special beast in that it’s juuuust close enough (and handy enough) that it can trip you up, because there’s some notable significant differences that if you spend all your effort in it first you might pick up bad habits that don’t apply elsewhere (off the top of my head, some of the applicable: scoping, some arg-handling semantics, stack stuff)

    other bit of advice: remember, it’s all just code. especially when you deal with libraries, if some error is coming out of a thing your first instinct may be to try ask the internet but you could also dive into the library - follow the callpath, figure out what’s what, see if you can figure the problem out yourself. it’s often not too hard, and it gives you some good practice of code reading and reasoning


  • frankly, it’s really not a good idea to early-years kids assembly (double especially not fantasy assembly), if your goal is to encourage learning the field. this is why all the strong/popular pi-based educational distros and options focus on stuff like scratch, some light python (often paired with light pygame and turtle), and other low-entry-effort exploratory things like sonic-pi

    many do come to explore programming topics in depth later (asm via zach games, other structural/dependency things via satisfactory/factorio, etc), and that’s fine too

    there is of course a longer-term balance to be struck with (and structural problems coming from) people not understanding the layers below them (cf. current nightmare of tottering piles of javascript and continually worsening app performance everywhere despite having literal supercomputers in our pockets), but “learn asm” is bad starter advice for the same reason that “you should know how to write in c” has been part of why we’re in this fucking mess in the first place