In 3.5 years @extropic:
-reinvented how to use the transistor
-reinvented architectures for probabilistic compute
-reinvented deep learning for thermo compute
-created our CUDA-like THRML
-created our TF-like framework (coming soon)
-scaled our systems 1000x yoy (3 gens of TSUs)
Capitalism, Socialism, Neoliberalism, the Singularity, Transhumanism, e/acc, and even Feminism, are all just modern-day religions hidden behind the guise of political philosophy.
When you see it through the lens of thousands of years of history, they check all the boxes.
Opus 4.8 is a very good model. Claude Code’s system prompts are holding it back.
When combined with Cursor’s harness, it’s exceptionally good at solving novel problems.
Opus 4.8 is a very good model. Claude Code’s system prompts are holding it back.
When combined with Cursor’s harness, it’s exceptionally good at solving novel problems.
Robotics is the perfect amalgamation of Mechanical, Electronics, and Computer Science engineering.
So, if you want to get into robotics, you don't necessarily have to learn all three. You can approach it from the lens of your own expertise.
If you are a Mechanical engineer, you can get into Robotics as a Design, Analysis, CAD/CAM, Composite Materials, Manufacturing, or Additive Manufacturing engineer.
If you are an Electronics engineer, you can get into Robotics as a Power Electronics, Embedded Hardware, Embedded Linux, RTOS, RF, Controls, or Simulation engineer.
If you are a CS Engineer, you can get into Robotics as a Computer Vision, AI/ML, Perception, SLAM, Motion Planning, Navigation, Autonomy, Simulation, Digital Twin, IoT, ROS/ROS2, or Robotics Software engineer.
The beautiful thing about robotics is that no single discipline owns it. Every robot is ultimately a mechanical system that needs to move, an electronic system that needs to sense and actuate, and a software system that needs to make decisions.
Whether you're designing the arm, building the control electronics, writing the perception stack, or developing the autonomy software, you're still contributing to the same machine.
You don't need to become an expert in all three domains overnight. Build depth in your own discipline first, then develop enough understanding of the others to collaborate effectively. That's how most robotics engineers grow anyway. The specialists build the components; the magic happens when they all come together!