|
7251
|
My awesome macropad! by @Sasindu25 | Stardance
|
Sasindu25
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Sasindu25 | Starda Title: My awesome macropad! by @Sasindu25 | Stardance...
|
1793382751.5853415
|
1793987551.5853415
|
|
7252
|
Untitled project by @naghul | Stardance
|
naghul
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @naghul | Stardance
|
1792691580.432995
|
1793296380.432995
|
|
7253
|
Untitled project by @bhivourdevnath | Stardance
|
bhivourdevnath
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @bhivourdevnath | Stard Title: Untitled project by @bhivourdevnath | Stardance...
|
1792954297.2858377
|
1793818297.2858377
|
|
7254
|
My awesome macropad! by @Abhinav_Boopathy | Starda My awesome macropad! by @Abhinav_Boopathy | Stardance...
|
Abhinav_Boopathy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Abhinav_Boopathy | Title: My awesome macropad! by @Abhinav_Boopathy | Stardance...
|
1793267687.248196
|
1793872487.248196
|
|
7255
|
Feverdream by @Emanutz | Stardance
|
Emanutz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Feverdream by @Emanutz | Stardance
|
1793346482.302457
|
1793951282.302457
|
|
7256
|
Untitled by @faustina | Stardance
|
faustina
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @faustina | Stardance
|
1792691284.6781907
|
1793296084.6781907
|
|
7257
|
My awesome macropad! by @e45g | Stardance
|
e45g
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @e45g | Stardance
|
1793350161.0379133
|
1793954961.0379133
|
|
7258
|
tyse by @tawhidulh1 | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: tyse by @tawhidulh1 | Stardance
|
1792684398.0886316
|
1793289198.0886316
|
|
7259
|
AI Hardware by @doenertrinker | Stardance
|
doenertrinker
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI Hardware by @doenertrinker | Stardance
|
1793314496.2181928
|
1793919296.2181928
|
|
7260
|
Nebula by @CVictor | Stardance
|
CVictor
|
0
|
46.14
|
0
|
[]
|
[{"post_id": 56455, "ts": "202 [{"post_id": 56455, "ts": "2026-08-28T07:01:12Z", "hours": 16.0547, "text": "For the past few weeks, I have been working on the hardware of my project. All components has been soldered onto the PCB and all pieces has been printed."}, {"post_id": 48712, "ts": "2026-08-17T07:05:20Z", "hours": 9.2172, "text": "CAD, Soldering, PCB design, all at once. Its been a busy month so I have been building all the progress bit by bit. Major updates and Progress: -Change MPU 6050 to LSM6DS3 -Get rid of the servo arms on both side -Functioning Webpage to control the bot via bluetooth. LSM6DS3 is overall a more reliable that the commonly known MPU 6050 The servo arms were not that important function wise but they took up too much space on the PCB layout, hense I remove its. The webpage is hosted via github and currently it can connect to esp through bluetooth and design patterns for the matrix led that serves as the face of my robot. Pretty much all, I am currently in the process of accumilating all the necessary hardware and materials. Hope I can post a build log soon on my Instagram page @vtr_lab , consider following!"}, {"post_id": 32837, "ts": "2026-07-22T07:28:39Z", "hours": 1.8131, "text": "Working on CAD and Assembling hardware."}, {"post_id": 23248, "ts": "2026-07-06T02:45:49Z", "hours": 10.1858, "text": "Finished Routing My PCB: Process: STEP 1. Check all schematics STEP 2. Use auto routing function, define the thickness or trace for each type of trace: eg. 11.1V-1.25mm, logic-0.254mm, 5V-0.9mm……etc. STEP 3. Skip the routing for GND nets STEP 4. Adjust any wiring STEP 5. Pour Copper layer for the grounds —————————————————–The process sounds easy, atleast that’s what I though at first, but here are some things that I learned and challenges encounter in the process: Schematics is the easy part, do it well and it could you could save alot of time in the routing section. When letting the software to handle auto-routing, make sure to leave out the GND nets so make the wiring less complex. Route the GND nets at last with copper filled layer to ensure all grounds and securely connected. Issue encounted->Isolated island As posted in the image, even after pouring in the GND layer , there still is a ratline between the ground port of C7 to other components, meaning the ground of the part is not connected. This is a common issue for auto routing other nets first , ignoring ground and make it an isolated island. Solution: To fix the problem, I swap the position of C7 and U8 so that the C7 will not be caught in the connectionof U8 to my ESP which is the main reason why C7 is electronically isolated. After that, we can simply regenerate the ground copper layer to fix the issue. Issue encounted-> Antenna Clearout: Since my project will rely heavily on RC control, I need to clearout the copper ground below the antenna part of my esp as the double copper layer could potentially block radio signal. That’s it for now, the design final reaches “DRC(0)” and now I am adding silktouch design to the bottom layer for the final touch before sending the file for production!!!!! . . . See yall later."}, {"post_id": 18183, "ts": "2026-06-29T07:25:37Z", "hours": 2.5339, "text": "Polishing My Schematics, AGAIN!!! Since My previous schematics relied heavily on net ports, it becomes hard to understand the relationship between components as I moved on to the routing part. Therefore, I am now going back to the schematics and check the wiring block by block. Current Progress: Power Block Sensors and Servos MPU6050 Stepper Driver Logic / Pinout of ESP Stepper Motor Currently(2/6). Checking progress includes tiding up wires and use more wires instead of all net ports. Checking amounts of decoupling capacitor needed for each component. Making sure that each individual block of components can run (electrically). Yeah, hope I get back to routing soon and finish the PCB, also, I want to gather some idea for PCB art for my first functionable PCB, so submit any ideas through commenting on this dev post of consider following vtr_lab on instagram(I am close to having more post than followers😭😭). Thanks alot~ 2026/6/29, Victor"}, {"post_id": 14929, "ts": "2026-06-24T07:47:17Z", "hours": 0.7333, "text": "Finalizing schematics and layout before routing- Problems encounter: clearing messy schematics, double checking component layouts, making sure the system links as planned. The main curren t struggle from being able to route the PCB is that some of the capacitors had been incorrectly route in the schematics part, therefore, I will need to take inspection into them before moving on."}, {"post_id": 11265, "ts": "2026-06-18T12:56:52Z", "hours": 3.4, "text": "I spent an afternoon finalizing my schematics and turned it into a PCB. After I finished the schematics, I entered the wiring phase and put all the components into a 84*59mm board that will be house in my final robot. The arrangement of the components took more time than I expected as some wiring were needed to be redesign so that the wiring on the board would not be that complicated and span across the whole board. Overall, I am satisfy with the current placement of the modules and will be starting to wire up the components tomorrow. Side note: I got the filaments needed to print the case of my robot so production and assembly is near!!!!(So excited, Hardware>Software). Anyways, see ya’ll tomorrow when hopefully I can finish all the wiring on the components!"}, {"post_id": 11126, "ts": "2026-06-18T06:23:41Z", "hours": 1.0336, "text": "Working on the schematics for a custom PCB in the robot. For the project, I am using EasyEDA to make my PCB. I am finished with the schematics and will be moving onto the wiring part. I am very excited to see this project come together. for the components in the project, I used a 11.1v battery as the robots power source, ESP32 as main logi c and control as it could bluetooth connect to my joystick controller, I chose a MAX7219 LED matrix as the face of the robot to give it a pixel-ly feel, and i used two 24mm nema17 as the robots drivetrain. Lastly, I hvae a HC-SR04 distance sensor and more importantly a MPU 6050 for the robots tilt feedback and achieve two wheel balance."}, {"post_id": 10476, "ts": "2026-06-17T06:56:26Z", "hours": 0.9003, "text": "Recap on past CAD on the project and explore color scheme for the final build. I started my design on the self-balancing robot almost a month before Stardance started, therefore, most of the CAD was finished in this period, except for the rim of the wheels which I have not settle on a design that I like yet. For my first time lapse on the the project, I replicated a wheel rim that I tested different color on my robot in Fusion360. I mainly focus on design with two colors for ease of printing and not using tons of different rolls of filament. So the hardware part of the robot is almost done, therefore, I will move on to PCB design with EasyEdaSTD for the next step and try more types wheel rim for my final design. Initially, I was going to use perfboards for the wiring, but I fear that could get messy and hard to debug real quick. I am currently done with half of the schematics and finalized the hardware modules using. (Please following Instagram: vtr_lab)(thx)"}, {"post_id": 7871, "ts": "2026-06-13T04:00:48Z", "hours": 0.2667, "text": "A self balancing Robot driven on two Nema 17 stepper motor and ESP 32 as main logic control. Currently, I am 85% done with hardware design, except the mount for the stepper motors. I am designing my CAD in Fusion360 and working on custom PCB in EasyEDA. In addition, how do I track work time outside coding, like working on PCB or Hardware, how are those hours logged into Hackclub? Thank you!"}]...
|
Title: Nebula by @CVictor | Stardance
Devlogs:
A Title: Nebula by @CVictor | Stardance
Devlogs:
A self balancing Robot driven on two Nema 17 stepper motor and ESP 32 as main logic control. Currently, I am 85% done with hardware design, except the mount for the stepper motors. I am designing my CAD in Fusion360 and working on custom PCB in EasyEDA. In addition, how do I track work time outside coding, like working on PCB or Hardware, how are those hours logged into Hackclub? Thank you!
Recap on past CAD on the project and explore color scheme for the final build. I started my design on the self-balancing robot almost a month before Stardance started, therefore, most of the CAD was finished in this period, except for the rim of the wheels which I have not settle on a design that I like yet. For my first time lapse on the the project, I replicated a wheel rim that I tested different color on my robot in Fusion360. I mainly focus on design with two colors for ease of printing and not using tons of different rolls of filament. So the hardware part of the robot is almost done, therefore, I will move on to PCB design with EasyEdaSTD for the next step and try more types wheel rim for my final design. Initially, I was going to use perfboards for the wiring, but I fear that could get messy and hard to debug real quick. I am currently done with half of the schematics and finalized the hardware modules using. (Please following Instagram: vtr_lab)(thx)
Working on the schematics for a custom PCB in the robot. For the project, I am using EasyEDA to make my PCB. I am finished with the schematics and will be moving onto the wiring part. I am very excited to see this project come together. for the components in the project, I used a 11.1v battery as the robots power source, ESP32 as main logi c and control as it could bluetooth connect to my joystick controller, I chose a MAX7219 LED matrix as the face of the robot to give it a pixel-ly feel, and i used two 24mm nema17 as the robots drivetrain. Lastly, I hvae a HC-SR04 distance sensor and more importantly a MPU 6050 for the robots tilt feedback and achieve two wheel balance.
I spent an afternoon finalizing my schematics and turned it into a PCB. After I finished the schematics, I entered the wiring phase and put all the components into a 84*59mm board that will be house in my final robot. The arrangement of the components took more time than I expected as some wiring were needed to be redesign so that the wiring on the board would not be that complicated and span across the whole board. Overall, I am satisfy with the current placement of the modules and will be starting to wire up the components tomorrow. Side note: I got the filaments needed to print the case of my robot so production and assembly is near!!!!(So excited, Hardware>Software). Anyways, see ya’ll tomorrow when hopefully I can finish all the wiring on the components!
Finalizing schematics and layout before routing- Problems encounter: clearing messy schematics, double checking component layouts, making sure the system links as planned. The main curren t struggle from being able to route the PCB is that some of the capacitors had been incorrectly route in the schematics part, therefore, I will need to take inspection into them before moving on.
Polishing My Schematics, AGAIN!!! Since My previous schematics relied heavily on net ports, it becomes hard to understand the relationship between components as I moved on to the routing part. Therefore, I am now going back to the schematics and check the wiring block by block. Current Progress: Power Block Sensors and Servos MPU6050 Stepper Driver Logic / Pinout of ESP Stepper Motor Currently(2/6). Checking progress includes tiding up wires and use more wires instead of all net ports. Checking amounts of decoupling capacitor needed for each component. Making sure that each individual block of components can run (electrically). Yeah, hope I get back to routing soon and finish the PCB, also, I want to gather some idea for PCB art for my first functionable PCB, so submit any ideas through commenting on this dev post of consider following vtr_lab on instagram(I am close to having more post than followers😭😭). Thanks alot~ 2026/6/29, Victor
Finished Routing My PCB: Process: STEP 1. Check all schematics STEP 2. Use auto routing function, define the thickness or trace for each type of trace: eg. 11.1V-1.25mm, logic-0.254mm, 5V-0.9mm……etc. STEP 3. Skip the routing for GND nets STEP 4. Adjust any wiring STEP 5. Pour Copper layer for the grounds —————————————————–The process sounds easy, atleast that’s what I though at first, but here are some things that I learned and challenges encounter in the process: Schematics is the easy part, do it well and it could you could save alot of time in the routing section. When letting the software to handle auto-routing, make sure to leave out the GND nets so make the wiring less complex. Route the GND nets at last with copper filled layer to ensure all grounds and securely connected. Issue encounted->Isolated island As posted in the image, even after pouring in the GND layer , there still is a ratline between the ground port of C7 to other components, meaning the ground of the part is not connected. This is a common issue for auto routing other nets first , ignoring ground and make it an isolated island. Solution: To fix the problem, I swap the position of C7 and U8 so that the C7 will not be caught in the connectionof U8 to my ESP which is the main reason why C7 is electronically isolated. After that, we can simply regenerate the ground copper layer to fix the issue. Issue encounted-> Antenna Clearout: Since my project will rely heavily on RC control, I need to clearout the copper ground below the antenna part of my esp as the double copper layer could potentially block radio signal. That’s it for now, the design final reaches “DRC(0)” and now I am adding silktouch design to the bottom layer for the final touch before sending the file for production!!!!! . . . See yall later.
Working on CAD and Assembling hardware.
CAD, Soldering, PCB design, all at once. Its been a busy month so I have been building all the progress bit by bit. Major updates and Progress: -Change MPU 6050 to LSM6DS3 -Get rid of the servo arms on both side -Functioning Webpage to control the bot via bluetooth. LSM6DS3 is overall a more reliable that the commonly known MPU 6050 The servo arms were not that important function wise but they took up too much space on the PCB layout, hense I remove its. The webpage is hosted via github and currently it can connect to esp through bluetooth and design patterns for the matrix led that serves as the face of my robot. Pretty much all, I am currently in the process of accumilating all the necessary hardware and materials. Hope I can post a build log soon on my Instagram page @vtr_lab , consider following!
For the past few weeks, I have been working on the hardware of my project. All components has been soldered onto the PCB and all pieces has been printed....
|
1792778002.444943
|
1793382802.444943
|
|
7261
|
Desktop ❌Goose❌ humanoid by @Tsutaki | Stardance
|
Tsutaki
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Desktop ❌Goose❌ humanoid by @Tsutaki | Star Title: Desktop ❌Goose❌ humanoid by @Tsutaki | Stardance...
|
1793361296.5391834
|
1793966096.5391834
|
|
7262
|
GENESIS-DECK by @YOD-BYTE | Stardance
|
YOD-BYTE
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: GENESIS-DECK by @YOD-BYTE | Stardance
|
1792716903.7198694
|
1793321703.7198694
|
|
7263
|
Dewey Decimal by @IDKHowToDeleteProfile | Stardanc Dewey Decimal by @IDKHowToDeleteProfile | Stardance...
|
IDKHowToDeleteProfile
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Dewey Decimal by @IDKHowToDeleteProfile | S Title: Dewey Decimal by @IDKHowToDeleteProfile | Stardance...
|
1793386198.5899498
|
1793990998.5899498
|
|
7264
|
IOS App by @hadek | Stardance
|
hadek
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: IOS App by @hadek | Stardance
|
1793181006.5741541
|
1793785806.5741541
|
|
7265
|
MEGATESTABOX by @canimacoes | Stardance
|
canimacoes
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: MEGATESTABOX by @canimacoes | Stardance
|
1793235135.2682636
|
1793839935.2682636
|
|
7266
|
My awesome macropad! by @grunsteinpeti | Stardance
|
grunsteinpeti
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @grunsteinpeti | St Title: My awesome macropad! by @grunsteinpeti | Stardance...
|
1793350577.4650068
|
1793955377.4650068
|
|
7267
|
pienso crear un Jarvis que pueda funcionar en cual pienso crear un Jarvis que pueda funcionar en cualquier computadora sin importar que prosesador o componentes internos:) by @jefrivera15 | Stardance...
|
jefrivera15
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: pienso crear un Jarvis que pueda funcionar Title: pienso crear un Jarvis que pueda funcionar en cualquier computadora sin importar que prosesador o componentes internos:) by @jefrivera15 | Stardance...
|
1793299949.3817632
|
1793904749.3817632
|
|
7268
|
Wingy plane by @Amayas | Stardance
|
Amayas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Wingy plane by @Amayas | Stardance
|
1793224322.9430935
|
1793829122.9430935
|
|
7269
|
My awesome macropad! by @ALU | Stardance
|
ALU
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ALU | Stardance
|
1793401019.0479596
|
1794005819.0479596
|
|
7270
|
My first slack bot! by @hunt | Stardance
|
hunt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @hunt | Stardance
|
1793321314.4749286
|
1793926114.4749286
|
|
7271
|
Sleepy Boi by @Shre | Stardance
|
Shre
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Sleepy Boi by @Shre | Stardance
|
1793256795.0936284
|
1793861595.0936284
|
|
7272
|
TRASHPAD by @Mokxsh_ | Stardance
|
|
1
|
20.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-17T13:34:37Z", "hours": 20.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What did you make? I made TRASHPAD, a 9-key macropad with an OLED screen, a rotary encoder, a custom PCB, and a 3D-printed case. Basically, it’s a little shortcut machine that sits on my desk and handles the stuff I use all the time. I also made a website and a simulator for it so people can mess around with it without needing the actual hardware. What was challenging? The PCB was definitely the hardest part. At one point I thought I was completely done, then realized I had forgotten some matrix connections and had no GPIO pins left on the XIAO. That meant going back, changing the design, removing parts, updating the PCB, and even changing the case. It was one of those moments where a tiny mistake somehow creates hours of extra work. What are you proud of? Honestly, I’m proud that I solved my own problem. I was getting annoyed constantly reaching for shortcuts while working, so instead of living with it, I built something around the way I actually use my computer. Now I have a device that puts my most-used shortcuts, controls, and macros right in front of me. It’s cool seeing something that started as a random idea turn into something I genuinely use. What should people know so they can test your project? The easiest way is through the website simulator. You can click the keys, play with the encoder, and see how the OLED responds. If you want to dig deeper, all the PCB files, CAD files, firmware, and production files are in the repo so you can see exactly how everything was built.", "repo": "https://github.com/Mokxsh404/TRASHPAD", "demo": ""}]...
|
[{"post_id": 10106, "ts": "202 [{"post_id": 10106, "ts": "2026-06-16T18:16:53Z", "hours": 1.4847, "text": "I honestly can’t believe I’m writing this, but TrashPad is finally at the point where I can call it finished. Today I wrapped up the OLED UI, which was one of the last things on my checklist. I spent some time cleaning up the screens, fixing spacing issues, and making everything feel consistent. It might seem like a small thing, but having a proper interface makes the whole project feel a lot more polished. It’s no longer just hardware connected together, it actually feels like a finished device. The hardware side is now stable, the enclosure design is finished, and the PCB has reached that stage where I’m finally comfortable saying “I’m not changing this anymore.” At this point there’s only one task left: getting everything organized. I need to clean up the code, prepare the repository, sort out the documentation, and make sure everything is ready for release. After that, that’s it, I’m Gonna Ship It"}, {"post_id": 9989, "ts": "2026-06-16T14:59:47Z", "hours": 2.4803, "text": "This project started as a “quick build” and somehow turned into a full redesign loop I did not see coming. I spent around 16 hours straight building it end to end. No breaks, just flow. Schematic → PCB → Fusion 360 enclosure. Everything was moving fast and honestly felt solid at the time. ⚡ Schematic phase Mapped out the full switch matrix. Rows and columns looked clean on paper. Nothing felt off. This was the calm stage. 🧩 PCB design Routed everything around the XIAO RP2040. Tight layout, all pins assigned, everything looked correct. That’s the keyword: looked . 🖼️ Fusion 360 enclosure Built the case, aligned the board, checked fitment. At this point I genuinely thought: “yeah, this is a first-try success.” It wasn’t. 💥 The moment it broke During final checks, I realized something stupid but critical: ✔ Rows were connected ❌ Columns were NOT connected to the XIAO At first I thought: “ok easy fix, PCB edit, done in 2 minutes.” Then reality hit. 🚫 The real problem No GPIO pins left on the XIAO. Zero. Everything was already assigned. So the “quick fix” wasn’t possible at all. 🔧 Forced redesign Only option left was to free up pins. That meant removing the potentiometer I had already designed into the system. And that one change didn’t stay small: ~ PCB had to be updated again ~ Pin mapping had to be redone ~ Fusion enclosure had to be redesigned ~ Mechanical layout shifted again What should’ve been a tiny wiring fix turned into a full system rollback."}, {"post_id": 7506, "ts": "2026-06-12T14:56:29Z", "hours": 4.4644, "text": "add more tweakss ;) i) changed the previous trash knob design ii) made random cuts which i thought are coolll iii) changed the fonts iv) added the stardance logo im gonna ship it soon!"}, {"post_id": 5454, "ts": "2026-06-09T07:45:14Z", "hours": 10.8656, "text": "took me a while but yay!"}, {"post_id": 4238, "ts": "2026-06-07T14:07:01Z", "hours": 0.2667, "text": "guys please tell me if this pcb will work ? the xiao is at the back side. (Im Lowkey New)"}, {"post_id": 2194, "ts": "2026-06-04T15:41:24Z", "hours": 0.2675, "text": "Just Finished Up Building the website for you’re very-very own “TRASHPAD”"}]...
|
Title: TRASHPAD by @Mokxsh_ | Stardance
Devlogs:
Title: TRASHPAD by @Mokxsh_ | Stardance
Devlogs:
Just Finished Up Building the website for you’re very-very own “TRASHPAD”
guys please tell me if this pcb will work ? the xiao is at the back side. (Im Lowkey New)
took me a while but yay!
add more tweakss ;) i) changed the previous trash knob design ii) made random cuts which i thought are coolll iii) changed the fonts iv) added the stardance logo im gonna ship it soon!
This project started as a “quick build” and somehow turned into a full redesign loop I did not see coming. I spent around 16 hours straight building it end to end. No breaks, just flow. Schematic → PCB → Fusion 360 enclosure. Everything was moving fast and honestly felt solid at the time. ⚡ Schematic phase Mapped out the full switch matrix. Rows and columns looked clean on paper. Nothing felt off. This was the calm stage. 🧩 PCB design Routed everything around the XIAO RP2040. Tight layout, all pins assigned, everything looked correct. That’s the keyword: looked . 🖼️ Fusion 360 enclosure Built the case, aligned the board, checked fitment. At this point I genuinely thought: “yeah, this is a first-try success.” It wasn’t. 💥 The moment it broke During final checks, I realized something stupid but critical: ✔ Rows were connected ❌ Columns were NOT connected to the XIAO At first I thought: “ok easy fix, PCB edit, done in 2 minutes.” Then reality hit. 🚫 The real problem No GPIO pins left on the XIAO. Zero. Everything was already assigned. So the “quick fix” wasn’t possible at all. 🔧 Forced redesign Only option left was to free up pins. That meant removing the potentiometer I had already designed into the system. And that one change didn’t stay small: ~ PCB had to be updated again ~ Pin mapping had to be redone ~ Fusion enclosure had to be redesigned ~ Mechanical layout shifted again What should’ve been a tiny wiring fix turned into a full system rollback.
I honestly can’t believe I’m writing this, but TrashPad is finally at the point where I can call it finished. Today I wrapped up the OLED UI, which was one of the last things on my checklist. I spent some time cleaning up the screens, fixing spacing issues, and making everything feel consistent. It might seem like a small thing, but having a proper interface makes the whole project feel a lot more polished. It’s no longer just hardware connected together, it actually feels like a finished device. The hardware side is now stable, the enclosure design is finished, and the PCB has reached that stage where I’m finally comfortable saying “I’m not changing this anymore.” At this point there’s only one task left: getting everything organized. I need to clean up the code, prepare the repository, sort out the documentation, and make sure everything is ready for release. After that, that’s it, I’m Gonna Ship It
Ships:
What did you make? I made TRASHPAD, a 9-key macropad with an OLED screen, a rotary encoder, a custom PCB, and a 3D-printed case. Basically, it’s a little shortcut machine that sits on my desk and handles the stuff I use all the time. I also made a website and a simulator for it so people can mess around with it without needing the actual hardware. What was challenging? The PCB was definitely the hardest part. At one point I thought I was completely done, then realized I had forgotten some matrix connections and had no GPIO pins left on the XIAO. That meant going back, changing the design, removing parts, updating the PCB, and even changing the case. It was one of those moments where a tiny mistake somehow creates hours of extra work. What are you proud of? Honestly, I’m proud that I solved my own problem. I was getting annoyed constantly reaching for shortcuts while working, so instead of living with it, I built something around the way I actually use my computer. Now I have a device that puts my most-used shortcuts, controls, and macros right in front of me. It’s cool seeing something that started as a random idea turn into something I genuinely use. What should people know so they can test your project? The easiest way is through the website simulator. You can click the keys, play with the encoder, and see how the OLED responds. If you want to dig deeper, all the PCB files, CAD files, firmware, and production files are in the repo so you can see exactly how everything was built....
|
1792875210.906979
|
1793739210.906979
|
|
7273
|
My first slack bot! by @samarthf99m | Stardance
|
samarthf99m
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @samarthf99m | Stard Title: My first slack bot! by @samarthf99m | Stardance...
|
1793321412.1211221
|
1793926212.1211221
|
|
7274
|
Sleepy Sounds by @Shre_ | Stardance
|
Shre_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Sleepy Sounds by @Shre_ | Stardance
|
1793166867.9549737
|
1793771667.9549737
|
|
7275
|
My first slack bot! by @Tony | Stardance
|
Tony
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Tony | Stardance
|
1793170154.9982014
|
1793774954.9982014
|
|
7276
|
LiteStyle by @JyotP | Stardance
|
JyotP
|
1
|
2.0
|
26
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-04T23:17:58Z", "hours": 2.0, "multiplier": 12.05, "payout": 26, "blessing": "neutral", "text": "I made a lightweight, highly customizable CSS library. It took me around 3 hours to put together, and it was honestly a fun thing to build. The whole point is that you can customize pretty much every single detail of a UI element and just drop the final .css file straight into your project. Node.js was definitely a bigger pain than I expected to get working right. But the workflow is pretty neat now: you just run the server locally, open up the dashboard, edit your components, hit save, and your CSS is ready to go in your HTML. Definitely going to be using this for my upcoming portfolio project.", "repo": "https://github.com/JHPate1/LiteStyle/", "demo": "http://Litestyle-demo.42web.io"}]...
|
[{"post_id": 2458, "ts": "2026 [{"post_id": 2458, "ts": "2026-06-04T23:12:31Z", "hours": 1.2106, "text": "Devlog 2- People said my last devlog sounded like AI, so I’m just gonna type this like a normal person. Anyway, I got a huge part of this project finished and I’m basically ready to ship it. I added a ton of new elements: badges, buttons, inputs, and all that stuff you’d expect from something like Bootstrap, and made it so you can actually edit every little detail. The main thing though was the debugging. Node.js and Vite were being a total nightmare. Vite kept crashing because it couldn’t find my files, and then the whole server refused to start just because of some dumb syntax errors I made while setting up the automatic code. It was a massive pain to get it all talking to each other, but I finally got it working. Also did I mention how stupid JS syntax errors can be? Like it throws errors that aren’t even errors. This project is basically finished now, if you want to use it go to my GitHub and follow the instructions. Still sad on how I lost 50 minutes of log time because of stupid HackaTime. (PS: I love intellisense now, saved me 30 minutes. Big W.)"}, {"post_id": 2397, "ts": "2026-06-04T21:07:56Z", "hours": 0.9622, "text": "Devlog 1: Building LiteStyle Okay so I made a CSS library. This is my first devlog and honestly I have no idea what I’m doing with the format, but here we go (no yap). Here’s the thing about existing libraries. Bootstrap? Fine. Works. But you hit a wall eventually where you’re fighting it more than using it. Tailwind? Incredibly powerful. Also incredibly easy to turn your HTML into unreadable alphabet soup if you don’t already know what you’re doing. I watched a friend who’s genuinely smart spend twenty minutes trying to center a div with Tailwind and I thought, there has to be a middle ground. So LiteStyle. Modular, lightweight, actually makes sense if you’re new to this. The idea is you grab pre-built CSS blocks, plug them in, tweak what you need. No config files. No memorizing forty utility classes to make a button. Just clean, readable code that does what you expect. What I actually built in 90 minutes: Repo’s up. File structure’s mapped out. Built a rough dashboard for customizing builds. The dashboard looks like garbage right now. Also I built it with Bootstrap and Tailwind which is obviously absurd. I’m building a CSS library to replace those and I used them to build the tool. You have to start somewhere I guess. It’ll get ripped out soon enough. HackaTime decided initializing my repo meant I started an entirely new project so my time tracking is completely broken. Small tragedy. Code’s committed at least. What’s next: Write the actual utility classes. Get the dashboard running on LiteStyle instead of the competition. Then we’ll see if this whole thing actually holds together or if I just wasted days."}]...
|
Title: LiteStyle by @JyotP | Stardance
Devlogs:
D Title: LiteStyle by @JyotP | Stardance
Devlogs:
Devlog 1: Building LiteStyle Okay so I made a CSS library. This is my first devlog and honestly I have no idea what I’m doing with the format, but here we go (no yap). Here’s the thing about existing libraries. Bootstrap? Fine. Works. But you hit a wall eventually where you’re fighting it more than using it. Tailwind? Incredibly powerful. Also incredibly easy to turn your HTML into unreadable alphabet soup if you don’t already know what you’re doing. I watched a friend who’s genuinely smart spend twenty minutes trying to center a div with Tailwind and I thought, there has to be a middle ground. So LiteStyle. Modular, lightweight, actually makes sense if you’re new to this. The idea is you grab pre-built CSS blocks, plug them in, tweak what you need. No config files. No memorizing forty utility classes to make a button. Just clean, readable code that does what you expect. What I actually built in 90 minutes: Repo’s up. File structure’s mapped out. Built a rough dashboard for customizing builds. The dashboard looks like garbage right now. Also I built it with Bootstrap and Tailwind which is obviously absurd. I’m building a CSS library to replace those and I used them to build the tool. You have to start somewhere I guess. It’ll get ripped out soon enough. HackaTime decided initializing my repo meant I started an entirely new project so my time tracking is completely broken. Small tragedy. Code’s committed at least. What’s next: Write the actual utility classes. Get the dashboard running on LiteStyle instead of the competition. Then we’ll see if this whole thing actually holds together or if I just wasted days.
Devlog 2- People said my last devlog sounded like AI, so I’m just gonna type this like a normal person. Anyway, I got a huge part of this project finished and I’m basically ready to ship it. I added a ton of new elements: badges, buttons, inputs, and all that stuff you’d expect from something like Bootstrap, and made it so you can actually edit every little detail. The main thing though was the debugging. Node.js and Vite were being a total nightmare. Vite kept crashing because it couldn’t find my files, and then the whole server refused to start just because of some dumb syntax errors I made while setting up the automatic code. It was a massive pain to get it all talking to each other, but I finally got it working. Also did I mention how stupid JS syntax errors can be? Like it throws errors that aren’t even errors. This project is basically finished now, if you want to use it go to my GitHub and follow the instructions. Still sad on how I lost 50 minutes of log time because of stupid HackaTime. (PS: I love intellisense now, saved me 30 minutes. Big W.)
Ships:
I made a lightweight, highly customizable CSS library. It took me around 3 hours to put together, and it was honestly a fun thing to build. The whole point is that you can customize pretty much every single detail of a UI element and just drop the final .css file straight into your project. Node.js was definitely a bigger pain than I expected to get working right. But the workflow is pretty neat now: you just run the server locally, open up the dashboard, edit your components, hit save, and your CSS is ready to go in your HTML. Definitely going to be using this for my upcoming portfolio project....
|
1793281944.946247
|
1793368344.946247
|
|
7277
|
Audio Mixer by @Dafric | Stardance
|
Dafric
|
0
|
3.44
|
0
|
[]
|
[{"post_id": 4282, "ts": "2026 [{"post_id": 4282, "ts": "2026-06-07T15:20:17Z", "hours": 3.4397, "text": "Audio Mixer - Devlog #00 Project Introduction This project actually started before Stardance , so I’ll give a short introduction first. The idea came from Modue . I wanted an audio mixer that can control and route audio from individual applications or groups of them into multiple output channels, while also allowing virtual control and saving presets. But Modue turned out to be quite expensive, so I decided to try building something similar myself. I ordered a few parts from AliExpress and started sketching out a concept. I designed a circuit , which was my first real attempt at hardware design. After that, I built a breadboard prototype and later soldered everything onto a perfboard. For the case, I’m using FreeCAD, which is also new to me. I was already familiar with Blender, but I picked up CAD by just doing, and I really enjoy it. The case is not finished yet, but most of it is done. On the software side, I’m writing an Electron app with a C++ backend (native addon). I already built a simple audio routing engine where you can add channels, select input devices or virtual inputs, and control volume. Communication between the software and the ESP32 already works, so I can control the faders from software, and the faders also update when changes happen in software. Each fader (except one) has a small display underneath. Its main purpose is to show channel information and states like mute. These displays are ESP32-C6 boards with integrated touchscreens. They communicate with the main ESP32 over ESP-NOW. Updates Added a 6-button push matrix (3x2) to a display (since the main ESP32 ran out of usable GPIO pins) Wrote a script to read button presses from the matrix (each row is pulled LOW individually, then columns are read) Button presses are sent to the main ESP32 via ESP-NOW Integrated the display firmware into the main firmware repository Challenges One of the buttons didn’t reliably trigger → Fix: added a small delay between setting the row LOW and reading the columns"}]...
|
Title: Audio Mixer by @Dafric | Stardance
Devlogs Title: Audio Mixer by @Dafric | Stardance
Devlogs:
Audio Mixer - Devlog #00 Project Introduction This project actually started before Stardance , so I’ll give a short introduction first. The idea came from Modue . I wanted an audio mixer that can control and route audio from individual applications or groups of them into multiple output channels, while also allowing virtual control and saving presets. But Modue turned out to be quite expensive, so I decided to try building something similar myself. I ordered a few parts from AliExpress and started sketching out a concept. I designed a circuit , which was my first real attempt at hardware design. After that, I built a breadboard prototype and later soldered everything onto a perfboard. For the case, I’m using FreeCAD, which is also new to me. I was already familiar with Blender, but I picked up CAD by just doing, and I really enjoy it. The case is not finished yet, but most of it is done. On the software side, I’m writing an Electron app with a C++ backend (native addon). I already built a simple audio routing engine where you can add channels, select input devices or virtual inputs, and control volume. Communication between the software and the ESP32 already works, so I can control the faders from software, and the faders also update when changes happen in software. Each fader (except one) has a small display underneath. Its main purpose is to show channel information and states like mute. These displays are ESP32-C6 boards with integrated touchscreens. They communicate with the main ESP32 over ESP-NOW. Updates Added a 6-button push matrix (3x2) to a display (since the main ESP32 ran out of usable GPIO pins) Wrote a script to read button presses from the matrix (each row is pulled LOW individually, then columns are read) Button presses are sent to the main ESP32 via ESP-NOW Integrated the display firmware into the main firmware repository Challenges One of the buttons didn’t reliably trigger → Fix: added a small delay between setting the row LOW and reading the columns...
|
1792691689.570213
|
1793296489.570213
|
|
7278
|
My awesome macropad! by @Tony | Stardance
|
Tony
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Tony | Stardance
|
1793170495.3882701
|
1793775295.3882701
|
|
7279
|
My first slack bot! by @ericsson | Stardance
|
ericsson
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @ericsson | Stardanc Title: My first slack bot! by @ericsson | Stardance...
|
1792785160.5274162
|
1793389960.5274162
|
|
7280
|
Untitled by @ABYLOVESCATS | Stardance
|
ABYLOVESCATS
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ABYLOVESCATS | Stardance
|
1793364633.0579948
|
1793969433.0579948
|
|
7281
|
My first slack bot! by @sreevaishnavi | Stardance
|
sreevaishnavi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @sreevaishnavi | Sta Title: My first slack bot! by @sreevaishnavi | Stardance...
|
1793263878.6167586
|
1793868678.6167586
|
|
7282
|
NeuroAssist by @eshunburge | Stardance
|
eshunburge
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: NeuroAssist by @eshunburge | Stardance
|
1792925350.7423196
|
1793789350.7423196
|
|
7283
|
My first slack bot! by @Salvi | Stardance
|
Salvi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Salvi | Stardance
|
1793289245.2497969
|
1793894045.2497969
|
|
7284
|
Impulse Campus by @The_Interwebs | Stardance
|
The_Interwebs
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Impulse Campus by @The_Interwebs | Stardanc Title: Impulse Campus by @The_Interwebs | Stardance...
|
1793303775.1425319
|
1793908575.1425319
|
|
7285
|
A robot by @Uknowmeh01 | Stardance
|
Uknowmeh01
|
0
|
25.0
|
0
|
[]
|
[{"post_id": 30152, "ts": "202 [{"post_id": 30152, "ts": "2026-07-17T14:26:19Z", "hours": 25.0, "text": "actually i’m woprking on how the robot will be i try to build it in 3d"}]...
|
Title: A robot by @Uknowmeh01 | Stardance
Devlogs Title: A robot by @Uknowmeh01 | Stardance
Devlogs:
actually i’m woprking on how the robot will be i try to build it in 3d...
|
1792896445.5775256
|
1793760445.5775256
|
|
7286
|
LaTx (Linguistic analysis and Text eXamination by LaTx (Linguistic analysis and Text eXamination by @MattC | Stardance...
|
MattC
|
0
|
7.62
|
0
|
[]
|
[{"post_id": 5583, "ts": "2026 [{"post_id": 5583, "ts": "2026-06-09T13:09:57Z", "hours": 7.6228, "text": "Completing the UI…"}]...
|
Title: LaTx (Linguistic analysis and Text eXaminat Title: LaTx (Linguistic analysis and Text eXamination by @MattC | Stardance
Devlogs:
Completing the UI…...
|
1793213573.1612763
|
1793818373.1612763
|
|
7287
|
My awesome macropad! by @verttt | Stardance
|
verttt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @verttt | Stardance
|
1793238787.4183428
|
1793843587.4183428
|
|
7288
|
rustbreeder by nagi by @asherwandenreich | Stardan rustbreeder by nagi by @asherwandenreich | Stardance...
|
asherwandenreich
|
1
|
5.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-27T18:59:21Z", "hours": 5.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a clone of a website I actually used while playing rust, rustbreeder.com. It’s a website where you add in all of the plant genes you have (in the video game rust) and it tells you the best plant you can breed and exactly where to put your current plants in game to get those plants.", "repo": "https://github.com/winterrmelonn/rustbreeder.py", "demo": "https://rustbreeder.vercel.app/"}]...
|
[{"post_id": 83336, "ts": "202 [{"post_id": 83336, "ts": "2026-10-27T18:54:05Z", "hours": 0.5214, "text": "Deployed on vercel (which I learned from the make your own blog tutorial) and did some stuff with the repo to make it shippable."}, {"post_id": 77099, "ts": "2026-10-05T17:08:32Z", "hours": 1.9556, "text": "Making it better: 01 First I found that finalizing anything over 5 plants would freeze my Mac for over 10 seconds. I looked over the vibe code and realized it was using permutations and generating every single outcome and running each outcome through the scoring system. I used AI to switch from a brute force engine to a much more optimized engine. It implemented memoization (cache) which eliminated duplicates. It also implemented hill climbing sorting and random restarts, which helped find the best outcome much faster. (86% decrease) Now that I’m starting to understand Stardance and Hack Club I’m pivoting from heavy vibe-coding to having Claude walk me through the code instead (in tandem with the tutorials). I’ll pitch the ideas, fixes, next steps, and ask Claude when I’m stuck on the technical aspects."}, {"post_id": 75129, "ts": "2026-09-29T07:00:52Z", "hours": 2.9564, "text": "Made it exist: Manually wrote the base of the engine that took a user’s given plant (berry) genes and weighed its worth based on its six traits. [rust (the game) genetics, iykyk] Manually wrote code to predict the resultant trait(s) in each of the six gene slots when two plants are crossbred. Vibe-coded a GUI with input for the user’s plant genes. Created a nice finalize button and separated the “instructions” (aka where to plant the plants you have) and the “resultants” (aka the plants you’ll breed). Added edit/delete feature in case of a fat-finger when inputting plant genes."}]...
|
Title: rustbreeder by nagi by @asherwandenreich | Title: rustbreeder by nagi by @asherwandenreich | Stardance
Devlogs:
Made it exist: Manually wrote the base of the engine that took a user’s given plant (berry) genes and weighed its worth based on its six traits. [rust (the game) genetics, iykyk] Manually wrote code to predict the resultant trait(s) in each of the six gene slots when two plants are crossbred. Vibe-coded a GUI with input for the user’s plant genes. Created a nice finalize button and separated the “instructions” (aka where to plant the plants you have) and the “resultants” (aka the plants you’ll breed). Added edit/delete feature in case of a fat-finger when inputting plant genes.
Making it better: 01 First I found that finalizing anything over 5 plants would freeze my Mac for over 10 seconds. I looked over the vibe code and realized it was using permutations and generating every single outcome and running each outcome through the scoring system. I used AI to switch from a brute force engine to a much more optimized engine. It implemented memoization (cache) which eliminated duplicates. It also implemented hill climbing sorting and random restarts, which helped find the best outcome much faster. (86% decrease) Now that I’m starting to understand Stardance and Hack Club I’m pivoting from heavy vibe-coding to having Claude walk me through the code instead (in tandem with the tutorials). I’ll pitch the ideas, fixes, next steps, and ask Claude when I’m stuck on the technical aspects.
Deployed on vercel (which I learned from the make your own blog tutorial) and did some stuff with the repo to make it shippable.
Ships:
I made a clone of a website I actually used while playing rust, rustbreeder.com. It’s a website where you add in all of the plant genes you have (in the video game rust) and it tells you the best plant you can breed and exactly where to put your current plants in game to get those plants....
|
1793271299.7471132
|
1793357699.7471132
|
|
7289
|
sap by @sylvieisnton | Stardance
|
sylvieisnton
|
0
|
20.79
|
0
|
[]
|
[{"post_id": 61243, "ts": "202 [{"post_id": 61243, "ts": "2026-09-04T02:36:59Z", "hours": 9.9556, "text": "Added several commands, colored help menu also imma push this to the repo tomorrow sob im embarrassed by the organization"}, {"post_id": 58806, "ts": "2026-08-31T12:02:18Z", "hours": 10.8367, "text": "sap has near full parity with node! (not even close)"}]...
|
Title: sap by @sylvieisnton | Stardance
Devlogs:
Title: sap by @sylvieisnton | Stardance
Devlogs:
sap has near full parity with node! (not even close)
Added several commands, colored help menu also imma push this to the repo tomorrow sob im embarrassed by the organization...
|
1792925284.9758797
|
1793789284.9758797
|
|
7290
|
Untitled project by @saai_24 | Stardance
|
saai_24
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @saai_24 | Stardance
|
1792734610.6640036
|
1793339410.6640036
|
|
7291
|
My first slack bot! by @I_want_that_3d_printer_Der My first slack bot! by @I_want_that_3d_printer_Derek05 | Stardance...
|
I_want_that_3d_printer_Derek05
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @I_want_that_3d_prin Title: My first slack bot! by @I_want_that_3d_printer_Derek05 | Stardance...
|
1792684121.7956977
|
1793288921.7956977
|
|
7292
|
veridian.study by @OrangJaguar | Stardance
|
OrangJaguar
|
1
|
25.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-01T04:05:21Z", "hours": 25.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I built a full-stack learning platform that builds personalized study plans from a student’s notes and exam dates, diagnoses exactly why they are getting questions wrong across six failure modes, and serves targeted practice each day using an ever-growing concept knowledge map.", "repo": "https://github.com/OrangJaguar/Veridian", "demo": "https://veridian.study/"}]...
|
[{"post_id": 19729, "ts": "202 [{"post_id": 19729, "ts": "2026-07-01T03:47:49Z", "hours": 24.8344, "text": "Veridian — Devlog 01 Sophomore year I walked into AP Chemistry, AP US History, and AP Psychology on the same schedule and realized for the first time that I had no idea how to actually study. Not in a “I’m lazy” way — I’d just never had to before. A quick review the night before a test was always enough. Nobody told me that was going to stop working until it already had. I tried everything. Re-reading notes felt like going through the motions. YouTube videos felt productive right up until I closed the tab and remembered nothing. Nothing told me whether what I was doing was actually working until the test came back with a number on it, and by then it was too late to change anything. I looked for something better. What I found were tools built for students who already knew how to study. None of them knew my material, my exam date, or which concepts I genuinely didn’t understand versus which ones just needed one more pass. So eventually I just built the thing myself. That’s Veridian . What It Does You upload your notes, a textbook chapter, a study guide — whatever you actually have for your class. Veridian pulls out the knowledge structure inside that material and builds you a Journey : a personalized study plan that figures out what you don’t know, drills you on it, and tells you exactly where you stand before the exam. Not after. The whole system is driven by FSRS , the most accurate spaced repetition algorithm out there, calibrated to your actual exam deadline so your review timing is mathematically optimized. The AI runs on Gemini Flash . And it’s completely free, permanently. Not a launch promotion. The students who need this the most are usually the ones who can’t afford another subscription. How It’s Built This is the part I’ve spent the most time on. Here’s the core architecture: Journeys are the main container. Inside each Journey are Modules , which are individual concept units extracted from your source material. Every Module moves through three stages: Stage A — Learn : A guided Learning Guide walks you through the concept with plain-language explanations, worked examples, and embedded check-in questions after each section. It’s not passive reading — you have to answer something before you move on. Stage B — Practice : AI-generated questions that never repeat. Every session builds new questions from your actual source material, so you’re always being tested on understanding, not card recognition. Stage C — Mastery : Active recall with no scaffolding. This is where you prove you actually know it. Underneath all of it is the FSRS engine deciding exactly when each concept needs to surface again based on your performance history. It’s not random — it’s a mathematical model of how human memory actually works. The Home screen is built around a single question: what should I do right now? Every Journey with something due today shows up as an action card with the activity type, a time estimate, and a single launch button. You open the app and start. That’s it. There’s also a Community Library where students can publish their Journey so others can clone it, plug in their own deadline, and use it. You share the structure — your personal progress and data always stays yours. Tech React + Vite + Tailwind + Zustand + TanStack Query + Base44 for the backend. Gemini Flash for AI. FSRS for scheduling. Full LaTeX rendering throughout for math-heavy subjects. Where It’s At Veridian is currently closed-source . You can sign up for the live public version at veridian.study . Free forever. No paywall, no AI upsell, no premium tier. More devlogs coming as I keep iterating. — Sanskar"}]...
|
Title: veridian.study by @OrangJaguar | Stardance
Title: veridian.study by @OrangJaguar | Stardance
Devlogs:
Veridian — Devlog 01 Sophomore year I walked into AP Chemistry, AP US History, and AP Psychology on the same schedule and realized for the first time that I had no idea how to actually study. Not in a “I’m lazy” way — I’d just never had to before. A quick review the night before a test was always enough. Nobody told me that was going to stop working until it already had. I tried everything. Re-reading notes felt like going through the motions. YouTube videos felt productive right up until I closed the tab and remembered nothing. Nothing told me whether what I was doing was actually working until the test came back with a number on it, and by then it was too late to change anything. I looked for something better. What I found were tools built for students who already knew how to study. None of them knew my material, my exam date, or which concepts I genuinely didn’t understand versus which ones just needed one more pass. So eventually I just built the thing myself. That’s Veridian . What It Does You upload your notes, a textbook chapter, a study guide — whatever you actually have for your class. Veridian pulls out the knowledge structure inside that material and builds you a Journey : a personalized study plan that figures out what you don’t know, drills you on it, and tells you exactly where you stand before the exam. Not after. The whole system is driven by FSRS , the most accurate spaced repetition algorithm out there, calibrated to your actual exam deadline so your review timing is mathematically optimized. The AI runs on Gemini Flash . And it’s completely free, permanently. Not a launch promotion. The students who need this the most are usually the ones who can’t afford another subscription. How It’s Built This is the part I’ve spent the most time on. Here’s the core architecture: Journeys are the main container. Inside each Journey are Modules , which are individual concept units extracted from your source material. Every Module moves through three stages: Stage A — Learn : A guided Learning Guide walks you through the concept with plain-language explanations, worked examples, and embedded check-in questions after each section. It’s not passive reading — you have to answer something before you move on. Stage B — Practice : AI-generated questions that never repeat. Every session builds new questions from your actual source material, so you’re always being tested on understanding, not card recognition. Stage C — Mastery : Active recall with no scaffolding. This is where you prove you actually know it. Underneath all of it is the FSRS engine deciding exactly when each concept needs to surface again based on your performance history. It’s not random — it’s a mathematical model of how human memory actually works. The Home screen is built around a single question: what should I do right now? Every Journey with something due today shows up as an action card with the activity type, a time estimate, and a single launch button. You open the app and start. That’s it. There’s also a Community Library where students can publish their Journey so others can clone it, plug in their own deadline, and use it. You share the structure — your personal progress and data always stays yours. Tech React + Vite + Tailwind + Zustand + TanStack Query + Base44 for the backend. Gemini Flash for AI. FSRS for scheduling. Full LaTeX rendering throughout for math-heavy subjects. Where It’s At Veridian is currently closed-source . You can sign up for the live public version at veridian.study . Free forever. No paywall, no AI upsell, no premium tier. More devlogs coming as I keep iterating. — Sanskar
Ships:
I built a full-stack learning platform that builds personalized study plans from a student’s notes and exam dates, diagnoses exactly why they are getting questions wrong across six failure modes, and serves targeted practice each day using an ever-growing concept knowledge map....
|
1793202526.74725
|
1793288926.74725
|
|
7293
|
Zerofiles by @franco | Stardance
|
franco
|
1
|
3.0
|
11
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-16T19:14:53Z", "hours": 3.0, "multiplier": 3.18, "payout": 11, "blessing": "neutral", "text": "Hey, i’ve made a Json Alternative called Zerofiles (.zr). I’ve made everything from 0 using only 2 libs and everything weighting a whoping 100kb so its also lightweight and fast. I am proud of making it a lossless, Custom AST engine which was kinda hard. So yeah. Run the test.py to test it.", "repo": "https://github.com/Franco-Senes/zerofiles", "demo": "https://github.com/Franco-Senes/zerofiles/blob/main/example.zr"}]...
|
[{"post_id": 3577, "ts": "2026 [{"post_id": 3577, "ts": "2026-06-06T16:04:00Z", "hours": 1.7214, "text": "Finished everything finally"}, {"post_id": 2512, "ts": "2026-06-05T01:23:20Z", "hours": 0.2669, "text": "I finally finished dumps and other stuff now we are going with ast & formatter classes :D"}, {"post_id": 2501, "ts": "2026-06-05T01:03:10Z", "hours": 0.7286, "text": "Finished my parser finally now we need to do loads and other functions so for now we are doing good"}, {"post_id": 2260, "ts": "2026-06-04T17:33:42Z", "hours": 0.4197, "text": "I ended implementing the comments now i need to actually add the json functionality"}, {"post_id": 2241, "ts": "2026-06-04T17:00:47Z", "hours": 0.3478, "text": "Implementing Json / Zerofiles The first step ill do for the projects is implementing json from 0 and adding a base for adding comments and other stuff. wish me luck"}]...
|
Title: Zerofiles by @franco | Stardance
Devlogs:
Title: Zerofiles by @franco | Stardance
Devlogs:
Implementing Json / Zerofiles The first step ill do for the projects is implementing json from 0 and adding a base for adding comments and other stuff. wish me luck
I ended implementing the comments now i need to actually add the json functionality
Finished my parser finally now we need to do loads and other functions so for now we are doing good
I finally finished dumps and other stuff now we are going with ast & formatter classes :D
Finished everything finally
Ships:
Hey, i’ve made a Json Alternative called Zerofiles (.zr). I’ve made everything from 0 using only 2 libs and everything weighting a whoping 100kb so its also lightweight and fast. I am proud of making it a lossless, Custom AST engine which was kinda hard. So yeah. Run the test.py to test it....
|
1793271313.034927
|
1793357713.034927
|
|
7294
|
My first slack bot! by @H4ck3n1gm4 | Stardance
|
H4ck3n1gm4
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @H4ck3n1gm4 | Starda Title: My first slack bot! by @H4ck3n1gm4 | Stardance...
|
1792694928.9564037
|
1793299728.9564037
|
|
7295
|
My first slack bot! by @LilPapi | Stardance
|
LilPapi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @LilPapi | Stardance
|
1793267691.6778803
|
1793872491.6778803
|
|
7296
|
My awesome macropad! by @Knight | Stardance
|
Knight
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Knight | Stardance
|
1792943679.7800715
|
1793807679.7800715
|
|
7297
|
fpv drone by @Thronyone | Stardance
|
Thronyone
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: fpv drone by @Thronyone | Stardance
|
1793209904.0596116
|
1793814704.0596116
|
|
7298
|
verSATile by @mdpham | Stardance
|
mdpham
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: verSATile by @mdpham | Stardance
|
1793386406.7469578
|
1793991206.7469578
|
|
7299
|
My first slack bot! by @AstroPaws | Stardance
|
AstroPaws
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @AstroPaws | Stardan Title: My first slack bot! by @AstroPaws | Stardance...
|
1793274858.3851156
|
1793879658.3851156
|
|
7300
|
Ducks by @williamhamilton | Stardance
|
williamhamilton
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ducks by @williamhamilton | Stardance
|
1793220590.5367236
|
1793825390.5367236
|