The First Automata: Mechanical Intelligence Before Electricity
Categories:
Artificial Intelligence
Categories: Artificial Intelligence
| Mechanical intelligence begins with a structural threshold. A device becomes intelligent the moment its architecture allows it to act without human intervention. The reason this matters is that once a mechanism can execute a sequence on its own, it stops being a tool and becomes a system with agency. What most readers do not realize is that this threshold appears far earlier in history than modern accounts suggest. The earliest automata, astronomical calculators, hydraulic regulators and clockwork mechanisms already implemented the functional categories that define intelligent systems today. They encoded sequences, represented relationships, maintained stable states, regulated periodic motion and separated mechanism from behavior. These machines were complete architectures. Once you see this, you understand that the evolution of intelligent devices is not invention. It is refinement. Ancient automata demonstrated the first appearance of mechanical sequencing. Hero of Alexandria described devices that opened doors, moved figures and executed actions in a predetermined order. A falling weight rotated a drum wrapped with ropes. As the drum turned, the ropes pulled levers and released components in a fixed sequence. The order of operations was encoded in the arrangement of the ropes. Once the weight began to fall, the system continued autonomously until the sequence was complete. This was the earliest form of instruction execution. The mechanism enforced behavior through structure. The lineage to modern control units is direct. The architecture makes the conclusion unavoidable. The Antikythera mechanism introduced mechanical representation. Turning a single input shaft advanced multiple indicators according to precise gear ratios. The device modeled lunar phases, solar motion and eclipse cycles. It computed rather than approximated. The gears embodied mathematical relationships, transforming input into a structured representation of a system. This is not analogy. It is architecture. Modern systems use electronic states instead of gears, but the functional mapping is identical. Representation is a structured transformation from input to output. The Antikythera mechanism proves that representation does not require electronics. It requires structure. The Islamic Golden Age extended mechanical intelligence into regulation and state maintenance. Al Jazari’s devices maintained stable water levels, controlled timing and coordinated multiple subsystems. His float regulators responded to changes in water level by opening or closing valves. The system sensed its internal state and acted to maintain stability. This was feedback control. The mechanism did not follow a script. It responded to conditions. Once a device could sense its own state and act on it, it crossed into a new category of intelligence. The lineage from hydraulic regulation to cybernetic control is exact. The continuity is empirical, not conceptual. The mechanism proves the principle. Clockwork mechanisms introduced controlled periodicity. The escapement converted continuous energy into discrete increments, producing a stable time base. Periodicity enabled synchronization, coordination and long term stability. The escapement was the first system clock. Every modern processor depends on the same architectural principle. A regulated pulse coordinates internal operations. Timing is not an electronic invention. It is a mechanical architecture expressed through new materials. Once you see this, you understand why every intelligent device depends on periodicity. Programmable automata introduced mechanical abstraction. The cam stack encoded behavior independently of the mechanism. Changing the cam changed the behavior. The system became programmable. The mechanism interpreted the representation and executed the pattern. The cam was the program. The mechanism was the execution engine. This was the foundation of software abstraction. Once behavior became a replaceable component, the system became modular. Modularity is the constraint every intelligent device inherits. The lineage is direct. The Renaissance and Enlightenment periods revealed the m oment where mechanical intelligence became unmistakably architectural. The Jaquet Droz automata demonstrated programmable behavior with clarity. The writing automaton used a cam stack to control the motion of the hand. Rearranging the cams changed the written text. The drawing automaton extended the same principle. The geometry of the cams determined the path of the hand. Changing the geometry changed the behavior. Once you see this, you understand that programmability is not a digital concept. It is a mechanical architecture refined through new materials. The mechanism proves the principle. Vaucanson’s automata introduced functional modeling. His flute player used bellows, valves and linkages to produce controlled airflow. The mechanism implemented the architecture of respiration. It did not imitate the appearance of breathing. It implemented the process. Mechanical intelligence advances when devices implement functional architectures rather than superficial imitations. This principle governs modern robotics. A robot does not imitate movement. It implements the architecture that produces movement. The lineage is exact. The nineteenth century introduced mechanical information systems. The Jacquard loom used punched cards to control weaving patterns. The pattern was encoded in the arrangement of holes. The mechanism read the card and lifted the corresponding threads. This was the first widely adopted system that separated data from mechanism. Once data became external, the system became programmable at scale. The punched card was the first mass produced information medium. It was the ancestor of digital memory. The lineage is mechanical, not symbolic. The architecture makes the conclusion unavoidable. Charles Babbage extended this principle into mechanical computation. The Difference Engine performed arithmetic operations through gear trains. The Analytical Engine introduced a store, a mill and a control unit. The system was a mechanical computer. It included conditional branching, loops and memory. The mechanism interpreted instructions encoded on punched cards. The system separated data, operations and control. This separation is the foundation of modern computation. The architecture has remained stable for two centuries. The materials evolve. The structure does not. The Analytical Engine demonstrated that mechanical systems could implement symbolic manipulation. The mechanism did not understand the meaning of the symbols. It manipulated them according to defined rules. The system transformed inputs into outputs through a sequence of operations determined by a program. A device became intelligent when its behavior was determined by an encoded representation rather than by its physical structure. This is the moment where intelligence becomes scalable. Once you see this, you understand why modern intelligent devices behave the way they do. Hydraulic regulators demonstrated regulation. Clockwork mechanisms demonstrated periodicity. Programmable automata demonstrated abstraction. Mechanical information systems demonstrated programmability. These principles formed the architecture of intelligent devices. Modern systems extended these principles through electronics, computation and software. The functional categories remained constant. Intelligent devices sensed, transformed and acted on inputs through designed structures. The origins of these structures were mechanical. The lineage is continuous. The architecture is ancient. The implementation is modern. The study of mechanical intelligence reveals an unavoidable conclusion. The essential characteristics of intelligent devices are not tied to electronics. They are tied to architecture. Sequencing, representation, regulation, periodicity, abstraction and programmability emerged in mechanical form long before digital computation. The continuity is unmistakable. The structure is stable. The materials evolve. Once you see this, you understand that the evolution of intelligent devices is the evolution of implementation, not the evolution of principle. Previous Articles in this Series: Start Here: The Intelligent Machine The First Automata: Mechanical Intelligence Before Electricity The Age of Calculation: From Pascal to Babbage War, Codebreaking and the Birth of Electronic Intelligence Early Robotics: Shakey, Cybernetics and the First Autonomous Machines The Microprocessor Revolution and Embedded Intelligence Early Failures, Hoaxes and Mechanical Deception Smart Homes and Ambient Intelligence Wearables, Health Devices & the Quantified Self Surveillance, Exploits and Smart Device Backfires Embodied AI: When Intelligence Learns to Move |
The Intelligent Machine
Categories:
Artificial Intelligence
Categories: Artificial Intelligence
| For years I have studied artificial intelligence through the lens of governance, institutions, and system design. Yet the more I published, the more one pattern became impossible to ignore. Readers were not asking for more theory or more debate about algorithms. They were asking for clarity about the physical world of artificial intelligence. They wanted to understand the machines that now shape daily life in ways most people never see. The machines that listen. The machines that watch. The machines that decide. The machines that act. The machines that help. The machines that fail. The machines that are becoming autonomous. People want to know where these devices came from, how they evolved so quickly, why they are vulnerable, why they fail in unexpected ways, how they could be exploited, what can be done to protect them, how they reshape society, and what happens as they move toward full autonomy. That is precisely why I am creating this series for The Intelligent Machine. When you examine the history of intelligent devices, a pattern becomes unmistakable. The origins of autonomy stretch from ancient automata to modern embodied systems, and the same architectural principles keep reappearing. This series will trace those foundations, examine the rise of smart machines, explore the evolution of autonomy, analyze the emergence of device free intelligence, and map the scenarios that define our path toward twenty fifty. I am writing this series in public because readers should have a role in shaping it. Your insights, your recommendations, and your critiques will influence the direction of the work. Add your perspective in the comments and share the questions you believe this series must answer. My takeaway Artificial intelligence is no longer only software. It has moved into the physical world. The future will be defined by the devices that sense, decide, act, and learn. Understanding these devices is the only way to understand where intelligence is heading. Previous Articles in this Series: Start Here: The Intelligent Machine The First Automata: Mechanical Intelligence Before Electricity The Age of Calculation: From Pascal to Babbage War, Codebreaking and the Birth of Electronic Intelligence Early Robotics: Shakey, Cybernetics and the First Autonomous Machines The Microprocessor Revolution and Embedded Intelligence Early Failures, Hoaxes and Mechanical Deception Smart Homes and Ambient Intelligence Wearables, Health Devices & the Quantified Self Surveillance, Exploits and Smart Device Backfires Embodied AI: When Intelligence Learns to Move Autonomous Vehicles: The Car Becomes a Robot |
Executives what to know - How is my portfolio doing in terms of Planned Revenue vs Actual Revenue and Planned Expense vs Actual Expense?
| In this article I will cover how to find the Delta between two numbers. A while back I wrote an article where I showed the how to utilized various queries to find difference and commonalities between two data sets. You might want to check it out.
Lets looks at a simple example where an organization is running multiple projects and needs to determine how projects are doing in terms of how the project owners predicted the value of the project will be in terms of planed revenue versus the actual revenue. The same goes to comparing the planned expenses, that will be as part of executing this project, and the actual expenses.
BTW, revenue is not the same as income or profit, we will not cover their differences this article. Simply revenue is a gross amount and income or profit reports the net proceeds.
To find the Delta between the Planned Revenue and Actual Revenue.
Absolute Delta formula: Delta Planned Revenue vs Actual Revenue = Planned Revenue - Actual Revenue Delta Planned Expense vs Actual Expense = Planned Expense - Actual Expense
Relative Delta formula: Delta Planned Revenue vs Actual Revenue = (Planned Revenue - Actual Revenue) / Planned Revenue * 100 Delta Planned Expense vs Actual Expense = (Planned Expense - Actual Expense) / Planned Expense * 100
This will provide the Percent (%) difference between the two numbers.
Here is a dashboard which clearly specifies the difference between planned revenue/expenses and actual revenue/expenses.
Now if you are overseeing the portfolio, you’d better have another dashboard explaining that differences to the executives.
Let me know what are your thoughts In the comments below. |
Memorial Day - A Day of Remembering the People Who Scarified Their Lives
Categories:
Motivation
Categories: Motivation
Today is Memorial Day, an American holiday, honoring the men and women who died while serving in the U.S. military. It was originally known as Decoration Day. The origins of it came years following the Civil War and only became an official federal holiday in 1971.This practice of honoring those who have fallen in battle dates back to the ancient Greeks and Romans who held annual days of remembrance for loved ones which included the soldiers. The first known public tributes to war dead was in 431 BC, when Pericles, an Athenian general and statesman, delivered a funeral speech praising the sacrifice and valor of those killed in the Peloponnesian War.Each of us as citizens of the planet earth have to hold our elected officials accountable from taking our rights away and becoming tyrants causing pain to us and our neighbors and thus avoiding the sacrifices of our brave soldiers. |
5 New Year Resolutions Every Project Manager Should Make and Keep
| It's beginning of the new year and we make grand resolutions that we would fail to achieve. Studies show that by the end of the year only 10% of the people will keep their New Year resolutions. Don't make overarching goals which will be unachievable. I use SMART goal setting: S - specific M - measurable A - achievable R - realistic T - time-bound
Here are my 5 Project Management Resolutions for your New Year: Stay Healthy Learn About Your Team Communicate More Provide Business Value Celebrate Wins
Stay Healthy Staying physical and mentally healthy is not just important for your job but for your life as well. Eat right - more fish, nuts and berries. Coffee - last call before 2pm so as not to interfere with your deep sleep. Hydrate - drink water throughout the day. Exercise - do muscle straightening as well as cardio. Turn off all electronics at least 1 hour before sleep. You'll have better concentration, you will be more creativity and productive the following day.
Learn About Your Team Over the course of the project you will be asking your team to perform tasks so that the project gets completed. What I like to do before the project starts is get to know each person on an individual basis. We all have strengths and weaknesses. I like to help each one on my team to improve on their weaknesses and get their strength to the next level. Have conversations with each member of your team. Observe their behaviors. Are they an introvert or an extrovert. Are they a problem solver or someone who needs a little push.
Communicate More In overseeing programs and portfolios, I find that most project managers only report things that are going well fearing the "shoot the messenger" blow back. What I tell them is: give me the good, bad, and the ugly. That way I can help them break down obstacles that are in their way. Other project owners will do the same. That's our job. Your project owners are looking for ways to help you and will help you remove roadblocks and provide guidance.
Provide Business Value You finish your projects on time, within scope and within timeframe, as well as with the right quality. All too often focusing on the output without understanding why. You need to understand how your project contributes to the overall business. That way you can make better decisions and recommendations during the execution of the project. If you understand the outcome what the project will provide, you will contribute to the business value over the course of the project and not just complete the project successfully. Look at the bigger picture. And ask a simple question: Why? Why are we doing this project?
Celebrate Wins Have you ever noticed how the minute you accomplish one thing you scratch it of your list and go to the next task? You become a robot doing a task after task after task. Celebrating individual and team achievement, large or small, during your project. Provide a meaning, remind the team of the reason for what they have done and accomplished. A simple "Thank You" through the day goes a long way in motivating your team and letting them know that their work matters.
Let me know about your New Year Resolution. |
