• 0 Posts
  • 12 Comments
Joined 7 months ago
cake
Cake day: April 13th, 2026

help-circle

  • I teached embedded programming for a while and students were to find out that AI often failed miserably at our tasks.

    And the funny thing is that when I tried it myself to see if it’s that bad at given tasks - I explained the task like I would explain to a student, and actually got a decent result - readable comprehensive code with meaningful comments. It all simply comes down to the fact that AI won’t really help you if you can’t do without it. So I double that making the guy pass some guidelines on styling the code to Claude should at least make the code less shit to debug.






  • Yep, people involved are the biggest problem sometimes.

    I’ve had to figure how to fix many issues myself, because quite often upon finding a thread where someone already had an issue that I had, folks were tryna gaslight the OP why it’s not actually an issue, eventually turning the thread into shit flinging contest. Or the good old “don’t do that, you’ll break something” (that I proceeded to do and was absolutely okay).

    Not to mention how FOSS developers have to deal with entitled assholes every now and then.



  • ivan@piefed.socialtoProgrammer Humor@programming.dev•Beastly
    link
    fedilink
    English
    arrow-up
    4
    ·
    5 months ago

    If you’re very new to that - I’d just recommend picking up some Arduino (at least UNO R3) starter kit plus some measurement tools - multimeter and maybe an oscilloscope (there are cheap handheld ones like DSO).

    And then you just fool around with what you’ve got - try to read each sensors data, try to use each actuator, think of some useful projects with what you’ve got.

    And from there you can go to stuff like ESP32 to explore wireless stuff (mostly compatible with Arduino too).