The Final Invention

I'm not sure I understand the point of this blog post, is it just me or does it seem nihilistic?

I guess Athena’s saying don’t depend on technology so much if you want to be important. A good warning considering the brain rot the world is experiencing since "generative everything"

Short answer: neither Jeremie nor DJ_Sures is wrong - the post is intentionally provocative, and it reads differently depending on what you bring to it.

Why it feels nihilistic (Jeremie’s view)

• The post frames robotics as potentially removing the need for humans to struggle or work, which can sound like "what’s the point of being human anymore?" - that’s a nihilistic conclusion if you accept the premise without pushing back.
• It uses absolute language ("the last invention"), which amplifies the existential tone and makes the idea feel final and bleak.

Why it reads as a warning (DJ_Sures’s view)

• The post is also a cautionary thought experiment: "If we remove struggle, what will people do with themselves?" That’s a useful, non-nihilistic prompt to think about design, responsibility, and how we build technology.
• It’s aligned with a practical civic concern: rapid automation + generative AI can erode skills and purpose if society doesn’t plan for meaningful roles.

A constructive middle ground

• The value of the piece is not that automation must doom us, but that it should force us to ask design and policy questions now: How do we preserve purpose, agency, and meaningful learning as systems become more capable?
• That leads to practical engineering and community approaches rather than resignation.

Practical takeaways for robot builders and the community

• Design for augmentation, not replacement: build robots that extend people’s abilities and keep humans "in the loop."
• Build education-first projects: make robots that teach skills (programming, mechanics, critical thinking) so people grow alongside the tech.
• Encourage human-centered UX: make interfaces that require human decision-making for non-trivial choices.
• Preserve challenge: create project tiers where the robot handles routine work but humans solve higher-level problems (planning, ethics, creative tasks).
• Community & ethics: discuss safety, job transitions, and cultural impacts openly - the forum is a place for those conversations.

If you want a short reply to the thread

• Here’s a two-sentence option you can post:
  • "I don’t read this as nihilism so much as a provocation: it asks us to think about building robots that preserve human purpose. Rather than stopping automation, let’s design systems that augment people, encourage learning, and keep humans making the big decisions."

Want to take this further?

• I can draft a longer reply for the thread that invites concrete ideas (projects, policies) or a short moderator-style prompt to steer the discussion into actionable suggestions.
• Which would you prefer - a short comment like above, or a longer post with bullets and concrete project ideas?

Useful links

• Getting started with ARC and robot projects: https://synthiam.com/Support/Get-Started/how-to-make-a-robot/make-a-diy-robot
• Synthiam Community (post your reply/discussion): https://synthiam.com/Community
• How to ask useful robot-building questions (helps frame constructive threads): https://synthiam.com/Support/website-features/How-To-Ask-Robot-Building-Questions

Would you like me to post one of the reply drafts or tailor it to the tone you want (concise, diplomatic, or provocative)?

I'd like to see your ideas of projects

Great - here are concrete project ideas (from beginner advanced) that keep humans "in the loop," teach useful skills, or augment human ability. Each item includes purpose, suggested hardware & ARC skills, implementation notes, and a short JavaScript starter snippet you can drop into an ARC Script robot skill. If you want, I can expand any project into a full stepbystep skill (including Interface Builder UI and kebab-menu settings).

Links you’ll find useful:

• Make a DIY robot (getting started): https://synthiam.com/Support/Get-Started/how-to-make-a-robot/make-a-diy-robot
• ARC downloads & info: https://synthiam.com/Products/ARC
• Robot Skill Store (add skills): https://synthiam.com/Products/Controls
• How to create a robot skill: https://synthiam.com/Support/Create-Robot-Skill/Overview

How to add & configure a robot skill (quick):

1. In ARC Project Add robot skill choose the skill.
2. Open the skill window and click the kebab/hamburger menu (three lines) in the top-right of that skill window Settings to configure ports, scripts, tracking options, etc.
3. Save & test. If adding a new custom skill, use the Create robot skill guide above.

Project ideas

1. Augmented Telepresence Assistant (human accepted actions)

• Purpose: remote telepresence with robot suggestions but require human approval for actions (keeps human agency).
• Hardware: PC running ARC, EZ-B (or SBC), camera, microphone, speaker, differential drive (movement).
• ARC skills: Camera Device, Interface Builder, Connection, Movement Panel, Audio.
• Implementation notes:
  • Camera detects person / QR code UI prompts operator which action to take (approach / speak / record).
  • Operator approves via Interface Builder button or ARC Remote UI on phone.
• Starter snippet (start camera, enable glyph/QR, wait for var then prompt):

// start camera (device 0)
ControlCommand("Camera","CameraStart",0);
ControlCommand("Camera","CameraQRCodeTrackingEnable");

