feat: daily log
This commit is contained in:
18
daily-log.md
18
daily-log.md
@@ -1,6 +1,22 @@
|
||||
# Daily Logs
|
||||
|
||||
## 2026-01-22 - (Thu) Nand2Tetris Unit
|
||||
## 2026-01-26 - (Mon) Nand2Tetris Unit 4
|
||||
|
||||
**Tasks:** Watch the material on Unit 04.
|
||||
**Blocker:** Not enough time to watch all of it in one day.
|
||||
**Lesson:** Learned of the Hack Assembly Machine Language and Machine Assembly Language in general. Looking forward to learn more.
|
||||
**Tomorrow:** Continue with the material. Video and text.
|
||||
**Time Spent:** 90m
|
||||
|
||||
## 2026-01-23 - (Fri) Nand2Tetris Unit 3
|
||||
|
||||
**Tasks:** Finalize the project. Completing the Program Counter (PC)
|
||||
**Blocker:** Was struggling a little bit with it. Could not figure out how to route the logic. The programmer mindset kept me back. You can't just loop and if statement your way out of it. No early returns.
|
||||
**Lesson:** Had to wire them together from their inputs to their outputs.
|
||||
**Tomorrow:** Start Unit 4
|
||||
**Time Spent:**90m
|
||||
|
||||
## 2026-01-22 - (Thu) Nand2Tetris Unit 3
|
||||
|
||||
**Tasks:** Finalize the reading on Unit 3 and start the project.
|
||||
**Blocker:** Full understanding of what happened.I kind of got it at the end when I implemented the RAM8. The bit & register made sense, but was struggling a little bit with RAM implementation. Had to figure out how to route things the right way. dMux8Way and Mux8Way.
|
||||
|
||||
Reference in New Issue
Block a user