Day 1 - Devlog 1
Date - 20 August 2026
Worked - 4 hours and 50 minutes

Today I started “Fresp” from an empty folder. It’s a local CLI. You run a command on your laptop and it does the work there.

I split the code into folders so it’s not one giant file but structured - core (calls the others), drivers (chrome), vision (screenshots + checks), state (saves results), logger, report, types, config.

Got Node set up (package.json, tsconfig). The logger prints a timestamp plus a message and also writes logs/run.txt. State is a scorecard per page - url, passed, notes, screenshot name. Core loops the pages from a heat sheet (a list of paths).

Then Playwright. Real chrome opens, hits a tiny demo I made (home and about). I broke home on purpose with a 4000px red bar so it should fail. About is normal so it should pass. It waits 3 seconds so you can actually see the page, then takes full-page screenshots into fixtures/baselines.

Vision has one real check, not AI: overflow. It asks chrome if the page is wider than the window (scrollWidth vs clientWidth). Home = true / fail. About = false / ok. That’s the point of today, not just pretty screenshots.

It writes logs/last-run.json and an HTML report you open in the browser, so you can see pass/fail without living in the terminal.

I also wrote docs: ARCHITECTURE, VISION (full product: facts first, then AI taste, no cloud dashboard), ENGINEERING (how the AI path should work later, including prompt cache and skip-AI if there’s no key), and taste.md, which is the judgement file (school site vs portfolio vs ai slop, etc.). Taste file + a vision API later is the plan.

GitHub is atireksd11/fresp-ai-tester. I published [email protected] on npm, so in theory npx fresp-ai-tester works. I tried it from another folder and it crashed because tsx was only a devDependency, so strangers don’t get it. I started 0.1.1 and moving tsx into dependencies. Haven’t published that yet, it might work. There’s also bin/fresp.mjs so npx fresp works inside this repo (had to fix a Windows path with a space in the folder name).

What’s not done: the actual ai taste api, more facts (clip, overlap, contrast), VS Code extension, crawling the whole internet, etc.

Next session: Publish 0.1.1 so npx works anywhere. Rebuild the demo so home has several real bugs (overflow, overlap, clipped text, messy theme) and about stays clean. Add those extra fact checks in vision, expand the json so every failure is listed, and redesign the HTML report (colors, screenshots, fact list, room for ai notes). Put product type and goal on the heat sheet, then start the vision api with taste.md (skip ai if there’s no key).

Devlog – Day 2

Date: August 14, 2026
Time Worked: 2 hours

Today I finalized the circuit diagram for my DIY radar speed gun and continued working on the physical enclosure design.

While reviewing the electronics, I discovered that the LM386 amplifier I originally planned to use was not suitable for conditioning the CDM324’s Doppler signal for the ESP32. I researched alternatives, including the MAX9814, but ultimately decided to use an LM358 op-amp breakout board because it provides a dedicated input and can be configured to amplify the signal at 3.3V.

I then completed the full circuit diagram, including the battery, power switch, CDM324 radar sensor, LM358 amplifier, ESP32, and OLED display. I also started designing the main enclosure and planning how the horn antenna, sensor, electronics, and display will fit together in the handheld housing.

Next Steps

• Continue designing the main enclosure.
• Finalize the component placement.
• Review the wiring.

Devlog – Day 2

Date: August 14, 2026
Time Worked: 2 hours

Today I finalized the circuit diagram for my DIY radar speed gun and continued working on the physical enclosure design.

While reviewing the electronics, I discovered that the LM386 amplifier I originally planned to use was not suitable for conditioning the CDM324’s Doppler signal for the ESP32. I researched alternatives, including the MAX9814, but ultimately decided to use an LM358 op-amp breakout board because it provides a dedicated input and can be configured to amplify the signal at 3.3V.

I then completed the full circuit diagram, including the battery, power switch, CDM324 radar sensor, LM358 amplifier, ESP32, and OLED display. I also started designing the main enclosure and planning how the horn antenna, sensor, electronics, and display will fit together in the handheld housing.

