---
# System prepended metadata

title: Dan's Notebook Fall 2023
tags: [lluf-notebook, dan-t]

---

# Dan's Notebook Fall 2023

## BIO-LLUFOGRAPHY
#### my lluf catch phrase:
*noun*: a well-known sentence or phrase, especially one that is associated with a particular famous person. 
you = LL famous!
#### lab: 
code-lab
#### tools I can help others with:
* (Basic) web dev questions
* Python, C++, HTML, css
* canva
#### my personal learning goals for this fall:
My goal for this semester is to gain more real world experience in coding and working with web development while also building up work experience on various events, activities and a wide range of projects. I'm excited to join a lab to continue learning new technologies and incorporating them in a creative way. This blend of creativity and technology is something that I am very passionate about so I'm excited to get more experience blending those two fields together. 

I am also just excited to be working in a new space where I can meet new friends and work alongside people that I already know in such a supportive and creative environment! There are so many cool technologies and tools that I want to learn here that I'm so excited to have the opportunity to work with and I look forward to being able to just have fun with them! 


## key links:
* links you may want to reference often!
* [The LLUF Guidebook for Fall 2023](/Hd1PfV98Q3GXuE5gykSvEA)
* [Work Response Form](https://airtable.com/appCm7g0XXkDhNB9v/shr5OaDtqIJCubFGj)
* [Weekly Update Form](https://airtable.com/appCm7g0XXkDhNB9v/shreQhF2GmuXCGpzV)

## dashboard:
a place for you to keep notes that you commonly refer to! For example, maybe a table of shortcut keys you need help remembering and commonly use:



| Shortcut Key | What It Does | 
| -------- | -------- | 
| command + tab     | toggles between apps!     | 
| command + space     | search and open app     | 
| I & O  & E   | in FCPX,  selects in and out points in footage and adds to end of timeline   | 

NOTE: do NOT put any "secret" info here like passwords!


## drafting space:
use this space to draft the markdown that you will paste into your work responses and weekly updates. it will help you to see the output and make sure the formatting and media are what you want! Then you can simply copy and paste that into the markdown prompt within those forms!

Here is a sample draft for the Markdown Update field in the Weekly Update Form:

## WEEK 1: Basic Training

This week, I spent my time on Monday and Thursday going through the Basic Training Package and submitting my work. I completed the case challenge, found all of the materials within the Learning Lab, and created my buttons for my creator brand. This week was just as much about learning about how the Learning Lab functions and how to go about doing work here than it was about the actual work I did, but I think I am adjusting well and I'm excited to join a lab and get started on an ILP. 

![alt text](https://files.slack.com/files-pri/T0HTW3H0V-F05TSFWFZDH/img_2710.jpg?pub_secret=f85283964e)

![alt text](https://files.slack.com/files-pri/T0HTW3H0V-F05TY2PHANB/dan_tracy_buttons.png?pub_secret=5c3fb52b2e)

## WEEK 2: FINISHING BASIC TRAINING PACKAGE, MOVING ON TO ILP
This week, I spent my time on Monday finishing up my training package, which mostly involved just finishing up with reading about the learning lab and selecting which lab I want to be a part of. Ultimately, I chose to be a part of CodeLab which is very exciting. Thursday I started looking at the ILP for CodeLab but couldn't get too far into it because I was assisting a DesignLab Testing of a project which was really fun and a unique project that I hadn't thought to do before.

## WEEK 10/12 - 10/19: CONTINUING WORKING ON ILP
This week, I spent my time at the Learning Lab working on the ILP and trying to work around my computer breaking, which was a struggle. Because of my computer being unusable, I have been using the Learning Lab computers while working on my project, which has been fine but I am still getting used to working with Macs and it has been a slight learning curve. The actual ILP itself has been going well, I have never worked with APIs before so it has been a new experience to research what exactly I am doing before I implement it and that has been really interesting to me. Having Christine's repository to look at has been helpful not to copy the code but to go through what the code is doing in each function and why I want that to happen. There is definitely still more to be done on the ILP but I've made progress. I do want to try to sync the work I've done on the learning lab computer into my own GitHub though because it would be ideal to work on it on my computer instead of havign to rely on this system I'm not as familiar with. 

## WEEK OF 10/19 - 10/26: CONTINUING WORKING ON ILP
This week, I spent most of my time working on my ILP and trying to sync my ILP so that I could access it on my GitHub and work on it on my personal computer instead of having to use the Learning Lab computer just because it is either to have that access and be able to have everything in one plce. I have gotten pretty far in the ILP but I had trouble on Thursday with my localhost just not working and it kept giving a 404 error when I ran npm run dev. It ended up being okay because I then spent my time on other tasks like connecting the repository to my GitHub and things like that, but that is something that hopefully was temporary and is not something that will be a continual problem. The timeline for finishing the ILP by the end of next week should hopefully be doable I just need to figure out the one or two bugs that are preventing my code from being runnable which was not a problem before. 

## WEEK OF 10/26 - 11/02: FINAL WEEK OF ILP WORK
The final week of working on my ILP was not everything I had hoped it would be as most of the time I spent struggling and fighting with npm run dev and the 404 error that it was giving me. Of the 5 hours I spent in the learning lab this week, approximately 4.5 of those were spent trying different ways to get my program to run instead of giving me an error, which was very unfortunate. In the end, I got my webapp to run by essentially uninstalling and unlinking everything to do with node on the computer and then completely rebooting and reinstalling node and finally that got the program to run. Other methods I had tried during the week were to sync it to GitHub and try to run it on my personal computer and trying to run it on a different Learning Lab Computer, but both times I ran into errors. I was not fully able to finish my ILP because of this essentially two week delay but I am close and I'm proud of the work that I did even though it is not fully complete and there are errors fetching data from airtable.

## WEEK(S) OF 11/03-11/20: WORKING ON PRINTABLE WORK TEMPLATES
Over the last two weeks at the Learning Lab I have been working on a task to create a printable cards for the various tasks at the Learning Labs. This has involved creating a new nextapp and then setting up an api route to access AirTable to get the jobs that are posted to the lluf-base. The biggest issue I ran into was accessing one table within a base which was a larger issue than I had anticipated and led to a lot of api and access problems which I am still sorting through. Christine has been helping me figure out how to work around this problem but she was also experiencing similar issues so I am at least comforted knowing that I am not the only one who found that task shockingly challenging. One of my biggest errors is that I thought I needed both an API route and a utility to access the data but I think now I only need an API route which simplifies my code. I am still getting some errors so I am not done, but once this roadblock is passed the rest of the project should be easy tweaks to the code formatting. 

## WEEK OF 11/23 - 11/30: Thanksgiving, Migraines, Continued Stalemate

---
Why there hasn't been a weekly update in a while is mostly due to outside factors which have limited the amount of time I've been in the learning lab. Since my last update on 11/23, I have only been in the learning lab for one shift, which was Monday 11/27. On the thursday of that week I had to call out because I had a horrible migraine so I unfortunately couldn't come to work at all that day. With that said, with only one visit to the learning lab and only 3 hours spent total, very minimal progress has been made. I talked to Christine about her updated status on the project and she was in a very similar place to me, at a stalemate with making data show up in our nextapps, which has proved to be a frustrating process. 

## Links for Hist 16D Project: 
https://datajournalism.com/read/longreads/how-data-captured-americas-protests

https://www.nytimes.com/interactive/2020/07/03/us/george-floyd-protests-crowd-size.html

https://www.nytimes.com/interactive/2024/01/04/us/january-6-capitol-trump-investigation.html

https://pudding.cool/2020/10/police-misconduct/

https://studentwork.prattsi.org/infovis/visualization/protests-in-us-20172020/

https://www.washingtonpost.com/graphics/2020/national/live-stream-george-floyd-protests/


| Type of Work | Time Spent | Notes
| -------- | -------- | -------- |
| Learning     | 3:00    | Worked on Job Card project   |
| Testing     | 0:00     | Tested for project in History of Art and Architecture    |
| Collecting     | 00:00     | this includes any work request tagged "collect"     |
| Prepping     | 00:00     | this includes any work request tagged "prep"     |
| Maintaining     | 00:00     | this includes any cleaning or organizing or set up requests. work request tagged "maintain"     |




