Over the past few months, I’ve been dedicating a few cycles of my mind’s CPU to an interesting thought problem which had occurred me while thinking about what success looks like for web development professionals. The problem goes a little something like this:
Let’s suppose I had a “Weird Science”-esque machine, which could fabricrate a perfect tech team leader? What would that leader look like, and how would I expect him to lead?
In my previous post in this series about how I used React.js within my Peabot quadruped robotics framework, I discussed my project and environment setup for working within React.js. I’ll go further in my discussion of the front-end application of my Peabot system in this post, now focusing on some of the rationale I had for the React components involved as well as how the application communicates with its back-end.
It may be helpful as a precursor to this article to briefly skim the RESTful service I’ve written for Peabot in the project’s repository within the readme file. Those methods are used to communicate with the robot, which in turn results in movements from the robot itself (see: video of the robot in action). For now, it should suffice to say that there are POST requests available to make the robot move in each of his cardinal directions, as well as to rotate in place and to do a few other nifty performance tricks.
In my previous post in this series about how I put React.js to use in my Peabot quadruped robot framework project, I gave a brief overview of the project itself. For those who might be interested in learning about React.js, I thought it might be useful to go into greater detail discussing it from a detailed technical perspective.
I will begin by discussing my project setup, as I know it always helps me to have some context as to the environment in which code is written. Likewise, React.js is typically used with a few specific new web development tools which you might find interesting in their own right.
One of the goals I had for my Peabot robotics framework was to feature a front-end web application, hosted directly from the Raspberry Pi at the core of Peabot itself. I intended for the application to be used like a remote control in the same way you would control, for example, a remote control car.
I’ve been working for the past month on a project I’m calling Peabot.
Peabot is a quadruped robotics framework, written in c, which allows the user to control a quadruped robot via a console-based prompt or via HTTP RESTful methods, the latter of which can be accessed through a React.js-based front-end web app I’ve written to control the robot.
This was a bit of a passion project for me, in that many of my recent personal pursuits in the field of computing have been centered around the technologies featured in this project.