Next Steps

• Continue designing the main enclosure.
• Finalize the component placement.
• Review the wiring.

Devlog – Day 1

Date: August 13, 2026
Time Worked: 3 hours 30 minutes

Today I started working on my DIY radar speed gun project. I researched different microwave Doppler sensors and selected the CDM324 24GHz sensor because of its better resolution and ability to detect smaller and faster-moving objects.

I also planned the complete signal-processing system, from filtering and amplifying the sensor’s Doppler signal to processing it with an ESP32 and displaying the calculated speed on an SSD1306 OLED.

I sourced the main components and designed a custom two-stage conical horn antenna in CAD to improve the sensor’s directionality and range. I also researched how horn antenna size affects gain, which helped me set more realistic expectations for the additional detection range.

Next Steps

• Design the main body of the radar speed gun.
• Continue developing the wiring diagram.
• Plan the placement of the electronics inside the enclosure.

Devlog – Day 1

Date: August 13, 2026
Time Worked: 3 hours 30 minutes

Today I started working on my DIY radar speed gun project. I researched different microwave Doppler sensors and selected the CDM324 24GHz sensor because of its better resolution and ability to detect smaller and faster-moving objects.

I also planned the complete signal-processing system, from filtering and amplifying the sensor’s Doppler signal to processing it with an ESP32 and displaying the calculated speed on an SSD1306 OLED.

I sourced the main components and designed a custom two-stage conical horn antenna in CAD to improve the sensor’s directionality and range. I also researched how horn antenna size affects gain, which helped me set more realistic expectations for the additional detection range.

Next Steps

• Design the main body of the radar speed gun.
• Continue developing the wiring diagram.
• Plan the placement of the electronics inside the enclosure.

Devlog – Day 18

Date: August 9, 2026
Time Worked: 2 hours

Today I fixed the wiring issue from my previous session. After tracing through the circuit, I found that the connections were mixed up. Once I corrected the wiring, the servos started responding properly.

I then worked with the Bluepad32 library and wrote code that allows an Xbox controller’s joysticks and buttons to control the servos. I ran into several setup and communication issues, but I worked through them and completed the full controller code.

With the wiring fixed and the code completed, the project is now ready for the physical build once funding is approved.

Next Steps

• Order the required parts.
• Begin 3D printing the robotic arm components.
• Start assembling the arm.

Devlog – Day 18

Date: August 9, 2026
Time Worked: 2 hours

Today I fixed the wiring issue from my previous session. After tracing through the circuit, I found that the connections were mixed up. Once I corrected the wiring, the servos started responding properly.

I then worked with the Bluepad32 library and wrote code that allows an Xbox controller’s joysticks and buttons to control the servos. I ran into several setup and communication issues, but I worked through them and completed the full controller code.

With the wiring fixed and the code completed, the project is now ready for the physical build once funding is approved.

Next Steps

• Order the required parts.
• Begin 3D printing the robotic arm components.
• Start assembling the arm.

Devlog – Day 17

Date: August 8, 2026
Time Worked: 2 hours

Today I started learning how to wire and program servos using an ESP32 in Cirkit. I began with simple push buttons instead of immediately using Bluepad32 and a gaming controller so I could understand the basic wiring and servo control first.

I successfully got one servo working, confirming that my basic wiring and code were correct. I also identified a wiring issue with the other servos that I wasn’t able to fix today. I learned more about ESP32 pins, servo-control functions, and how the different components need to be connected.

Next Steps

• Fix the wiring issue with the other servos.
• Continue practicing servo control.
• Start learning how to use Bluepad32 with a gaming controller.

Devlog – Day 17

Date: August 8, 2026
Time Worked: 2 hours

Today I started learning how to wire and program servos using an ESP32 in Cirkit. I began with simple push buttons instead of immediately using Bluepad32 and a gaming controller so I could understand the basic wiring and servo control first.