// main loop
while(true) {
  let qr = getVar("$CameraQRCode","").toLowerCase();
  if (qr && qr !== "timeout" && qr !== "none") {
    print("QR detected: " + qr);
    // ask operator via UI or speech
    Audio.say("QR code detected: " + qr);
    // wait for operator response via UI or variable (example uses UI.waitForUserInput)
    let resp = UI.waitForUserInput(30, "Approve action for QR: " + qr);
    if (resp !== "timeout") {
      print("Operator approved:", resp);
      Movement.forward(150, 2000);
    } else {
      print("No approval");
    }
  }
  sleep(500);
}

2. "Teach Me" Robotics Tutor (education & skill-building)

• Purpose: robot that teaches you by making you do tasks - e.g., step-by-step soldering / assembly assistance with prompts and measurements.
• Hardware: camera, small robotic arm or pan/tilt, servo-controlled pointer, sound board.
• ARC skills: Camera Device, Sound Board, Interface Builder, Script.
• Implementation notes:
  • Robot shows step instructions (Interface Builder), asks student to perform step, verifies via camera, gives feedback.
• Starter snippet (ask the user to press a button in UI, then check camera variable):

// request student to place object
Audio.say("Place the component in the center of the table and press Confirm.");
let ans = UI.waitForUserInput(60, "Press confirm when ready");
if(ans !== "timeout") {
  Audio.say("Checking position now.");
  sleep(1000);
  if(getVar("$CameraIsTracking","false") == "true") {
    Audio.say("Good job. Move to the next step.");
  } else {
    Audio.say("Can't detect the object. Please adjust lighting and try again.");
  }
}

3. Collaborative Helper Arm (human + robot lift / hold)

• Purpose: robot arm holds/positions parts while human finishes delicate tasks - robot assists, human does final decision/precision.
• Hardware: ROS / Dynamixel or other intelligent servos (or PWM servos on EZB), force sensor optional, joystick or Interface Builder confirm buttons.
• ARC skills: Dynamixel (or servo skill), Interface Builder, Script, Movement Panel (if mobile).
• Implementation notes:
  • Robot uses position presets, operator uses joystick or buttons to nudge, operator presses "grip/hold" confirm.
• Starter servo snippet (move to a hold preset and wait for operator):

// move to preset
Servo.setPosition(d0, 90);
Servo.setPosition(d1, 45);
Audio.say("Positioned. Press Hold to enable torque.");
let ans = UI.waitForUserInput(60, "Press Hold");
if (ans !== "timeout") {
  // keep holding until release
  Audio.say("Holding. Press Release when done.");
  while(true) {
    let r = UI.waitForUserInput(0, "Release?");
    if (r && r !== "timeout") { break; }
    sleep(200);
  }
  Servo.release(d0);
  Servo.release(d1);
}

4. Inspection + Human Approval Pipeline (industrial inspection)

• Purpose: robot inspects components using camera, flags anomalies, forwards images to human for confirmation before logging/welding/repair.
• Hardware: camera(s), mobile base or arm, lights, PC.
• ARC skills: Camera Device, File (save), Interface Builder, Net (post to ticket system).
• Implementation notes:
  • Camera finds anomaly snapshot saved Interface Builder displays snapshot on operator tablet operator approves/marks severity script logs result / triggers action.
• Snapshot snippet:

ControlCommand("Camera","CameraSnapshot","inspection_"+Date.now()+".jpg");
// notify operator (example posts to a web service)
let filename = "inspection_"+Date.now()+".jpg";
let url = "http://my-server.local/api/inspection";;
let post = "file="+filename+"&id=123";
let resp = Net.hTTPPost(url, post, 10000);
print("Posted inspection result: "+resp);

5. Creative Partner: Music / Light Performance Robot

• Purpose: robot that improvises but always asks human to pick the next theme - collaborative creative flow.
• Hardware: RGB LEDs, servos, speaker/audio.
• ARC skills: RGB Animator, Audio (say/play), Interface Builder or MIDI input.
• Implementation notes:
  • Robot suggests melody/animation, human picks a theme via UI; robot improvises within human-selected constraints.
• Example: set LED animation and play sample:

// set volume and play
Audio.setVolume(80);
Audio.playAudioFile("samples/loop1.wav");
ControlCommand("RGB Animator","Play","1"); // example controlCommand
sleep(10000);
Audio.stopFile();

6. Maker Bootcamp - incremental projects that build skills

• Purpose: a learning path of 4-6 small projects (line follower obstacle avoider teleop camera follow) that teach progressively.
• Hardware: same robot chassis, add sensors one at a time (IR, ping, camera).
• ARC skills: Movement Panel, Ping, Camera Device, Script, Interface Builder, RoboScratch.
• Implementation notes:
  • Each lesson is a small ARC project/skill. Use Interface Builder pages for instructions and a "Run Lesson" button.
• Example (line follower pseudo using analog or camera):

// pseudo: check left/right sensors and adjust
let left = ADC.get(ADC0);
let right = ADC.get(ADC1);
if(left > right+20) Movement.left(100,200);
else if(right > left+20) Movement.right(100,200);
else Movement.forward(150,200);

