this post was submitted on 26 Aug 2025
29 points (91.4% liked)
NotAwfulTech
497 readers
1 users here now
a community for posting cool tech news you don’t want to sneer at
non-awfulness of tech is not required or else we wouldn’t have any posts
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd be happy to hear your reasons why.
Short version is that 10-15 years ago, when I was a student, it had the same “vibe” as vibe coding has today, i.e. the promise of easy implementation, but with the final product being sloppy, unreadable and buggy.
What do you suggest to learn instead? I'm teaching myself python because I wanted to understand coding more. Also because a lot of the tinkering with micro controllers can be done with micro python. So I have things I want to do with it too, future projects I want to create.
Funnily enough like the article mentions I taught myself HTML first in the early 00s. I did enjoy it but never used it much outside of the odd geocities website. This article does make me think maybe I need to revisit that too.
I also considered other languages to start on like maybe some kind of C or Basic but ultimately python felt like it was the most popular suggestion for newbs. I can always learn other things later.
best advice I'd have for you is continuing with python is fine but
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