I successfully got one servo working, confirming that my basic wiring and code were correct. I also identified a wiring issue with the other servos that I wasn’t able to fix today. I learned more about ESP32 pins, servo-control functions, and how the different components need to be connected.

Next Steps

• Fix the wiring issue with the other servos.
• Continue practicing servo control.
• Start learning how to use Bluepad32 with a gaming controller.

Devlog – Day 9

Date: August 6, 2026
Time Worked: 3 hours

Today I finalized several major aspects of my drone project. I updated the battery system by switching to a 6S Li-ion pack to improve efficiency and flight performance, completed the final bill of materials, and recreated the project’s wiring diagrams after losing my previous work.

I also finished the demonstration video for the drone, adding realistic motor rotation to accurately represent how a quadcopter operates. After reviewing the entire project, I confirmed that the design is complete and ready for the funding and manufacturing stage.

Next Steps

• Apply for project funding.
• Order the project components.
• Begin 3D printing the custom parts.
• Start assembling the drone once the parts arrive.

Devlog – Day 9

Date: August 6, 2026
Time Worked: 3 hours

Today I finalized several major aspects of my drone project. I updated the battery system by switching to a 6S Li-ion pack to improve efficiency and flight performance, completed the final bill of materials, and recreated the project’s wiring diagrams after losing my previous work.

I also finished the demonstration video for the drone, adding realistic motor rotation to accurately represent how a quadcopter operates. After reviewing the entire project, I confirmed that the design is complete and ready for the funding and manufacturing stage.

Next Steps

• Apply for project funding.
• Order the project components.
• Begin 3D printing the custom parts.
• Start assembling the drone once the parts arrive.

Devlog – Day 8

Date: August 5, 2026
Time Worked: 3 hours

Today I continued refining my drone CAD assembly by creating detailed proxy models of the ESC, flight controller, motors, and propellers. Integrating these components into the full assembly gave me a much more accurate representation of the final build and helped verify that everything fits together correctly.

During the assembly process, I identified and corrected several design issues, including screw hole sizing problems and an incompatibility between my planned hardware and the flight controller/ESC stack. I also reinforced key structural areas of the frame while removing unnecessary material in low-stress regions to improve the balance between strength and weight.

Next Steps

• Perform a final review of the complete assembly.
• Create a Demo Video of the build.
• Apply for project funding and order the components.

Devlog – Day 8

Date: August 5, 2026
Time Worked: 3 hours

Today I continued refining my drone CAD assembly by creating detailed proxy models of the ESC, flight controller, motors, and propellers. Integrating these components into the full assembly gave me a much more accurate representation of the final build and helped verify that everything fits together correctly.

During the assembly process, I identified and corrected several design issues, including screw hole sizing problems and an incompatibility between my planned hardware and the flight controller/ESC stack. I also reinforced key structural areas of the frame while removing unnecessary material in low-stress regions to improve the balance between strength and weight.

Next Steps

• Perform a final review of the complete assembly.
• Create a Demo Video of the build.
• Apply for project funding and order the components.

Devlog – Day 7

Date: August 2, 2026
Time Worked: 3 hours

Today I completed the CAD design for my custom drone controller and created a complete assembly to verify that all of the components fit together correctly. Building the full assembly allowed me to identify a few missing parts and small design issues, which I corrected before moving to manufacturing.

I also began creating the project’s wiring diagrams using Cirkit. I completed the full wiring diagram for the drone, including the flight controller, ESC, motors, GPS module, and LoRa receiver. This gives me a clear electrical layout before starting the physical build.

Next Steps

• Complete the controller wiring diagram.
• Perform a final review of the complete parts list.
• Apply for project funding.
• Order the components once funding is approved.

Devlog – Day 7

Date: August 2, 2026
Time Worked: 3 hours

Today I completed the CAD design for my custom drone controller and created a complete assembly to verify that all of the components fit together correctly. Building the full assembly allowed me to identify a few missing parts and small design issues, which I corrected before moving to manufacturing.

