helenchong/helenchong.dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Replace categories links to topic links

Browse Source
This commit is contained in:
Helen Chong
2025-05-07 19:51:24 +08:00
parent 90097f6aaa
commit 3154dfb5c5
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/blog/posts/2025-04-13-42-piscine-first-week.md
View File

@@ -11,7 +11,7 @@ Despite having attended the Discovery Piscine to get a taste of what the Piscine
A key to succeed the projects is to pay close attention to the details of the project exercise requirements and examples. A good thing is, one of the ways 42 is not a traditional school is that we can retry projects even if we failed. During my first try of the Piscine's very first project, which was about shell commands, I failed due to not paying enough attention to the details of the exercise requirements, but after learning my mistakes and retrying the project, I succeeded by passing both peer and automatic evaluations.
I had learned C when I took [CS50's Introduction to Computer Science course](/blog/categories/cs50x), but it has been a while since I wrote C, so the Piscine served as a good opportunity to refresh my C skills and knowledge. I started the Piscine's first C project on April 10, and despite already having some background in C, I still got to learn some things about C that I was not aware of before, such as the `write()` function. That said, refreshing my C knowledge and skills by starting the C projects in the Piscine's curriculum certainly helped me to pass the Piscine's first exam on April 11.
I had learned C when I took [CS50's Introduction to Computer Science course](/blog/topics/cs50x), but it has been a while since I wrote C, so the Piscine served as a good opportunity to refresh my C skills and knowledge. I started the Piscine's first C project on April 10, and despite already having some background in C, I still got to learn some things about C that I was not aware of before, such as the `write()` function. That said, refreshing my C knowledge and skills by starting the C projects in the Piscine's curriculum certainly helped me to pass the Piscine's first exam on April 11.
After the weekly exam happened on Fridays, we got assigned weekly group projects to do during the weekends, with our team members being generated randomly. The first group project was easy enough for my team to complete it on Saturday, including alternate versions of the project as an opportunity to earn bonus points. Therefore, I got to take one day break on Sunday, but I still need to prepare for the possibility of needing to visit the campus for group projects in Sundays in the next few weeks.

2
src/blog/posts/2025-05-04-42-piscine-completed.md
View File

@@ -5,7 +5,7 @@ date: 2025-05-04T11:05:16+0800
topics: ["42 the school", "c", "life updates"]
---
2 May 2025 marked the final day of [42 the computer science school](/blog/categories/42-the-school/)'s 26-day bootcamp, named the Piscine, that I was attending. The final day of the Piscine was also when the final exam took place. I am happy to announce that I have completed the Piscine, by taking and passing the final exam!
2 May 2025 marked the final day of [42 the computer science school](/blog/topics/42-the-school/)'s 26-day bootcamp, named the Piscine, that I was attending. The final day of the Piscine was also when the final exam took place. I am happy to announce that I have completed the Piscine, by taking and passing the final exam!
This intake of bootcamp started on April 7, and the intense and challenging curriculum meant April had been my busiest month since forever. Despite already having learned C before attending the Piscine, I still got to learn things about C that I did not before, such as using the `write()` function instead of `printf()` to print out something in the terminal, creating a Makefile for the first time ever as part of one of the solo projects, and having fun with it.