|
6473
|
cool hardware project by @dld | Stardance
|
dld
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: cool hardware project by @dld | Stardance
|
1793249766.941064
|
1793854566.941064
|
|
6474
|
My first slack bot! by @Prag | Stardance
|
Prag
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Prag | Stardance
|
1793386531.620751
|
1793991331.620751
|
|
6475
|
My awesome macropad! by @lucy_stiglitz | Stardance
|
lucy_stiglitz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @lucy_stiglitz | St Title: My awesome macropad! by @lucy_stiglitz | Stardance...
|
1793227681.1249235
|
1793832481.1249235
|
|
6476
|
A Calculator for basic math by @Marco | Stardance
|
Marco
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A Calculator for basic math by @Marco | Sta Title: A Calculator for basic math by @Marco | Stardance...
|
1793173949.3484006
|
1793778749.3484006
|
|
6477
|
Light tracker by @victorisness | Stardance
|
victorisness
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Light tracker by @victorisness | Stardance
|
1793256573.2618861
|
1793861373.2618861
|
|
6478
|
rocket simulator by @Turner | Stardance
|
Turner
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: rocket simulator by @Turner | Stardance
|
1793458504.9086828
|
1794063304.9086828
|
|
6479
|
My awesome macropad! by @Yaredp | Stardance
|
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Yaredp | Stardance
|
1793029680.5257978
|
1793634480.5257978
|
|
6481
|
My awesome macropad! by @chvk1000 | Stardance
|
chvk1000
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @chvk1000 | Stardan Title: My awesome macropad! by @chvk1000 | Stardance...
|
1792792086.514312
|
1793396886.514312
|
|
6482
|
My first slack bot! by @AKM | Stardance
|
AKM
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @AKM | Stardance
|
1793332509.9929557
|
1793937309.9929557
|
|
6483
|
Orbital Assembly by @Astro-Duck | Stardance
|
Astro-Duck
|
0
|
8.21
|
0
|
[]
|
[{"post_id": 82242, "ts": "202 [{"post_id": 82242, "ts": "2026-10-24T11:31:49Z", "hours": 1.6167, "text": "orbital assembly: priming for launch!!! this is almost entirely work on getting the project downloadable properly and easily. not much to say other than every part now has its own file instead of one HUGE file"}, {"post_id": 78695, "ts": "2026-10-11T10:15:01Z", "hours": 1.8503, "text": "actual assembly: I have begun constructing the prototype, as of now I have printed 7 modules with a few more planned"}, {"post_id": 67459, "ts": "2026-09-13T15:54:03Z", "hours": 1.2167, "text": "TRUSSES WITH EASE!!! orbital assembly kinda major update: in this update there is now a brand new construction system: TRUSSES (you know the uninhabitable parts of the ISS/beams) with TRUSSES (yes it is always in caps) you can construct solar arrays, link segments to other segments, and obviously just look cool. now the “WITH EASE” part is about how I have completley redesigned a decent chunk of the modules, to allow easier printing. other bits: A print test has been made it was successfull and showed the cliping system was fully functional (also print times are relativley low, ~1 hour per module) -astro duck signing off"}, {"post_id": 47056, "ts": "2026-08-14T17:41:12Z", "hours": 0.3167, "text": "ORBITAL ASSEMBLY: THE THIRD AXIS (daily log no.4). in this minor update I have added FIVE new modules three of witch completely change the construction system. firstly two new generator modules; the solar array Cap (A+B). and now the interesting modules; THE VERTICAL CONNECTORS, allowing for easy stacking of modules in your station. these new modules are: X module vertical base, X module vertical top and X module vertical extension. thanks for reading. -Astro duck signing off-"}, {"post_id": 46303, "ts": "2026-08-13T13:08:51Z", "hours": 0.45, "text": "orbital assembly: servers online (minor update) in todays minor report i have created two new station modules: the server module and the flag bearer module. the server module is probably one of my most complicated modules yet. while the flagbearer variant pays homage to this event in which orbital assembly is growing from. Astro duck signing off."}, {"post_id": 45798, "ts": "2026-08-12T14:46:21Z", "hours": 1.4053, "text": "decorative bits and bobs (verry large update). in this update I have added 19 total parts including: new window variants for modules, radiators, communication arrays, solar panels and some RTGs. firstly the new windows 8, i mean the eight new windowed modules these allow the astronauts of the station to look outside and see space. next the two new communication modules; the comms array cap modules (A+B). after that the new heat management modules preventing the station from overheating in space; dual radiator and quad radiator modules. importantly the new generator modules, three solar modules and two RTG (Radioisotope thermoelectric generator) modules. last but not least the two new access modules; the multipurpose exterior platform S (or the MEPS). so as you can see a big update. also total list of new modules: cap module a, cap module B, corner windowed A, corner windowed B, T module windowed A, T module windowed b, T module windowed c, comms array module A, comms array module B, dual radiator module, quad radiator module, small solar array, medium solar array, large solar array, RTG cap module A, RTG cap module B, MEPS A and finally MEPS B"}, {"post_id": 43945, "ts": "2026-08-09T12:16:51Z", "hours": 0.8753, "text": "I have returned! I have made big work on orbital assembly including: windowed variant of strait module, corner module A, corner module B, T module A, T module B, T module C, X module A, X module B, cap module A and cap module B. This is the first part of what I am calling operation “push”, with the aim to get most of my projects fully operational. Orbital assembly has been given top priority and I am hoping to do daily updates for a least the next couple of weeks. -Astro duck signing off-"}, {"post_id": 24758, "ts": "2026-07-08T15:21:29Z", "hours": 0.4803, "text": "started work on the core module model it is pretty simple but i still like it"}]...
|
Title: Orbital Assembly by @Astro-Duck | Stardance Title: Orbital Assembly by @Astro-Duck | Stardance
Devlogs:
started work on the core module model it is pretty simple but i still like it
I have returned! I have made big work on orbital assembly including: windowed variant of strait module, corner module A, corner module B, T module A, T module B, T module C, X module A, X module B, cap module A and cap module B. This is the first part of what I am calling operation “push”, with the aim to get most of my projects fully operational. Orbital assembly has been given top priority and I am hoping to do daily updates for a least the next couple of weeks. -Astro duck signing off-
decorative bits and bobs (verry large update). in this update I have added 19 total parts including: new window variants for modules, radiators, communication arrays, solar panels and some RTGs. firstly the new windows 8, i mean the eight new windowed modules these allow the astronauts of the station to look outside and see space. next the two new communication modules; the comms array cap modules (A+B). after that the new heat management modules preventing the station from overheating in space; dual radiator and quad radiator modules. importantly the new generator modules, three solar modules and two RTG (Radioisotope thermoelectric generator) modules. last but not least the two new access modules; the multipurpose exterior platform S (or the MEPS). so as you can see a big update. also total list of new modules: cap module a, cap module B, corner windowed A, corner windowed B, T module windowed A, T module windowed b, T module windowed c, comms array module A, comms array module B, dual radiator module, quad radiator module, small solar array, medium solar array, large solar array, RTG cap module A, RTG cap module B, MEPS A and finally MEPS B
orbital assembly: servers online (minor update) in todays minor report i have created two new station modules: the server module and the flag bearer module. the server module is probably one of my most complicated modules yet. while the flagbearer variant pays homage to this event in which orbital assembly is growing from. Astro duck signing off.
ORBITAL ASSEMBLY: THE THIRD AXIS (daily log no.4). in this minor update I have added FIVE new modules three of witch completely change the construction system. firstly two new generator modules; the solar array Cap (A+B). and now the interesting modules; THE VERTICAL CONNECTORS, allowing for easy stacking of modules in your station. these new modules are: X module vertical base, X module vertical top and X module vertical extension. thanks for reading. -Astro duck signing off-
TRUSSES WITH EASE!!! orbital assembly kinda major update: in this update there is now a brand new construction system: TRUSSES (you know the uninhabitable parts of the ISS/beams) with TRUSSES (yes it is always in caps) you can construct solar arrays, link segments to other segments, and obviously just look cool. now the “WITH EASE” part is about how I have completley redesigned a decent chunk of the modules, to allow easier printing. other bits: A print test has been made it was successfull and showed the cliping system was fully functional (also print times are relativley low, ~1 hour per module) -astro duck signing off
actual assembly: I have begun constructing the prototype, as of now I have printed 7 modules with a few more planned
orbital assembly: priming for launch!!! this is almost entirely work on getting the project downloadable properly and easily. not much to say other than every part now has its own file instead of one HUGE file...
|
1793029751.9340463
|
1793634551.9340463
|
|
6484
|
Untitled by @victorisness | Stardance
|
victorisness
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @victorisness | Stardance
|
1792752654.587155
|
1793357454.587155
|
|
6485
|
Untitled by @victorisness | Stardance
|
victorisness
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @victorisness | Stardance
|
1793285736.706128
|
1793890536.706128
|
|
6486
|
Untitled by @victorisness | Stardance
|
victorisness
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @victorisness | Stardance
|
1793429253.575924
|
1794034053.575924
|
|
6487
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792932880.6518178
|
1793796880.6518178
|
|
6488
|
Black Jack Game by @JWNORRIS | Stardance
|
JWNORRIS
|
0
|
2.07
|
0
|
[]
|
[{"post_id": 2033, "ts": "2026 [{"post_id": 2033, "ts": "2026-06-04T09:57:20Z", "hours": 0.7992, "text": "Finished the game’s logic, and now it works smoothly with no issues so far."}, {"post_id": 1588, "ts": "2026-06-03T18:23:20Z", "hours": 1.2697, "text": "Started Creating the logic and Gameplay with Python. The core ideas are starting to form but a lot of logic is missing."}]...
|
Title: Black Jack Game by @JWNORRIS | Stardance
D Title: Black Jack Game by @JWNORRIS | Stardance
Devlogs:
Started Creating the logic and Gameplay with Python. The core ideas are starting to form but a lot of logic is missing.
Finished the game’s logic, and now it works smoothly with no issues so far....
|
1793152402.533491
|
1793757202.533491
|
|
6489
|
My awesome macropad! by @tautikghosh | Stardance
|
tautikghosh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tautikghosh | Star Title: My awesome macropad! by @tautikghosh | Stardance...
|
1792781586.6923602
|
1793386386.6923602
|
|
6491
|
My awesome macropad! by @fkeblas | Stardance
|
fkeblas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @fkeblas | Stardanc Title: My awesome macropad! by @fkeblas | Stardance...
|
1793407646.8556023
|
1794012446.8556023
|
|
6492
|
Econnect by @Jessie | Stardance
|
Jessie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Econnect by @Jessie | Stardance
|
1792806510.6814394
|
1793411310.6814394
|
|
6493
|
My first slack bot! by @ambition_sisters | Stardan My first slack bot! by @ambition_sisters | Stardance...
|
ambition_sisters
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @ambition_sisters | Title: My first slack bot! by @ambition_sisters | Stardance...
|
1792795907.2555315
|
1793400707.2555315
|
|
6495
|
Coil Gun by @MossyManufacturing | Stardance
|
MossyManufacturing
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Coil Gun by @MossyManufacturing | Stardance
|
1793335775.0172591
|
1793940575.0172591
|
|
6496
|
My first slack bot! by @Jessie | Stardance
|
Jessie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Jessie | Stardance
|
1793371972.0460968
|
1793976772.0460968
|
|
6497
|
My awesome macropad! by @Boden_Wood | Stardance
|
Boden_Wood
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Boden_Wood | Stard Title: My awesome macropad! by @Boden_Wood | Stardance...
|
1793235003.998989
|
1793839803.998989
|
|
6498
|
Untitled by @tautikghosh | Stardance
|
tautikghosh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @tautikghosh | Stardance
|
1793270921.3867812
|
1793875721.3867812
|
|
6499
|
Jinxed by @Jeffrin | Stardance
|
Jeffrin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Jinxed by @Jeffrin | Stardance
|
1793281862.8858953
|
1793886662.8858953
|
|
6501
|
That one macropad by @NotJaxon76 | Stardance
|
NotJaxon76
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: That one macropad by @NotJaxon76 | Stardanc Title: That one macropad by @NotJaxon76 | Stardance...
|
1793253050.6276047
|
1793857850.6276047
|
|
6502
|
My awesome macropad! by @Bekir | Stardance
|
Bekir
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Bekir | Stardance
|
1793156091.8141823
|
1793760891.8141823
|
|
6503
|
amu by @Amu | Stardance
|
Amu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: amu by @Amu | Stardance
|
1793198994.5943267
|
1793803794.5943267
|
|
6504
|
Spesia.it by @gianluca_morello | Stardance
|
gianluca_morello
|
0
|
1.55
|
0
|
[]
|
[{"post_id": 2093, "ts": "2026 [{"post_id": 2093, "ts": "2026-06-04T12:51:28Z", "hours": 1.55, "text": "Created Spesia monorepo and scaffolded the backend (Express + Prisma/Postgres), configured Redis cache and reverse proxy on my Proxmox host, and implemented basic auth + health/profile endpoints. Performed smoke tests to verify the API is reachable and responding."}]...
|
Title: Spesia.it by @gianluca_morello | Stardance
Title: Spesia.it by @gianluca_morello | Stardance
Devlogs:
Created Spesia monorepo and scaffolded the backend (Express + Prisma/Postgres), configured Redis cache and reverse proxy on my Proxmox host, and implemented basic auth + health/profile endpoints. Performed smoke tests to verify the API is reachable and responding....
|
1793170461.4666672
|
1793775261.4666672
|
|
6505
|
System dev logs, drafts by @SamTheArchitect | Star System dev logs, drafts by @SamTheArchitect | Stardance...
|
SamTheArchitect
|
0
|
107.05
|
0
|
[]
|
[{"post_id": 34618, "ts": "202 [{"post_id": 34618, "ts": "2026-07-25T14:27:31Z", "hours": 12.6883, "text": "Workflow Closure & Collapse orchestrator This feature ensures the git commit history remains clean from wips, and the closure when the development of a requirement is finished remains frictionless by automating git operations such as path finding, worktree and branch deletion. Leaving the workspace clean and ready to restart the workflow again for a new update or extra feature. How this engine works Once the builder has complete the implementation, perform a final commit with all changes implemented and staged When the builder runs the command collapse within the worktree to finish the workflow, Then the engine should: Merge the final commit to the main branch The implementation of the requirement wips are preserved in the final commit squash. The history has only one commit with the wip changes The merge is complete successfully Delete the worktree & branch once the commit is present in the main branch to ensure no data is lost and the req name is availability for future implementations Unlink the symlink connection of the markdown editor for the specific docs folder and link to the main docs tree The engine in action"}, {"post_id": 29472, "ts": "2026-07-16T13:23:05Z", "hours": 11.5917, "text": "Git Wortree Set Up & Spawn Orchestrator New functionalities The spawn command is now connected to the orchestrator in the package.json so that it can later be publish in npm and make it fully global accessible in the developer system by using the -g flag Config changes memory: Every time the system changes the system-config.json the changes are automatically staged and commit so that they are present in the new worktree Testing Created two integration automated test using jest that stress test the spawn engine under different scenarios and flags, implement a cool ghost typist so that no questions arise why testing, since those are handle by the ghost typist and test itself. Performed an e2e test in an isolated enviroment within my computer, finding some bugs and fixing them properly. (The video shows the e2e test in action) Fixes The system faced a config path mismatch when the command was trigger when the worktree was outside of a prefix folder and then moved to it, making the config file ENOENT . e2e test e2e spawn engine in action Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Handle the config-system.json presence if not handle its creation Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Connect the docs of the new worktree to the folder in the markdown editor Open a VS code instance"}, {"post_id": 27206, "ts": "2026-07-12T15:48:41Z", "hours": 10.3403, "text": "Git Wortree Set Up & Spawn Orchestrator I develop the initial part of the system requirement of a workflow orchestrator that interacts with git and the system files to create a frictionless, fast and intuitive experience when bringing ideas to live. Creating and isolated environment that ensures the change log remains pristine and connected to a specific Requirement artifact and its context and market value. Command and flags The command that triggers the first part of the orchestrator is spawn with a string argument that will be the name of the requirement to implement e.g: req023 . It can be called with different flags to modify the behavior of the orchestrator and achieve different functionalities: --symlink or -s --code or -c Flag Combinations and what it achieves Scenario A: Git Tree Workflow & Symlink Connection To The Markdown Editor Update Only trigger the command with the -s flag: Creates a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Connect the docs of the new worktree to the folder in the markdown editor Scenario B: Git Tree Workflow Intialization enhance functionality for VSCode instance & Symlink Connection To The Markdown Editor Update Trigger the command with the -s & -c flag: Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Connect the docs of the new worktree to the folder in the markdown editor Open a VS code instance Scenario C: Git Tree Workflow Initialization enhance functionality for VSCode instance Only trigger the command with the -c flag: Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Open a VS code instance Scenario D: Default only worktree creation folder set up Trigger the command without flags: Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Challenges To handle the underlying mechanism of git such as the way it manages the links from the main worktree to its linked ones, how to move them without breaking the linkage and how to heal the systme once the main woerktree is moved represent a challenge that involve some hours of debugging, logs, investigation and testing to make it properly set up the initial state of the system and continue with the worktree creation."}, {"post_id": 25089, "ts": "2026-07-09T02:19:03Z", "hours": 20.9244, "text": "Git staging workflow & pristine version control engineering Context of the problem Now that the system is getting to its final shape one of the most important tools it should integrate is git, but how to do it properly to ensure a pristine commit history to understand the project, its progression, what has been implemented and how the project as evolved over time. Also easily look backwards for quickly identification of the implementation details we are looking for. Nor in a messy uncontextualized way but rather having clear context on what are those changes related to, which requisite is being implemented, refactor or updated Managing docs and code within the same repository carries the risk of “micro commit bloat” only small work and temporary struggle that doesn’t carry a significant weight when backward looking in the future fill the commit history. When reviewing you don’t what to see hundreds of micro commits that doesn’t actually inform of a complete feature. I’ve analize the possible architectural decision including: Workspace squashing and isolated staging of wip commits Git worktrees Clean commit guidelines Clean Room Extraction: 2 branches one for the workspace, containing all the wip messy commits. Edge cases But the one that must be picked is the one that adresses the edge cases: Probable cross device synchronization commits that should not be part of the final commit history. Another key edge case is the synchronization of the cloud repository and the conflict it might cause with the overall sync and the atomic commit history. Handling two REQs that modify the same file in different lines Complete vision of the doc files from the markdown renderer The decision The final decision combines some of the previously mention alternatives and discards others but to make it short the solution is to use worktrees, one per requirement implementation and then clean it out, but this also comes with the frictions of having to update the symlink connection to the markdown editor of preference. Visually explained the architecture is in a digrama below Benefits Semantic commits The repository becomes self-documenting. Generating >“release notes”, “architectural change log” or revising >the project evolution becomes a mathematical query: git log --grep=\"^type\" Structural Bracket Identifier This makes it possible to audit the overall evolution of a >specific requirement implementation or architectural >decision over the project life by using git log --grep=\"[ID]\" . Ease the debugging process and version control >navigation. Git-Tree Concurrent file work history collapse solution: by using >the git-tree the edge case of losing track of multi line >edits that belong to different REQs in the same file is >handled gracefully by the work tree capabilities Dashboard blindness solution: Eliminates dashboard >blindness by using the symlink connection Workflow & the custom Script Finding paths to create symlinks, moving trees to a parent folder so the development can began, the squashing of the commits for a clean history and the merge of wortrees to the main branch migth represent minutes of administrative friction. So the implementation of a script that ease the friction parts of the workflow to ensure the developer never gets out of flow due to administrative stuff is a foundational add on to the system."}, {"post_id": 19990, "ts": "2026-07-01T13:49:00Z", "hours": 41.9653, "text": "Automatic Link Connections Refactor Engine This engine ensures there is no need for manually refactoring of links that connect the related files across the project. Simply imagining updating hundreds of broken links when a name or folder is change, that is not acceptable. Also helps reducing the friction when creating connections like thinking the relative path to the file. This way is avoid the debt of having broken links across the traceability system and friction of connecting files is reduce to 0. Implementation Details File mapping Engineer FileSelectionHelper.js which uses a recursive algorithm that serves as a helper method for data collection using node for file path extraction that works as follows: Extracts the root folder directories and all files paths and names storing them in a data structure. Stores them separately creating a distinction between files and folders. Recursively calls itself to scan the directories stored but before deletes the previously scan directory to ensure the algorithm doesn’t fall in an infinite loop. Stops once there are no more directories to scan. Connections Mapping Implement a helper function PathExtractionHelper.js that will take the found files by FileSelectionHelper.js build a map of the artifacts and the files that mention a connection to them. Algorithm behavior: Loop over all the files of the project Reads the file data an check for a connection mention @trace REQ-001 @ If that artifact exist as a key in the data structure it will append the file, and ensure the already stored connections are not lost Otherwise it will append the first file and create the key Traceability Pipeline Class To ensure clean code, concern separation and functionality encapsulation I develop a class that contains methods that make possible the traceability engine. Methods capabilities: Find artifact path in the project folder Classify artifact connections in different areas Build a markdown table with those connections classification and its relative path to the current artifact ready to navigate by a click from any markdown rendering engine (this ensures the builder can easily open and navigate through the artifact related files, probably implementing what the artifact states) Write the markdown table to a specific artifact.md file Engine execution Once the separated functionalities are encapsulated in its methods and helpers the engine must be orchestrated to provided the expected behavior for this the AutoLinkRefactorExecutionThread.js ensures the execution works as intended leveraging the tools available to ensure the acceptance criteria expected outcome is fulfilled. Testing To ensure system integrity this implementation includes 2 test suits: 6 unit tests for the standalone methods and helpers 1 integration test that ensures that the orchestration of the standalone pieces provide the expected output."}, {"post_id": 11268, "ts": "2026-06-18T13:00:02Z", "hours": 9.5367, "text": "CORE FEATURES Engineer the requirements structure & artifacts including: Kanban Board: How data can be accessed from the requisite Kanban board to increase productivity and maintain a wip (work in progress) of one at the time while visualizing the status and priority of each requisite. Artifacts: Create templates for each of the requisite note artifacts: User Stories, acceptance criteria, Analytical breakdown (Operational procedure to guide problem solving ). Traceability properties: Define the yaml properties for the REQ artifact to ensure traceability form the kanban and the Maps of content dashboard. Define a symlink connection usage from the markdown editor to the project folder with the git system Engineer the architectural decision records structure and artifacts including: Kanban Board: How data can be accessed from the ADRs Kanban board visualize decisions that are pending, approved or depracated Artifacts: Create templates for each of the requisite note artifacts Traceability properties: Define the yaml properties for the ADR artifact to ensure traceability from the kanban and the Maps of content dashboard. Created a central MOC dashboard that maps automatically ADRs, REQs and Vertical slicing diagrams. Includes also an architectural diagram that gives a big picture of how the system behaves."}]...
|
Title: System dev logs, drafts by @SamTheArchitect Title: System dev logs, drafts by @SamTheArchitect | Stardance
Devlogs:
CORE FEATURES Engineer the requirements structure & artifacts including: Kanban Board: How data can be accessed from the requisite Kanban board to increase productivity and maintain a wip (work in progress) of one at the time while visualizing the status and priority of each requisite. Artifacts: Create templates for each of the requisite note artifacts: User Stories, acceptance criteria, Analytical breakdown (Operational procedure to guide problem solving ). Traceability properties: Define the yaml properties for the REQ artifact to ensure traceability form the kanban and the Maps of content dashboard. Define a symlink connection usage from the markdown editor to the project folder with the git system Engineer the architectural decision records structure and artifacts including: Kanban Board: How data can be accessed from the ADRs Kanban board visualize decisions that are pending, approved or depracated Artifacts: Create templates for each of the requisite note artifacts Traceability properties: Define the yaml properties for the ADR artifact to ensure traceability from the kanban and the Maps of content dashboard. Created a central MOC dashboard that maps automatically ADRs, REQs and Vertical slicing diagrams. Includes also an architectural diagram that gives a big picture of how the system behaves.
Automatic Link Connections Refactor Engine This engine ensures there is no need for manually refactoring of links that connect the related files across the project. Simply imagining updating hundreds of broken links when a name or folder is change, that is not acceptable. Also helps reducing the friction when creating connections like thinking the relative path to the file. This way is avoid the debt of having broken links across the traceability system and friction of connecting files is reduce to 0. Implementation Details File mapping Engineer FileSelectionHelper.js which uses a recursive algorithm that serves as a helper method for data collection using node for file path extraction that works as follows: Extracts the root folder directories and all files paths and names storing them in a data structure. Stores them separately creating a distinction between files and folders. Recursively calls itself to scan the directories stored but before deletes the previously scan directory to ensure the algorithm doesn’t fall in an infinite loop. Stops once there are no more directories to scan. Connections Mapping Implement a helper function PathExtractionHelper.js that will take the found files by FileSelectionHelper.js build a map of the artifacts and the files that mention a connection to them. Algorithm behavior: Loop over all the files of the project Reads the file data an check for a connection mention @trace REQ-001 @ If that artifact exist as a key in the data structure it will append the file, and ensure the already stored connections are not lost Otherwise it will append the first file and create the key Traceability Pipeline Class To ensure clean code, concern separation and functionality encapsulation I develop a class that contains methods that make possible the traceability engine. Methods capabilities: Find artifact path in the project folder Classify artifact connections in different areas Build a markdown table with those connections classification and its relative path to the current artifact ready to navigate by a click from any markdown rendering engine (this ensures the builder can easily open and navigate through the artifact related files, probably implementing what the artifact states) Write the markdown table to a specific artifact.md file Engine execution Once the separated functionalities are encapsulated in its methods and helpers the engine must be orchestrated to provided the expected behavior for this the AutoLinkRefactorExecutionThread.js ensures the execution works as intended leveraging the tools available to ensure the acceptance criteria expected outcome is fulfilled. Testing To ensure system integrity this implementation includes 2 test suits: 6 unit tests for the standalone methods and helpers 1 integration test that ensures that the orchestration of the standalone pieces provide the expected output.
Git staging workflow & pristine version control engineering Context of the problem Now that the system is getting to its final shape one of the most important tools it should integrate is git, but how to do it properly to ensure a pristine commit history to understand the project, its progression, what has been implemented and how the project as evolved over time. Also easily look backwards for quickly identification of the implementation details we are looking for. Nor in a messy uncontextualized way but rather having clear context on what are those changes related to, which requisite is being implemented, refactor or updated Managing docs and code within the same repository carries the risk of “micro commit bloat” only small work and temporary struggle that doesn’t carry a significant weight when backward looking in the future fill the commit history. When reviewing you don’t what to see hundreds of micro commits that doesn’t actually inform of a complete feature. I’ve analize the possible architectural decision including: Workspace squashing and isolated staging of wip commits Git worktrees Clean commit guidelines Clean Room Extraction: 2 branches one for the workspace, containing all the wip messy commits. Edge cases But the one that must be picked is the one that adresses the edge cases: Probable cross device synchronization commits that should not be part of the final commit history. Another key edge case is the synchronization of the cloud repository and the conflict it might cause with the overall sync and the atomic commit history. Handling two REQs that modify the same file in different lines Complete vision of the doc files from the markdown renderer The decision The final decision combines some of the previously mention alternatives and discards others but to make it short the solution is to use worktrees, one per requirement implementation and then clean it out, but this also comes with the frictions of having to update the symlink connection to the markdown editor of preference. Visually explained the architecture is in a digrama below Benefits Semantic commits The repository becomes self-documenting. Generating >“release notes”, “architectural change log” or revising >the project evolution becomes a mathematical query: git log --grep="^type" Structural Bracket Identifier This makes it possible to audit the overall evolution of a >specific requirement implementation or architectural >decision over the project life by using git log --grep="[ID]" . Ease the debugging process and version control >navigation. Git-Tree Concurrent file work history collapse solution: by using >the git-tree the edge case of losing track of multi line >edits that belong to different REQs in the same file is >handled gracefully by the work tree capabilities Dashboard blindness solution: Eliminates dashboard >blindness by using the symlink connection Workflow & the custom Script Finding paths to create symlinks, moving trees to a parent folder so the development can began, the squashing of the commits for a clean history and the merge of wortrees to the main branch migth represent minutes of administrative friction. So the implementation of a script that ease the friction parts of the workflow to ensure the developer never gets out of flow due to administrative stuff is a foundational add on to the system.
Git Wortree Set Up & Spawn Orchestrator I develop the initial part of the system requirement of a workflow orchestrator that interacts with git and the system files to create a frictionless, fast and intuitive experience when bringing ideas to live. Creating and isolated environment that ensures the change log remains pristine and connected to a specific Requirement artifact and its context and market value. Command and flags The command that triggers the first part of the orchestrator is spawn with a string argument that will be the name of the requirement to implement e.g: req023 . It can be called with different flags to modify the behavior of the orchestrator and achieve different functionalities: --symlink or -s --code or -c Flag Combinations and what it achieves Scenario A: Git Tree Workflow & Symlink Connection To The Markdown Editor Update Only trigger the command with the -s flag: Creates a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Connect the docs of the new worktree to the folder in the markdown editor Scenario B: Git Tree Workflow Intialization enhance functionality for VSCode instance & Symlink Connection To The Markdown Editor Update Trigger the command with the -s & -c flag: Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Connect the docs of the new worktree to the folder in the markdown editor Open a VS code instance Scenario C: Git Tree Workflow Initialization enhance functionality for VSCode instance Only trigger the command with the -c flag: Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Open a VS code instance Scenario D: Default only worktree creation folder set up Trigger the command without flags: Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Challenges To handle the underlying mechanism of git such as the way it manages the links from the main worktree to its linked ones, how to move them without breaking the linkage and how to heal the systme once the main woerktree is moved represent a challenge that involve some hours of debugging, logs, investigation and testing to make it properly set up the initial state of the system and continue with the worktree creation.
Git Wortree Set Up & Spawn Orchestrator New functionalities The spawn command is now connected to the orchestrator in the package.json so that it can later be publish in npm and make it fully global accessible in the developer system by using the -g flag Config changes memory: Every time the system changes the system-config.json the changes are automatically staged and commit so that they are present in the new worktree Testing Created two integration automated test using jest that stress test the spawn engine under different scenarios and flags, implement a cool ghost typist so that no questions arise why testing, since those are handle by the ghost typist and test itself. Performed an e2e test in an isolated enviroment within my computer, finding some bugs and fixing them properly. (The video shows the e2e test in action) Fixes The system faced a config path mismatch when the command was trigger when the worktree was outside of a prefix folder and then moved to it, making the config file ENOENT . e2e test e2e spawn engine in action Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there Handle the config-system.json presence if not handle its creation Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix Connect the docs of the new worktree to the folder in the markdown editor Open a VS code instance
Workflow Closure & Collapse orchestrator This feature ensures the git commit history remains clean from wips, and the closure when the development of a requirement is finished remains frictionless by automating git operations such as path finding, worktree and branch deletion. Leaving the workspace clean and ready to restart the workflow again for a new update or extra feature. How this engine works Once the builder has complete the implementation, perform a final commit with all changes implemented and staged When the builder runs the command collapse within the worktree to finish the workflow, Then the engine should: Merge the final commit to the main branch The implementation of the requirement wips are preserved in the final commit squash. The history has only one commit with the wip changes The merge is complete successfully Delete the worktree & branch once the commit is present in the main branch to ensure no data is lost and the req name is availability for future implementations Unlink the symlink connection of the markdown editor for the specific docs folder and link to the main docs tree The engine in action...
|
1793256970.6733804
|
1793861770.6733804
|
|
6506
|
Playback Control MacroPad by @Landon | Stardance
|
Landon
|
0
|
3.49
|
0
|
[]
|
[{"post_id": 4587, "ts": "2026 [{"post_id": 4587, "ts": "2026-06-07T22:39:24Z", "hours": 2.3142, "text": "finalizing PCB and some basic cad did a lil bit or drawing, and a bit more routing. today just made some tlittle tweaks, added bolt holes, changed pcb size and rewired. started with some cad and making a case for my macro/hackpad"}, {"post_id": 1864, "ts": "2026-06-04T02:26:10Z", "hours": 1.1781, "text": "#Re learning kicad# today i spent way too long importing footprints, looking for footprints, and everything in between, im happy to have come up with a semi finished product that would work at the stage its in. next time im going to find a fitting rotary encoder and inegrate it! hopefully i can get a screen on this little guy too"}]...
|
Title: Playback Control MacroPad by @Landon | Star Title: Playback Control MacroPad by @Landon | Stardance
Devlogs:
#Re learning kicad# today i spent way too long importing footprints, looking for footprints, and everything in between, im happy to have come up with a semi finished product that would work at the stage its in. next time im going to find a fitting rotary encoder and inegrate it! hopefully i can get a screen on this little guy too
finalizing PCB and some basic cad did a lil bit or drawing, and a bit more routing. today just made some tlittle tweaks, added bolt holes, changed pcb size and rewired. started with some cad and making a case for my macro/hackpad...
|
1793418542.1844559
|
1794023342.1844559
|
|
6508
|
SkyAware by @andychenweizhao | Stardance
|
andychenweizhao
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SkyAware by @andychenweizhao | Stardance
|
1793231726.7707505
|
1793836526.7707505
|
|
6509
|
Untitled project by @akaki | Stardance
|
akaki
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @akaki | Stardance
|
1793397000.481282
|
1794001800.481282
|
|
6510
|
My awesome macropad! by @HamzaEren | Stardance
|
HamzaEren
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @HamzaEren | Starda Title: My awesome macropad! by @HamzaEren | Stardance...
|
1792752878.1048586
|
1793357678.1048586
|
|
6511
|
My first slack bot! by @Sol75 | Stardance
|
Sol75
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Sol75 | Stardance
|
1793238470.200646
|
1793843270.200646
|
|
6512
|
My awesome macropad! by @najil_kilayil | Stardance
|
najil_kilayil
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @najil_kilayil | St Title: My awesome macropad! by @najil_kilayil | Stardance...
|
1792939655.09829
|
1793803655.09829
|
|
6513
|
Untitled project by @kaabia_ahmed2009 | Stardance
|
kaabia_ahmed2009
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @kaabia_ahmed2009 | Sta Title: Untitled project by @kaabia_ahmed2009 | Stardance...
|
1793274780.448163
|
1793879580.448163
|
|
6514
|
My first slack bot! by @Lavender | Stardance
|
Lavender
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Lavender | Stardanc Title: My first slack bot! by @Lavender | Stardance...
|
1793389912.5788634
|
1793994712.5788634
|
|
6515
|
Minecraft weapon mod by @CalebRivera | Stardance
|
CalebRivera
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Minecraft weapon mod by @CalebRivera | Star Title: Minecraft weapon mod by @CalebRivera | Stardance...
|
1793432894.9810169
|
1794037694.9810169
|
|
6516
|
My first slack bot! by @lucy_stiglitz | Stardance
|
lucy_stiglitz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @lucy_stiglitz | Sta Title: My first slack bot! by @lucy_stiglitz | Stardance...
|
1793181283.0180004
|
1793786083.0180004
|
|
6518
|
My first slack bot! by @lucy_stiglitz | Stardance
|
lucy_stiglitz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @lucy_stiglitz | Sta Title: My first slack bot! by @lucy_stiglitz | Stardance...
|
1793372040.6643178
|
1793976840.6643178
|
|
6519
|
Personal OS by @PyroProtato | Stardance
|
PyroProtato
|
0
|
0.37
|
0
|
[]
|
[{"post_id": 5110, "ts": "2026 [{"post_id": 5110, "ts": "2026-06-08T19:56:26Z", "hours": 0.3683, "text": "Started basic HTML!"}]...
|
Title: Personal OS by @PyroProtato | Stardance
De Title: Personal OS by @PyroProtato | Stardance
Devlogs:
Started basic HTML!...
|
1793180871.9659262
|
1793785671.9659262
|
|
6520
|
Unus by @laurynas_lubauskas | Stardance
|
laurynas_lubauskas
|
0
|
10.23
|
0
|
[]
|
[{"post_id": 8640, "ts": "2026 [{"post_id": 8640, "ts": "2026-06-14T11:17:37Z", "hours": 1.2636, "text": "Day 6 I added this feature a few days ago, but I was too lazy to write a devlog, but I will now. So I added a reply button to in the AI assistant. It wasn’t so hard just I needed to search a lot and even went into the second page of google. It is a vital feature, because when I added the AI assistant it asked a question and I couldn’t answer, because there was no reply button. That is it for today/few days ago. Thanks for taking your assisted mind to read it :P"}, {"post_id": 6376, "ts": "2026-06-10T18:52:22Z", "hours": 2.6589, "text": "Day 5 Today I was sick so I had some time to add AI to my browser! It took me a while but I did it with no bugs/problems. I was deciding a long time between different AI models that I could use for my browser, but I choose grok. It wasn’t my first option, but it was the only free api that was available. I know it’s not the best AI model, but it will do for the moment. Right after adding AI I went to test it and I found that I can’t respond to grok when it asks questions. So now thats what I am trying to add. I hope I will do it tomorrow or in the next few days. I am really happy that I was able to add the AI. It took me a while to research everything. Thanks for taking your Intelligent time to read this ;o Get it?"}, {"post_id": 5137, "ts": "2026-06-08T20:29:15Z", "hours": 1.3672, "text": "Day 4 Today I kinda finished the ui even tho in the future I will add more. Today I was brainstorming ideas for the features that I could add. I decided on ai integration into the browser. I think ai is a great feature especially when you search something and you dont need to enter random sketchy websites. It shows what you searched for. I’m hoping on adding the feature tomorrow, or at least starting to add. This is all for today. I think the new ui looks way better and I hope to make it even better. Thanks for taking your sweetest time to read this :D"}, {"post_id": 4493, "ts": "2026-06-07T20:28:46Z", "hours": 1.9892, "text": "Unus Day 3 During the weekend I didn’t code just Sunday evening. I am updating the ui once again and I am changing a lot of the python code and it takes a lot of time and I still need to update the qss file. My idea after I finish the ui is adding the features to the browser. I think features is the main “selling point” of a browser. Since I am updating the python file you cant see the ui difference in the browser so I will just attach a screenshot of the code! Bye ;D"}, {"post_id": 2351, "ts": "2026-06-04T20:01:08Z", "hours": 1.7922, "text": "Unus Day 2 Today I worked on optimizing the code for the ui. My first code was not optimized for ui and I needed to do lots of changes before I could create a style.qss file. I worked a lot on optimizing the code today, so I didn’t have time to do some improvement on the ui, but there is a few minor differences. I don’t know if I will log a lot of hours during the weekend. This was all for today thanks for reading!"}, {"post_id": 1627, "ts": "2026-06-03T19:16:08Z", "hours": 1.1547, "text": "Unus Day 1 Hi, This is my first devlog and i took 1h 9m to create the “backbone/base” of the browser. The browser is based on chromium and I used python for the code. I still need to do lots of ui design and other features. I might try adding ai to the browser, but that’s a big question mark. By the end I hope to have a full nice browser with lots of features. I will try to make it so that people could download my browser. This is all for today. My summer holidays start in less than 3 weeks so during the summer holidays I want to absolutely perfect this browser. Thanks for taking your time to read this!"}]...
|
Title: Unus by @laurynas_lubauskas | Stardance
De Title: Unus by @laurynas_lubauskas | Stardance
Devlogs:
Unus Day 1 Hi, This is my first devlog and i took 1h 9m to create the “backbone/base” of the browser. The browser is based on chromium and I used python for the code. I still need to do lots of ui design and other features. I might try adding ai to the browser, but that’s a big question mark. By the end I hope to have a full nice browser with lots of features. I will try to make it so that people could download my browser. This is all for today. My summer holidays start in less than 3 weeks so during the summer holidays I want to absolutely perfect this browser. Thanks for taking your time to read this!
Unus Day 2 Today I worked on optimizing the code for the ui. My first code was not optimized for ui and I needed to do lots of changes before I could create a style.qss file. I worked a lot on optimizing the code today, so I didn’t have time to do some improvement on the ui, but there is a few minor differences. I don’t know if I will log a lot of hours during the weekend. This was all for today thanks for reading!
Unus Day 3 During the weekend I didn’t code just Sunday evening. I am updating the ui once again and I am changing a lot of the python code and it takes a lot of time and I still need to update the qss file. My idea after I finish the ui is adding the features to the browser. I think features is the main “selling point” of a browser. Since I am updating the python file you cant see the ui difference in the browser so I will just attach a screenshot of the code! Bye ;D
Day 4 Today I kinda finished the ui even tho in the future I will add more. Today I was brainstorming ideas for the features that I could add. I decided on ai integration into the browser. I think ai is a great feature especially when you search something and you dont need to enter random sketchy websites. It shows what you searched for. I’m hoping on adding the feature tomorrow, or at least starting to add. This is all for today. I think the new ui looks way better and I hope to make it even better. Thanks for taking your sweetest time to read this :D
Day 5 Today I was sick so I had some time to add AI to my browser! It took me a while but I did it with no bugs/problems. I was deciding a long time between different AI models that I could use for my browser, but I choose grok. It wasn’t my first option, but it was the only free api that was available. I know it’s not the best AI model, but it will do for the moment. Right after adding AI I went to test it and I found that I can’t respond to grok when it asks questions. So now thats what I am trying to add. I hope I will do it tomorrow or in the next few days. I am really happy that I was able to add the AI. It took me a while to research everything. Thanks for taking your Intelligent time to read this ;o Get it?
Day 6 I added this feature a few days ago, but I was too lazy to write a devlog, but I will now. So I added a reply button to in the AI assistant. It wasn’t so hard just I needed to search a lot and even went into the second page of google. It is a vital feature, because when I added the AI assistant it asked a question and I couldn’t answer, because there was no reply button. That is it for today/few days ago. Thanks for taking your assisted mind to read it :P...
|
1793195512.6469765
|
1793800312.6469765
|
|
6521
|
Rogue-Lite Top Down Shooter by @Orangeson76 | Star Rogue-Lite Top Down Shooter by @Orangeson76 | Stardance...
|
Orangeson76
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Rogue-Lite Top Down Shooter by @Orangeson76 Title: Rogue-Lite Top Down Shooter by @Orangeson76 | Stardance...
|
1793310693.6533628
|
1793915493.6533628
|
|
6523
|
Pet Rock Web Page by @Aster_ | Stardance
|
Aster_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Pet Rock Web Page by @Aster_ | Stardance
|
1793371695.7712853
|
1793976495.7712853
|
|
6524
|
My first slack bot! by @DheerajS | Stardance
|
DheerajS
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @DheerajS | Stardanc Title: My first slack bot! by @DheerajS | Stardance...
|
1793433086.4321826
|
1794037886.4321826
|
|
6525
|
Career.com by @Hannah | Stardance
|
Hannah
|
0
|
4.74
|
0
|
[]
|
[{"post_id": 78816, "ts": "202 [{"post_id": 78816, "ts": "2026-10-11T17:56:16Z", "hours": 2.3972, "text": "Worked on the sql connectivity todayy^^"}, {"post_id": 11258, "ts": "2026-06-18T12:41:09Z", "hours": 1.1633, "text": "Working on some evaluation questions today :)"}, {"post_id": 10590, "ts": "2026-06-17T12:29:48Z", "hours": 1.1794, "text": "started the project today^^"}]...
|
Title: Career.com by @Hannah | Stardance
Devlogs: Title: Career.com by @Hannah | Stardance
Devlogs:
started the project today^^
Working on some evaluation questions today :)
Worked on the sql connectivity todayy^^...
|
1792792098.9568172
|
1793396898.9568172
|
|
6526
|
Untitled by @Orangeson76 | Stardance
|
Orangeson76
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Orangeson76 | Stardance
|
1793389671.1201017
|
1793994471.1201017
|
|
6527
|
Untitled by @Liza | Stardance
|
Liza
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Liza | Stardance
|
1793454750.9037704
|
1794059550.9037704
|
|
6529
|
My first slack bot! by @st4r21722 | Stardance
|
st4r21722
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @st4r21722 | Stardan Title: My first slack bot! by @st4r21722 | Stardance...
|
1792770580.4891202
|
1793375380.4891202
|
|
6530
|
My awesome macropad! by @SamBair | Stardance
|
SamBair
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @SamBair | Stardanc Title: My awesome macropad! by @SamBair | Stardance...
|
1792752531.6781406
|
1793357331.6781406
|