I also began creating the project’s wiring diagrams using Cirkit. I completed the full wiring diagram for the drone, including the flight controller, ESC, motors, GPS module, and LoRa receiver. This gives me a clear electrical layout before starting the physical build.

Next Steps

• Complete the controller wiring diagram.
• Perform a final review of the complete parts list.
• Apply for project funding.
• Order the components once funding is approved.

Devlog – Day 6

Date: August 1, 2026
Time Worked: 2 hours 46 minutes

Today I made major progress on the CAD design of my drone project. I completed the drone frame design and brought the custom controller design close to completion. I also built a complete CAD assembly of the frame, including proxy M3 screws, which allowed me to visualize how all the components fit together before manufacturing.

Creating the full assembly helped me identify several clearance, alignment, and mounting issues that were difficult to notice while designing the individual parts. I corrected these problems in the CAD model, reducing the likelihood of print failures and unnecessary redesigns later. I also designed the landing legs, completing the frame’s structural layout.

Next Steps

• Finish the remaining controller CAD design.
• Perform a final review of the complete assembly.

Devlog – Day 6

Date: August 1, 2026
Time Worked: 2 hours 46 minutes

Today I made major progress on the CAD design of my drone project. I completed the drone frame design and brought the custom controller design close to completion. I also built a complete CAD assembly of the frame, including proxy M3 screws, which allowed me to visualize how all the components fit together before manufacturing.

Creating the full assembly helped me identify several clearance, alignment, and mounting issues that were difficult to notice while designing the individual parts. I corrected these problems in the CAD model, reducing the likelihood of print failures and unnecessary redesigns later. I also designed the landing legs, completing the frame’s structural layout.

Next Steps

• Finish the remaining controller CAD design.
• Perform a final review of the complete assembly.

Devlog – Day 5

Date: July 31, 2026
Time Worked: 3 hours

Today I reviewed my drone design and optimized several major components to better match my goal of building an efficient long-endurance quadcopter. I replaced my original motors with more efficient iFlight XING-E Pro 2207 1800KV motors, upgraded to a 4500mAh 4S Li-ion battery for significantly longer flight times, and selected the SkyRC B6Neo charger to support the new battery.

I also continued designing the drone frame in CAD, reaching approximately 50% completion. During this process, I finalized the arm dimensions and confirmed that my Bambu A1 Mini printer and Elegoo PETG filament are suitable for manufacturing the frame without requiring any upgrades.

Next Steps

• Continue designing the remaining sections of the drone frame.
• Refine the CAD model before beginning the first prototype print.

Devlog – Day 5

Date: July 31, 2026
Time Worked: 3 hours

Today I reviewed my drone design and optimized several major components to better match my goal of building an efficient long-endurance quadcopter. I replaced my original motors with more efficient iFlight XING-E Pro 2207 1800KV motors, upgraded to a 4500mAh 4S Li-ion battery for significantly longer flight times, and selected the SkyRC B6Neo charger to support the new battery.

I also continued designing the drone frame in CAD, reaching approximately 50% completion. During this process, I finalized the arm dimensions and confirmed that my Bambu A1 Mini printer and Elegoo PETG filament are suitable for manufacturing the frame without requiring any upgrades.

Next Steps

• Continue designing the remaining sections of the drone frame.
• Refine the CAD model before beginning the first prototype print.

Devlog – Day 3

Date: July 29, 2026

Time Worked: 3 hours

Today I refined the hardware design for both the drone and the custom controller. I switched to the Heltec WiFi LoRa 32 board for the transmitter and receiver, finalized the controller’s battery setup, and continued planning the drone frame.

I also confirmed the motor mounting hardware, selected M3 nylon standoffs for mounting the flight controller stack, and evaluated using a PLA+ frame instead of carbon fiber to reduce cost and manufacturing time.

Next Steps

• Continue designing the drone frame.
• Finalize the frame material.
• Design the controller enclosure.
• Review the parts list.