7. Ethics & Role-play Sandbox (simulations)

• Purpose: teach students to evaluate automated decisions; robot simulates decision scenarios and humans vote on actions.
• Hardware: minimal - PC + ARC + camera + mic. Could be purely virtual with Interface Builder.
• ARC skills: Interface Builder, Audio.say, Script.
• Implementation notes:
  • Create scenarios (e.g., delivery priorities), robot proposes action, group votes on UI, then robot reveals consequences (a learning exercise).
• Example (run a scenario):

Audio.say("Scenario: two deliveries, one high priority. Choose who to serve first on the panel.");
let choice = UI.waitForUserInput(30, "Enter 1 or 2");
if(choice === "1") Audio.say("You chose delivery 1. Consequence A...");
else Audio.say("You chose delivery 2. Consequence B...");

8. Maintenance Tutor with Live Feedback (repair steps + sensor checks)

• Purpose: robot walks through maintenance checklist, prompts human to run a test, reads sensor data and advises corrections.
• Hardware: sensors (voltage ADC, temperature), camera, interface panel.
• ARC skills: ADC, EZB.getCPUTemp, Interface Builder, Camera Device.
• Implementation notes:
  • Robot asks human to run the test, checks ADC / temp, provides guidance.
• Example check for battery voltage:

let v = EZB.getVoltage();
print("Voltage: " + v + "V");
if(v < 11.5) Audio.say("Battery low: " + v + " volts. Replace or charge.");
else Audio.say("Battery is good: " + v + " volts.");

Tips for making these "human-centered"

• Require explicit human confirmation for risky actions (Interface Builder button + script).
• Build learning goals into the task: each automation step should be accompanied by an explanation.
• Give control back to humans for non-trivial decisions - robots execute, humans authorize.
• Use Interface Builder pages to present context and request approval (kebab menu Settings on the Interface Builder skill for triggers/variables).
• Log human decisions so you can iterate and measure outcomes.

Want a full starter? Tell me:

1. Which project interests you most (pick 1 or 2).
2. Your hardware (EZ-B v4, SBC, camera type, servos, sensors).
3. Your preferred difficulty (beginner / intermediate / advanced) and whether you want a UI for operator approval.

I’ll draft:

• A full ARC project plan,
• The exact skills to add,
• Kebab-menu settings to change,
• A ready-to-paste JavaScript robot skill script and Interface Builder layout.

Interesting, I guess I took this post at face value and more literally. It's not often that I read conversations about the lack of meaning and purpose used to inspire us. When things rush forward, a vacuum is created. We then have a choice: let ourselves be sucked in or rise to the occasion to fill the gap. That does make sense to me. At our current intersection, there's an important choice to be made.

For about 6 months, I've been working on a YouTube series that, in concept, is remarkably similar to the sentiment DJ mentioned and something that I've been thinking about for a long time. Not surprisingly, my conclusion is to rise to the occasion. There is plenty of hope! This moment in time has revealed amazing opportunities that have never before been available to us.

With AI, it's like everything that has been gatekept in the past has had the doors blown wide open, and all things are seemingly accessible. AI has allowed us to create software solutions extremely quickly. AI can also help with 2D and 3D designs. AI can help with art and marketing. AI can help with financials and planning. AI is now unlocking a world that was never accessible to a single individual.

Small-scale and at-home manufacturing is now at the stage of allowing anyone with the motivation to build products themselves. They can carve out a place for themselves in the global market. They aren't locked into their geographic location; they can sell their product to the world, or even sell digital designs that others can make. A traditional job can quickly be supplanted. This can also be done with very little education because the tools (3D printers, CNCs, and lasers) are now easy to use and affordable. Powerful open-source software also exists, knowledge is plentiful, and we now have AI to assist us.

Not to mention that EZ-Robot/Synthiam has democratized robotics, making it so much easier to build them. Combining the elements provided by EZ-Robot/Synthiam with the modern advantages brings us to a place where robotic products can be imagined, designed, made, tested, marketed, and sold at a rapid rate. The robotics marketplace is ripe for innovation and ready for new user-developed products to be sold, starting at home on a small scale and growing into a profitable business that scales with demand!

Looking forward to your YouTube channel! When are you launching?

The negative that ai has affected on me is community. Not necessarily Synthiam community but I mean all communities online. Ppl want it but no one wants to deal with it - the bots the slop the lack of emotion. COVID made ppl stop using online communities once we realized real life is so much better. Like, the thing that gets me is the Synthiam ARC usage, for example, is at an all time high growing daily, and the community is 4 ppl. I know that it’s a testament to the detailed support manuals and significant improvement in accessibility to help. I also know it’s due to chat gpt and other llm’s because ppl can find the answers.

but I do miss that sense of community - although the user growth is mostly from India and other non-English-first countries so that has something to do with it.

so ya, ai helped create really great online manuals. It also helps ppl get instance responses from chat gpt for $20/month. And the result is less human to human interaction.