this post was submitted on 22 Sep 2025
1059 points (99.1% liked)
Microblog Memes
9285 readers
2548 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
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
Being the devil's advocate here.
Do you guys really understand all of your tools down to the technical level? People can make good use of AI/LLM without the need of understanding NN, weights and biases. The same way as I make good use of a microwave or a rangefinder without understanding the deep levels of electromagnetic waves and so on. Fun meme tho.
This is an extremely basic intro level ML topic. If you cannot even identify a fully connected network (or "MLP") then you don't know anything about the subject. You don't need to know how to hand compute a back prop iteration to know what this is.
This is like claiming to be working as an electrician and not knowing how electricity works.
Someone who uses AI to code or make images isn’t doing machine learning anymore than a pilot is doing aerospace engineering. And someone claiming to be an aerospace engineer can’t say that they don’t understand fluid dynamics.
If someone is claiming to be in the machine learning field, not recognizing a fundamental technique of machine learning is a dead giveaway that they’re lying. This kind of diagram is used in introductory courses for machine learning, anyone with any competence in the field would know what it was.
You're not a "microwave expert". Claiming to be one would imply that you do understand the inner workings. I write code in Java everyday for my job, but I wouldn't claim to be a "Java expert" because I don't have exceptionally deep knowledge of its inner workings.
Usage of a tool does not make someone an expert of a tool. An expert can describe, at least at a high-level, why the tool works the way it does.
Sure but if you make your living with microwaves somehow you should know what a magnetron is/be able to recognize one. You don't have to know exactly how it works but like... This is fundamental stuff.
To further the analogy, if you make your living cooking using a microwave, you better know how one works, how micro-waves propagate, how they interfere with each other (superposition), creating either constructive or deconstructive interference, creating hot and cold pockets, how they are generated and where they come from in a microwave, as well as ideally how heat works... And so on. Otherwise you're just gonna end up with mushy food that has hot and cold spots, and not know why or how to fix the problem.
If I'm claiming expertise (not just proficiency), then yes, I would make it a point to know my tools down to the technical level.