Week 1 summary of code and problems faced
Monday
On Monday, me and my partner Sathvik began the day by installing the nessasary tools fo the course. A few of the tools included, docker, anaconda, vscode, slack etc. At one step, namely make both of use could not progress further as we faced the same error error1. This little error stopped us from moving further. We tried a lot of things but none of it seemed to work the make command. Finally chatgpt helped out solving the problem with the two commands.
bundle install and bundle update
Tuesday
Although the bundle update code worked to fix the make error for me the same did not work for Sathvik’s error. Thus we kept working around the code as our presentation was the next day. We tried many new things but the make code still did not seem to work on Sathvik’s computer. After a while Saathvik seemed to solve the code on his his by closing and reopening the vscode terminal which seemed to fix the make error once and for all. We then worked on our speeches for our first tool check which was scheduled for the next day.
Wednesday
Today was the day of our tool check. We were the first to be called on as the previous group did no seem to answer their call. We then explained all the we did, our main make error and how we seem to have fixed the error and also show the changes we made to our home change inlcuding the addition of the our freeform introductory picture. We then finished our presentation with a total score of 1.8 and 1.85 each. Overall i felt it was a pretty well done presentation. I then changed my theme to hacker for the theme change point. Before class ended I seem to have got the make error back, I tried the same bundle update but it didnt seem to work. Fianlly this code which one of my classmate had sent in worked to fix my make error.
ln -s /opt/homebrew/share/jupyter/nbconvert ~/Library/Jupyter
Thursday
On Thurday since the tool check was still going on for our peers we continued to customize our home page and also worked on helping oour peers with the samll problems they faced here and there including a few make error here and there. Overall this was a pretty small day as there was not a lot of coding involved.
Friday
On Friday we started really coding into new blogs and also use new code such as python and Java. The two new project that me and my partner worked on were, the Javascript calculator and the python input output quiz which was mainly about about the new commands that I leanrnt in the markdown code. The list of the code i learnt and used throughout the week are listed below.
Key Vocabulary Learnt
| Commands | Definition | Week |
|---|---|---|
| make | This runs local severer | Week 0 |
| print () | In Python code the print code literally prints the message onto the site, similar to the used in HTML</td> | Week 1 | </tr>
| cd | Changes directories within a folder | Week 0 |
| ls | Checks all the directories in a folder. | Week 0 |
| --version | Checks for the version of each of the application installed. It really helped out during the installation process. | Week 1 |
| **xyz** | Changes the boldness of the text as well as the italics part of the text. | Week 1 |
| Command S | Saves the code into the local server | Week 1 |
| Commit on VScode | Commits the code into the github terminal and the site | Week 1 |
| ### | Highlights the peice of text as a heading. The larger it gets the smaller the heading. | Week 1 |