Skip to content
TheChatArchiveThe Chat Archive
Qwenqwen3-235b-a22b-no-thinking· Alibaba (Qwen)Hugging Face LMArena Human Preference 140K

From where are we going to learn all of the things

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with DeepSeekdeepseek-v3-0324’s answer.
  1. User

    From where are we going to learn all of the things

  2. Qwen Assistant

    Great question! Since the 42 Piscine (especially at 42 Heilbronn) is project-based and doesn’t have traditional teachers, you’ll need to teach yourself using online resources, documentation, and peer collaboration.

    Here’s a comprehensive list of learning sources, organized by subject, that will help you prepare for everything you'll encounter during the Piscine — from day one!


    🧠 Where to Learn: Subject-by-Subject

    1. UNIX Shell / Terminal Basics

    You’ll use this every day in the Piscine.

    🔹 Recommended Resources:

    🔹 Practice Sites:


    2. Git & Version Control

    Used daily to submit your projects.

    🔹 Recommended Resources:

    🔹 Practice:

    • Use GitHub or GitLab to create test repositories.
    • Practice pushing code to remote repos (git push, git pull, git commit).

    3. C Programming Language

    This is the core of Weeks 2–4 of the Piscine.

    🔹 Recommended Books:

    🔹 Video Courses:

    • Harvard CS50 (Weeks 1–3): CS50 on YouTube
      • Week 1 covers basic C syntax.
    • freeCodeCamp C Tutorial: Intro to C Programming
    • Caleb Curry (YouTube): Search "C programming tutorial" – he has excellent beginner-friendly playlists.

    🔹 Practice Platforms:


    4. Pointers, Memory Allocation, and Data Structures

    These topics come up heavily in Weeks 3–4.

    🔹 Resources:

    🔹 Practice:

    • Write small programs using malloc, calloc, realloc, and free.
    • Implement simple linked lists manually.

    5. VIM / Text Editor in Terminal

    During exams, you may be restricted to VIM only.

    🔹 Learning Resources:

    🔹 Practice:

    • Open files with vim, write some text, save and quit (:wq).
    • Learn basic navigation and insert mode.

    6. Problem Solving and Logical Thinking

    This is key to passing the Moulinette and final exam.

    🔹 Practice Platforms:

    • Codewars – Do C katas
    • LeetCode – Easy problems
    • Exercism.io
    • [42’s own exercises (if available)] – Some campuses release past piscine tasks.

    7. German / Living in Heilbronn (Optional but Helpful)

    While not required, knowing basic German helps with daily life.

    🔹 Resources:

    • Duolingo – German course
    • Language Exchange Apps: HelloTalk, Tandem

    📅 Suggested Study Plan Before Piscine Starts

    WeekFocus
    Week 1Terminal + Git
    Week 2C basics (variables, loops, functions)
    Week 3Pointers, memory allocation
    Week 4Structs, recursion, linked lists + practice exams

    ✅ Final Tips:

    • Start early. Even if you spend just 1 hour/day now, you’ll be ahead.
    • Practice daily. Coding is a skill; repetition builds muscle memory.
    • Ask questions. Once you're in the Piscine, don’t hesitate to ask others — that’s how you survive.
    • Don’t panic. Everyone starts from scratch. The goal is to show growth, not perfection.

    Would you like a PDF checklist or daily study plan to follow? I can create one tailored to your current level and schedule!

  3. User

    What is the best daily schedule routine for the piscine to be optimal

  4. Qwen Assistant

    Creating a structured daily routine during the 42 Piscine (especially at 42 Heilbronn) is one of the best ways to stay focused, avoid burnout, and maximize your progress. The Piscine is intense — you’re expected to learn programming from scratch in just 4 weeks — so time management is critical.

    Here’s a proven daily schedule used by successful students in the Piscine, broken down into blocks that help you stay productive without burning out:


    🕒 Optimal Daily Schedule for 42 Piscine

    ⏰ Wake Up: 7:00 AM

    • Why early? Clear mind, less distraction.
    • Morning Routine: Eat a healthy breakfast, brush teeth, maybe a quick walk or stretch.

    📚 Block 1: Review & Planning – 8:00 AM – 9:00 AM (60 mins)

    • Review yesterday's work: Look over what you did, read any feedback from the Moulinette.
    • Plan today’s tasks: Write a small to-do list (3–5 items max).
    • Goal: Start the day with clarity and direction.

    💻 Block 2: Core Work Session #1 – 9:00 AM – 12:00 PM (3 hours)

    • Focus: Tackle your hardest or most important task first (e.g., solving a difficult exercise, learning pointers).
    • Tips:
      • Use Pomodoro: 25 min work / 5 min break
      • Avoid distractions (phones on silent!)
      • Ask peers when stuck (but only after trying yourself)

    🍱 Lunch Break – 12:00 PM – 1:00 PM (60 mins)

    • Eat well and rest. Don’t skip meals or eat poorly — it affects concentration.
    • Take a real break: Walk around, chat with others, clear your head.

    💻 Block 3: Core Work Session #2 – 1:00 PM – 4:00 PM (3 hours)

    • Focus: Continue working on exercises, fix errors, ask more questions.
    • Optional: Do a side project or rework failed exercises to understand mistakes.

    🧠 Block 4: Learn & Improve – 4:00 PM – 5:00 PM (60 mins)

    • Study documentation/man pages.
    • Review C concepts: Pointers, memory allocation, recursion.
    • Read Norminette rules if you're not passing style checks.
    • Watch short videos or read articles to reinforce understanding.

    🥋 Optional: Rush Practice / Group Work – 5:00 PM – 7:00 PM (2 hours)

    • Only if needed: If there's an upcoming Rush (group project), meet with your team.
    • Pair programming can help solve complex problems faster.

    🛌 Wind Down – 7:00 PM Onwards

    • Dinner + Relaxation: Eat well, maybe cook something simple.
    • Light activity: Listen to music, take a walk, or talk to friends.
    • Avoid all-nighters! Sleep is crucial for learning and memory retention.

    🛏️ Sleep – 10:30 PM – 7:00 AM (8.5 hours ideal)

    • Sleep is non-negotiable. Lack of sleep = slower thinking, more bugs, slower progress.

    🗓️ Weekly Rhythm Tips

    DayFocus
    MondayReview weekend progress, reset goals
    MidweekPush hard on current projects
    FridayPrepare for Friday exam, review weak areas
    WeekendRush projects come this weekend — expect long hours but pace yourself

    ✅ Pro Tips for Staying Optimized

    1. Use a To-Do List App: Notion, Todoist, or even a notebook.
    2. Track Your Progress: Mark completed tasks — gives motivation!
    3. Stay Hydrated & Move: Drink water, do light stretches every hour.
    4. Ask Smart Questions: Before asking someone, Google it or try to debug it yourself.
    5. Don’t Compare Yourself to Others: Everyone learns at different speeds.
    6. Celebrate Small Wins: Passing one test on the Moulinette is a win!

    📄 Bonus: Sample Daily Checklist Template

    ✅ Wake up & morning routine
    📅 Plan today's tasks
    💻 Core work session #1
    🍱 Lunch break
    💻 Core work session #2
    🧠 Study/Improve
    🥋 Rush/team work (if needed)
    🛌 Wind down & sleep
    

    Would you like me to generate a custom PDF version of this schedule or a Notion template you can use during the Piscine?

    Also, if you tell me how many hours per day you can commit before the Piscine starts, I can create a preparation plan tailored to you!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.