11 ms·
The Mythical Non-Roboticist: Wouldn't it be great if everyone could do robotics?
- TeeMassive 2y ago"Robots are hard because the world is complicated" Or it could be that some problems are inherently hard. Just solving the motion matrix of a simple robotic arm is an academic research field of its own.
- securam 2y agoStop making up new titles. And stop these demands.
- goldfishgold 2y agoAre those demands themselves?
- securam 2y agoYou are so clever.
- koolala 2y ago[flagged]
- koolala 2y ago[flagged]
- eitland 2y agoMore generally, stop copying the smallest-common-denominator DX/UX of <famous mass market product> when designing for other markets. I recently overheard a very smart user struggle to find how to mute a group in Teams. And while I get it that the context menu is probably less "cluttered" if one doesn't include "mute", and I get that there might be confusion if someone mutes a channel without being aware, I still want modern UX to stop and think. When decluttering means you end up having to search the internet for a recipe as to what place to click to find which flydropping menu, was it worth it? Or when your userbase consist of people who go out of their way to avoid Chrome, maybe stop and think if copying Chrome at every step is a good idea? Same goes for a certain distro that at some point thought that their users was just people who couldn't afford Macs and threw out an IMO rather well functioning Gnome 2 setup for a what I consider a clone of the desktop of Mac OS X that had almost all of the problems from Mac OS X but unlike couldn't run Mac OS X software.
- robomartin 2y agoYes, UI's (physical and software) have, in a lot of cases, gone off the rails. One of my examples is the change to the button on the side of iPhone 15 used to switch between vibration and sound-on. I press it all the time by accident just by grabbing the phone. And, often enough, I have no idea I did. So, the phone doesn't ring. Same with the ringer volume up/down buttons. Can I disable them in the lock screen? I don't think so. Once again, the ring volume is modified and you have no clue. The other one, which is a UI issue in the sense that there does not seem to be an obvious way to deal with it, is what happens when I connect my Plantronics single-ear headset. The volume is reduced to around 15%, which is fine. However, when I turn it off, the volume does not return to the prior setting. Which means that EVERY TIME I use the headset for a call I have to remember to raise the volume or the ringer will not be loud enough when the phone is in my pocket. My criteria has become simple these days: If you have to google how to do something with the UI of a piece of software or hardware, something could be wrong. I am not including complex tools like Maya, Solidworks, etc. Let's call those, professional tools. Anything else just needs to make sense. Not sure how anyone thought that not restoring a phone to the pre-headset level was a good idea, or having live buttons in lock mode that you cannot disable (or at least alter the way they respond in some reasonable way).
- p_l 2y agoTeams has probably worst notification handling in my experience out of all major systems in that space. It's not just muting, it's that it's either going to show me big honking unread counts begging for my action, or I have to mute the channel and As Far As I Know mute all notifications from it, even when someone explicitly pings me.
- shrimp_emoji 2y agoIt has all the worst everything in my experience out of all major systems in that space.
- marcosdumay 2y agoYou can get a notification when someone explicitly pings you by enabling an activity for it... (yeah, I know) My issue is stuff like it disabling notifications on the desktop because I turned my phone face-down, or meetings disappearing because... well, I have no idea why. And it delaying messages for hours, again no idea the reason.
- blowski 2y agoOriginal title: > The Mythical Non-Roboticist: Wouldn't it be great if everyone could do robotics? Not sure why it's been changed here.
- ilayn 2y agoIt is sad to see that IEEE is becoming the discovery channel of engineering.
- GuB-42 2y agoWhy are you saying this? It is a message from people who program robots to those who design robots. Both groups are (mostly) made up of professional engineers for which API design affect their job. It is not an article intended to those who know nothing about robotics and are unlikely to become roboticists as it would be the case for a "discovery channel" type article. Note that I have nothing against pop science, quite the opposite actually. But this isn't that.
- ModernMech 2y ago> It is a message from people who program robots to those who design robots. I thought it was a message from someone who designs robots to someone who programs robots. The author says they are an ME and mostly self taught. In my experience, self taught MEs are not adept robot programmers or programmers in general. If I may try to parse the subtext here, this is a post by a ME who is helping manage/direct a startup of recent college grads, and they are frustrated with ROS because you basically have to be a Linux network admin and skilled C/C++ programmer to get anywhere with ROS. MEs especially find it frustrating because they just want to do robots, but to use ROS they have to be expert linux console hackers and it's just not a skillset they have. Same is true for the fresh out of college CS majors -- my students who are seniors, Master's, and even some PhD students have trouble with it. So what I see here is someone expressing that frustration of how tooling is in the robotics ecosystem is not accessible. The reason this is a "discovery channel" treatment of the topic is because we're not talking about it at that level. We're talking about it at this distilled, filtered, high-minded perspective that is above the weeds, when really we should be digging in the dirt talking about exactly the problem here.
- ilayn 2y agoI am in that group you mentioned and this is not even a bad take. They might have been trying to imply ROS but that's also a very much not a well-targeted criticism either. Robotics is not bunch of humanoids moving their attached manipulators. Next; this article appears in IEEE spectrum not Quanta. I want higher quality from IEEE as was the case for decades and it is not a pop science avenue. Good pop science is hard and other places do it much better. This is just a mediocre blog article found somehow its way into IEEE which is very concerning about the quality of IEEE spectrum.
- TaylorAlexander 2y agoCongrats Benjie on getting this published in IEEE Spectrum!
- gtsnexp 2y agoThe "Mythical Non-Roboticist" idea suggests making robotics accessible to everyone by simplifying the programming process is the way to go. However, this overlooks the complexity of getting robots to function in the unpredictable real world. Creating oversimplified APIs for a vague, inexperienced user base leads to tools that fall apart in practical use. Instead of aiming for condescending simplicity, we should focus on developing powerful, flexible tools that eliminate unnecessary complexity. When someone starts programming a robot, they become roboticists, so design your APIs for peers who won't tolerate needless complications.
- darkwater 2y agoThis smells like LLM bot
- jgalt212 2y ago> When decluttering means you end up having to search the internet for a recipe as to what place to click to find which flydropping menu, was it worth it? The Jony Ive aesthetic made so many things harder to use.
- J_cst 2y agoThat's lame llm output
- nonrandomstring 2y agoROS [0] always seems an essential layer if there is ever to be a common ground between something as concrete as motors and sensors, and something as abstract as tasks and learning. [0] https://en.wikipedia.org/wiki/Robot_Operating_System https://en.wikipedia.org/wiki/Robot_Operating_System
- agentultra 2y agoI think this applies equally well to domains other than robots: making comic books, programming (in general), making music, etc. “Democratizing access to skills,” by replacing mastery with a tool always requires sacrifice: of the output, of the input, etc. Sometimes it produces nice results but I don’t see the point of it.
- vouaobrasil 2y agoI think the great tragedy of democratization is that it forces the popularization of a few skills by making it easy for everyone to pursue things because they are popular, rather than because they have an innate ability. Therefore, more obscure hobbies and artistic avenues die out since most people would rather "create" something effortlessly as long as it is popular instead of finding out who they truly are through art.
- MarcScott 2y agoI've taught kids to make line-following robots, with very little code. They are slow, don't handle crossing lines very well, and can often just flip out and do their own thing. I'm not teaching the kids to compete in line-following competitions with robots that can run a course in seconds though. I'm not teaching them to handle multiple crossovers in their code. What I am doing is developing a passion for robotics and programming, and hoping that a handfull go on from there. If they are inspired, they can ditch the simple APIs and move on to the more complex and powerfull stuff.
- paulsutter 2y agoRobotics is on the cusp of total reinvention. Almost everything that it took to make robots work is about to become archaic. The core ideas in old robotics will become a framework for the guardrails for new robotics, but this will widely become a solved problem that few need to think about Stanford Aloha https://x.com/cunha_tristan/status/1743314831912874251 https://x.com/cunha_tristan/status/1743314831912874251 MIT https://youtu.be/w-CGSQAO5-Q?si=kiQ7mBPe6Kh7ZbCq https://youtu.be/w-CGSQAO5-Q?si=kiQ7mBPe6Kh7ZbCq Figure/OpenAI https://youtu.be/Sq1QZB5baNw?si=ZBdDkO2HRT5sOPly https://youtu.be/Sq1QZB5baNw?si=ZBdDkO2HRT5sOPly Tesla Optimus https://youtu.be/cpraXaw7dyc?si=xm-925fFwLeYnkpb https://youtu.be/cpraXaw7dyc?si=xm-925fFwLeYnkpb NVIDIA Groot, https://nvidianews.nvidia.com/news/foundation-model-isaac-robotics-platform https://nvidianews.nvidia.com/news/foundation-model-isaac-ro...
- cwoolfe 2y agoWell said. "Don’t design for amorphous groups. If you can’t name three real people (that you have talked to) that your API is for, then you are designing for an amorphous group and only amorphous people will like your API."
- thriftwy 2y agoI can see uses for robots who comb jellyfish out of water and remove them from the beach. I can also see uses for robots who cut down Heracleum mantegazzianum and ideally make biodiesel out of it. I'm not going to develop or buy either one, though.
- krisoft 2y agoMeh. There is the definition of robots used in academy. Something like "A robot is a machine—especially one programmable by a computer—capable of carrying out a complex series of actions automatically." Or "A robot is an autonomous machine capable of sensing its environment, carrying out computations to make decisions, and performing actions in the real world." And if you go by that definition you see that things like dishwasher, washing machines, elevators, full authority digital engine controls, surface to air missiles are all robots. But nobody, not even roboticist, calls those things robots. You don't need a roboticist to load your dishes, or to get to the floor of your meeting, or shoot down an enemy airplane. The reality is that the real definition of a robot is "a machine which does not work yet". Once it starts working we stop calling it a robot. Making robots for non-roboticist should absolutely be the goal. Giving that up is giving up making reliable useful machines. If you can't make a "grab_object" api useful that is because we all together suck at making robots percept and suck at making robots manipulate things. Once we get good at those (if ever) that API will become easy and commonplace. And anyone who doesn't use it to achieve their goals will feel like a weirdo reinventing the wheel.
- pixl97 2y agoThe AI Effect, but for robots.
- eschneider 2y ago> And if you go by that definition you see that things like dishwasher, washing machines, elevators, full authority digital engine controls, surface to air missiles are all robots. > But nobody, not even roboticist, calls those things robots. You don't need a roboticist to load your dishes, or to get to the floor of your meeting, or shoot down an enemy airplane. I guess I'm a roboticist, and yeah, I call all of those robots. Those are _tantastic_ robots that just get their jobs done.
- Izkata 2y ago> The reality is that the real definition of a robot is "a machine which does not work yet". Once it starts working we stop calling it a robot. Counterpoint: Robot vacuums I think the real colloquial meaning is more along the lines of how constrained or hidden the movement is. Elevators stick to a track, dishwashers only move on the inside, missiles pretty much move on a straight line. On the other hand robot vacuums roam the floor, and while a robot arm is rooted to one spot it can move freely in that range.
- aDyslecticCrow 2y agoThis article reads as a rant about ROS (robot operating system) without mentioning ROS once. Which in their quest to make robotics simple; made json a programming language and made a massive ecosystem of abstracted complexity that breaks in undebuggable ways.
- joe_the_user 2y agoYeah, the article seems like it's several different claims and arguments. Yes, robotic is hard with no general solution visible and with the solutions readily a available to companies turning out to be from people who've spent a decade "squinting" at the problem, know the rules of thumb for a bunch things that work and don't work and still build things that are less than ideal. From this, yes, there are many ways that creating a simplified API in a conventional programming language seems useless. But as an argument against any "turn a hundred newbies loose", it seems not right. It seems plausible newbies to robotics could find paradigms that don't currently exist. I mean, robotics seems to be in the state that pre-deep-learning computer vision generally was in. Nothing worked "out of the box" and you needed experts to make the random smattering of approach that did exist work. Now we have an out-of-the-box working approach and I'm pretty sure it didn't come from existing experts.
- agarwa90 2y agoLike previously said, ROS is not an OS, its a framework for making hardware easily programmable with simple APIs, which happens to be very useful to get started with robots. Sure there is a learning curve like many other frameworks!
- diydsp 2y agomy bg: I have done a few robotics projects: a warehouse robot and a surgical arm. About ROS: that's fair, but to be fair, it was an ambitious first attempt that began hmm decades ago? and has some great parts (the 3d simulator, the robot construction, the python interface) and some less great parts (bags). It's a great place to make the next generation from. Unfortunately, the scope of robot design pain is even larger than TFA! the definition of "robot" is so broad it includes factory robots with hardly any sensor requirements and intelligence, as well as devices with intense vision input, or even large network requirements, micro devices, stationary devices, mobile truck-like things, robotic systems composed of numerous robots, humanoids, etc.
- SamBam 2y agoPrevious discussion on the substack version of the article (114 comments): https://news.ycombinator.com/item?id=39707356 https://news.ycombinator.com/item?id=39707356
- TrackerFF 2y agoI've been under the impression that getting into robotics has never been easier. For the past 10-15 years, high-schools have had easy access to things like Lego mindstorms, etc. Small microcontrollers and computers like Arduino, Raspberry Pi has made development much easier, as you're no longer stuck with writing Assembly or C to get something working, and there are tons of modules that are easy to interface against. Back when I started out playing with robots, as part of my microcontroller and control engineering classes, we were stuck with writing ASM. Same with components, like motor controllers, sensor networks, and what not. Lots of vero and perfboard, lots of soldering.
- spieswl 2y agoBecause it is. There is an abundance of tutorials showing people how to get Gazebo simulations going, or set up a rudimentary classifier in Pytorch, or actuate motors with Arduino using whatever framework of the week (I even wrote some!). The hardware has really made strides too, easy and cheap sensors, controllers, cameras. It's awesome how quickly someone can plug-and-play a Realsense with a servomotor or pneumatic slide and start manipulating the world. The thing that's usually underappreciated is that once you understand how to code a robot, you are barely closer to having solved a practical problem. There are lots of practical problems in the world where spending 4 hours learning how to use $PERCEPTION_API would be actually better spent spending 4 hours understanding more about the widget being perceived or the object being manipulated. Getting into robotics has never been easier, getting something useful out of robotics is still the trick.
- logicallee 2y agoEven a vastly simplified 2D robotics is unexpectedly difficult. I ran a simplified 2D robotics contest to automate code where the task was a simple 2D javascript canvas with a robot that had just two segments that could move (the arm and elbow). A piece of fruit was placed somewhat randomly within its reach, and when its hand was close enough it could be instructed to grasp the fruit. (No grasping code needed to be written, the hand just needed to be close enough) The task was then to bring it to its mouth. There were no sensors involved, the positions were available as global values. About twenty people looked at the contest (number of concurrent viewers on the dedicated subreddit I posted it on) but nobody submitted a successful entry. When I tried to solve it myself, I found I couldn't automate the task either, neither geometrically nor with a neural network, which turned out to be too difficult to train. The closest I got was being able to grasp the fruit about 7 out of 8 times or so (I forget the exact number), without being able to bring it to the mouth successfully. By contrast, solving it by hand on the keyboard (moving the two joints and grasping using keyboard shortcuts) like remote controlling the robot (with a human in the loop) is easy. I had no idea that even such a toy problem with a tiny 2D universe, only two joints, and perfect information, would prove to be so difficult to automate without a robotics framework.
- anticrymactic 2y agoWhy not post the details here? I'd love to have a go at it
- logicallee 2y agoIt was flagged when I posted it originally, so someone didn't like it. (Maybe because I included a $10 prize as a token motivator.) Here is the contest, you can play with your keyboard with a human in the loop (try to bring the fruit to the head using the listed keyboard shortcuts) or you can try to automate it using javascript: https://news.ycombinator.com/item?id=39949966 https://news.ycombinator.com/item?id=39949966 About twenty people looked at it when I posted it but I didn't have any winning entries and I couldn't solve it myself either. If you are very interested you can see a walkthrough of my attempts to solve it here: https://news.ycombinator.com/item?id=39962620 https://news.ycombinator.com/item?id=39962620 I must emphasize that even this very toy, 2D robotics problem with perfect information is very hard, despite being quite easy for a human in the loop. (I tried it with test users, who could complete the task easily with a human in the loop remote controlling the robot.) Let me know if you have any questions or need help using the test environment or understanding the task. You can give me any other feedback you want as well. The contest is finished (with no winners) and there is no longer any prize.
- vitiral 2y agoI'd like some feedback from those in the know. It seems to me we've been building "robots" since the industrial revolution. An assembly line is a series of "robots" performing highly specific actions on highly constrained inputs. So for "learning robotics" I would personally recommend starting with something like assembly lines. Highly constrain your inputs and limit what the robot is supposed to accomplish and you will have an achievable goal. You wouldn't teach programming by telling someone to write a highly scalable dbms, neither should we teach robotics by creating a general purpose "6 degrees of freedom" robot which can grab any object and do something useful with it. Does this resonate with anyone else or am I alone here?
- bigger_cheese 2y ago>Highly constrain your inputs and limit what the robot is supposed to accomplish and you will have an achievable goal. I think this is the key take away. I work in an industrial plant we have a large amount of things that are automated but I would say they are "dumbly automated". For example we have automated cranes. This sounds fancy and sophisticated but the whole system is designed to be as dumb as possible. The Cranes are overhead cranes that run on fixed rails. This immediately limits the degrees of freedom in which crane can move. The whole operation is to pick up object at location A, deposit it at B then travel back to A and repeat. It is always picking up the same objects, with same dimensions/weight etc. The whole thing is designed to be as dumb as possible it does exactly one thing, I imagine if it suddenly had to pick up a different type of object with different dimensions it would require rewrites etc.
- spieswl 2y agoBackground: Started in industrial automation (lots of Fanuc, Yaskawa, Omron, etc.), built a lot of cool systems with cool people that made things with robots. Pivoted to "general" robotics in grad school. Been spending the last 5+ years making "general" robots. I think the best thing for learning robotics looks pretty similar to learning a programming language: Have a specific task in mind that the robot/programming language will help you solve. Even if its just a pick-and-place and a camera, or a shaker table with a camera over top, or a garden watering timer/relay combo. Just work on something specific with your toy robot and you'll naturally encounter much of the difficult things about robotics (spatial manipulation, control, timing, perception, drivers (GODDAMN DRIVERS), data, you name it). Going right to a high-DOF arm or trained LLM is always cool, but the person who hacks together a camera/relay/antenna to automate some gardening task or throws some servos and slides together to make a Foosball robot is doing the most interesting things, in my opinion.
- greenslvio 2y agoindustrial robots are surprisingly simple to program, Fanuc/Kuka etc. with tablet teach pendants and the like. there are even extremely simple ones where no lines of code are required (programmed by human movement). I'm sure these real-world open-ended robots will take inspiration from that, possibly having a general world knowledge but human would need to finetinue/teach movement for specific tasks
- taneq 2y agoThis is just "wouldn't it be great if everyone could program" but with extra kinematics.
- seeknotfind 2y ago> Maybe I should tell them it didn’t work for us. You need to believe to achieve.
- mitchbob 2y agoOriginal version discussed 3 months ago (114 comments): https://news.ycombinator.com/item?id=39707356 https://news.ycombinator.com/item?id=39707356
- kaycebasques 2y agoI'm not knowledgeable to have an opinion on the article but I chuckled at this framing: > Global mutable state is bad programming style because it’s really hard to deal with, but to robot software the entire physical world is global mutable state, and you only get to unreliably observe it and hope your actions approximate what you wanted to achieve. Holson’s Law of Tolerable API Design also has potential: > Design your APIs for someone as smart as you, but less tolerant of stupid BS.
- ozim 2y agoThere is a general idea that people would like a free lunch. At the gym people would like one simple trick to buff. In robotics one simple trick to make whatever they want. I see the same in software where people build behemoths like SAP or other ERP so customer could configure whatever they want and don’t have to hire those expensive developers - just to hire expensive consultants because it is so complex anyway that you need a specialist.