Background
I study Computer Science and learn best by following a system past the API boundary. On AnthonyCS that has meant building browser tools, maintaining a Linux/Nginx deployment, and iterating CAPY from an Arduino Mega proof of concept to an ESP32 handheld.
Most projects start with a capability I want. I build a usable version, run into a real limitation, then change the design around what the system actually needs.
How I approach projects
My usual loop is simple: build the project, run it, find the constraint, measure or debug it, and revise the design. That is why projects on AnthonyCS tend to have multiple generations instead of ending after the first working version.
Software and systems
My current software work includes C/C++, data structures, browser tooling, Linux, and server infrastructure. I also deploy and maintain AnthonyCS myself, including Nginx, HTTPS, permissions, and production updates.
Hardware direction
My long-term direction is embedded systems and digital hardware, then FPGA/RTL and ASIC/SoC work. I am building the prerequisites now through C/C++, computer architecture, digital logic, microcontrollers, and hardware/software integration.
CAPY
CAPY is one of the main projects through which I explore hardware and software integration.
The project is intended to evolve over multiple hardware and software generations. Each revision provides an opportunity to reconsider constraints such as memory, processing power, display bandwidth, physical controls, storage, power, usability, and system organization.
Learning through iteration
One of the most valuable parts of independent development is being able to revisit earlier decisions.
A system that works is not necessarily a system that is well designed. As my knowledge grows, I can return to previous projects, identify weaknesses, restructure components, measure improvements, and understand why one design works better than another.
Long-term goal
My goal is to develop into an engineer capable of working across software and digital hardware, particularly in embedded systems, computer architecture, FPGA development, and ASIC / SoC design.
I want the projects documented here to show that progression over time: not only what I built, but how my technical understanding and engineering judgment developed with it.